Code verifies
Required evidence, criteria results, record integrity, candidate identity, required council seats and unresolved rework.
How it works
A handover is a promise.
Acceptance closes the loop.
Each role owns a distinct kind of judgment. The next role returns a delivery against the agreement it received, and the sender checks that agreement was honored.
Follow one change.
Agree on the outcome.
The analyst captures who needs the export and what a useful result looks like. The architect and planner define constraints, affected interfaces and the validation approach.
Purpose + scope + acceptance criteriaHand over an explicit contract.
The planner sends the developer the approved scope, required artifacts and acceptance criteria: correct columns, access boundaries, test results and documented behavior.
RoleHandoff + AcceptanceContractDeliver work with evidence.
The developer implements the change. The tester owns the test verdict. The receiving role returns evidence and declares deviations, rather than asking the sender to infer what happened.
DeliveryReceipt + criterion results + evidence referencesCheck before reviewing.
Code verifies required evidence, record integrity and the current candidate. If a required check fails, the delivery returns for rework. A positive model opinion cannot override it.
Deterministic verification reportAccept, or return with a reason.
The sender checks conformance to the handover. Cross-domain questions can go to a council. Blocking objections need resolution, and sensitive work still needs human approval.
AcceptanceDecision or ReworkRequest
Deterministic first
Use code for checks.
Use judgment for meaning.
Not every review question needs an LLM. AgentFlow separates repeatable verification from the judgment a specialist must own.
Roles judge
Whether the design fits the problem, the behavior meets the need and the delivery conforms to the agreed method and scope.
Humans authorize
Consequential actions and high-assurance acceptance remain subject to the host's authorization controls and human review.
A content digest detects changed evidence. It does not authenticate a person, prove that software is correct or replace a security review.
Collaboration proportional to complexity
Call the right council.
Keep a clear decision owner.
A council is a bounded request for advice inside a role, not a new lifecycle phase and not a majority vote. Required experts review the same evidence; the owner resolves objections.
Routine work / Linear
Complete, low-risk work takes deterministic checks first. It does not need a standing council or a different agent for every role.
Uncertain or cross-domain work / Bilateral
The sender explicitly accepts conformance to the contract after the receiving role delivers. Methods and domain thresholds are configurable.
Broad impact, public contracts or migrations / Council
Targeted seats contribute structured advice, evidence and objections. Deferred blocking objections do not permit acceptance. Seats can run sequentially or in parallel.
Sensitive or high-assurance work / Human-gated
Deterministic checks and council evidence support a delivery-bound human approval. Customization cannot remove built-in sensitive-surface and high-assurance controls.
Nine lifecycle roles
Distinct responsibilities.
Flexible execution.
One executor may perform several roles. Independence is preserved where review requires it. Each role has a defined scope, inputs, outputs and handover boundaries.
- Product managerOwns product intent and priorities.
- AnalystClarifies needs and acceptance criteria.
- ArchitectOwns system design and boundaries.
- Implementation plannerTurns the design into a delivery plan.
- DeveloperOwns the implementation.
- TesterOwns validation and test verdicts.
- Technical writerOwns the documentation.
- ReviewerProvides independent review.
- PR readinessChecks evidence and readiness for integration.
An optional QA expert is a specialist sidecar, not a tenth lifecycle phase. The orchestrator coordinates the flow; skills support specific work without changing role ownership.
Inspect role definitions and methods ↗Start small. Keep control.
One repository.
One clear next step.
The next delivery update
From a passing check to an accepted change.
The new run workflow connects criteria, actual observations and the accountable role decision. It remains in development; the illustrated interaction above is not a live execution.
Freeze the criteria
Agree what must be demonstrated before running the check. Changed requirements or inputs invalidate earlier evidence.
Observe the behavior
Collect the current test report and required assertions. Journey coverage reveals missing product behavior.
Accept and recover
Advance only with current evidence and role acceptance. Unknown actions or an active prior writer block unsafe recovery.
Development preview · release acceptance pending · AgentFlow requires a supported AI client and any necessary subscription or API access.