Delivery Lifecycle
CanonicalPurpose
The delivery lifecycle defines how Business coordinates approved work across humans, Agent Coder, ACS, governance, product owners, security reviewers, and requesters until deliverables are accepted and archived.
Delivery begins only after scope is approved. This page documents delivery coordination, not autonomous transaction execution, production deployment authorization, wallet signing, treasury movement, or governance execution authority.
Scope
This page applies to development, documentation, governance, BBA, Academy, ACS, Marketplace, DAO, reporting, and consulting deliverables coordinated through Business.
Delivery Inputs
Delivery should begin with an approved scope document, acceptance criteria, assigned owner, required resources, governance approval if required, security review requirements, technical requirements, communication plan, change request policy, and delivery milestones.
Stages
- Handoff: convert approved scope into execution tasks, owners, and delivery plan.
- Planning: align resources, dependencies, milestones, and risks.
- Implementation: build, configure, document, execute, or prepare artifacts.
- Internal review: validate deliverables before requester or DAO review.
- Security or governance review: validate sensitive deliverables involving contracts, plugins, treasury, tokenomics, governance, trading, or ACS permissions.
- Milestone delivery: submit partial or complete work for review.
- Change request handling: classify new requirements and assess impact.
- Final delivery: deliver the complete scope with documentation, release notes, and known limitations.
- Acceptance: confirm whether the work meets acceptance criteria.
- Archive: preserve final reports, records, links, decisions, and lessons learned.
Artifact Types
Business delivery may produce code, technical documentation, public documentation, governance artifacts, business artifacts, BBA campaign artifacts, Academy materials, ACS workflows, MCP specifications, automation plans, reports, or accountability records.
Milestone Model
Each milestone should define a title, scope reference, deliverables, owner, status, review requirement, acceptance criteria, blockers, phase, completion record, and notes.
Milestone statuses may include Planned, In Progress, Under Review, Changes Requested, Accepted, Blocked, or Cancelled.
Quality Gates
Business should verify:
- deliverables match approved scope;
- acceptance criteria are met;
- documentation and handoff notes are present;
- sensitive work received required review;
- governance-sensitive work was approved;
- DeFi, trading, token, treasury, or financial-risk language is present where needed;
- the next operator, client, DAO, or product owner can use the deliverable.
ACS Role
ACS may generate task breakdowns, draft Coder instructions, summarize blockers, compare deliverables to scope, draft checklists, prepare delivery reports, classify change requests, and detect missing documentation.
ACS cannot final-accept sensitive delivery, replace security review, override governance or requester acceptance, or commit to unapproved scope.
Delivery Risks
Risks include unclear scope, dependency blockers, review delay, scope creep, implementation drift, documentation gaps, and acceptance gaps.