The methodology
Formwork
An open engineering methodology for structured agentic development.
AI can generate the material. Engineering must provide the form.
Formwork gives complex agent work enough structure to remain coherent across prompts, sessions, developers, sprints, and quarters. When the work is complete, temporary plans are retired or archived, while durable learning is graduated into the living harness that continues guiding the codebase.
The problem
Generation is not structure
Coding agents can produce useful implementation quickly, but generated output does not arrive with a reliable delivery system around it. Complex work still needs research, specifications, decomposition, decisions, approval boundaries, verification, and a durable record of what changed and why.
Formwork provides that engineering structure without pretending every artifact should live forever.
The central distinction
Temporary Formwork and the Living Harness
Formwork distinguishes between the structures required to carry a specific initiative and the structures that should continue guiding the codebase afterward.
Temporary formwork includes research, plans, task breakdowns, working assumptions, progress state, and handovers. These artifacts travel with the work when it spans more than one prompt, session, pull request, sprint, or quarter.
The living harness contains the durable knowledge and controls that future developers and AI tools still need: specifications, architecture decisions, tests, verification gates, repository instructions, agent skills, policies, golden paths, and tool configuration.
Specs describe the system as it is. Plans carry the work that changes it. Readers who know spec-driven development will recognize the intent and notice the split: specifications stay behavioral and current in the living harness, while plans are free to carry rich execution context because they are built to retire. Neither artifact has to do the other's job, and neither goes stale doing it.
Temporary formwork carries the change. The living harness carries the learning.
The artifact lifecycle
What retires and what remains
At the end of an initiative, Formwork requires an explicit decision for each meaningful working artifact. It may be retired because its job is complete, archived as useful historical evidence, or graduated into the living harness because the learning should continue shaping future work.
This prevents two common failures: context evaporation, where valuable reasoning disappears when a task ends; and context sedimentation, where every temporary plan remains forever and gradually becomes stale repository debris.
The delivery structure
Built to carry work across time
Formwork organizes delivery through Initiatives, Milestones, Phases, and Tasks, supported by research, specifications, architecture decisions, verification criteria, progress state, and evidence. The structure can travel across coding-agent sessions and human handoffs without forcing the team to reconstruct the intent each time.
Initiative Milestone Phase Task
Plans are ephemeral. Continuity is not.
The lifecycle payoff
Every initiative should strengthen the next one
The completed implementation is not the only output of the work. A useful review finding can become a test. A repeated correction can become an agent skill or repository instruction. A successful implementation pattern can become a golden path. An architectural decision can become durable context.
Every completed initiative should leave both working software and a stronger engineering system.
Methodology and product
Formwork and Artificer Crucible
Formwork is the open methodology. Artificer Crucible is the managed harness being built to operationalize the broader system around agent work: codebase readiness, structured context, approval boundaries, secure execution, verification, observability, cost controls, and feedback loops.
Formwork defines how complex work is shaped and how temporary delivery artifacts become durable engineering knowledge. Crucible is being built to apply and govern that lifecycle in real codebases.
The open method
Developed in the open
Formwork is being published as an open methodology so engineering teams can inspect it, challenge it, adapt it, and use the parts that solve real problems. The repository contains the concepts, artifact conventions, reusable skills, and worked examples that make the method practical.
The Fishery will use Formwork to build smaller public labs, showing how the method carries bounded agentic and infrastructure projects from intent through verification.
FAQ
Common questions
Is Formwork another coding-agent framework?
No. Formwork is a methodology and set of engineering conventions for structuring work around coding agents. It does not require a particular model, IDE, orchestration framework, or runtime.
Why are plans temporary?
Plans exist to carry a bounded initiative. Keeping every plan active forever creates stale and contradictory context. Formwork preserves continuity while the work is active, then explicitly retires, archives, or graduates its artifacts.
How does Formwork differ from spec-driven development?
Spec-driven development gets the important part right: agents do better work when context is explicit and structured. Formwork keeps that insight and splits the artifact in two. Specifications describe the system as it is, stay behavioral, and are updated whenever the system changes. Plans are the temporary formwork: they carry what execution actually needs, from the files to touch and the loop to run to model routing, verification, and the definition of done, and they can afford that richness because they retire when the work completes. That split is what keeps specifications current instead of slowly absorbing stale execution detail.
What is the living harness?
The living harness is the maintained set of specifications, decisions, tests, instructions, skills, policies, tools, and verification controls that continuously guide both human and AI-assisted development.
Does Formwork replace agile methods?
No. Formwork can operate inside sprints, Kanban flow, milestone planning, or other delivery systems. It focuses on the structure and artifact lifecycle required for complex agentic work.
How is Formwork related to Artificer Crucible?
Formwork is the open method. Artificer Crucible is the managed product being built to operationalize the wider harness around agent work in real codebases.
Give agent work a structure it can carry.
Explore the Formwork methodology, follow its development, and use it in your own projects.