Milestones
CanonicalPurpose
Milestones make Runtime measurable. A milestone is a checkpoint. A deliverable is an output. Acceptance criteria define whether that output is complete.
Without milestones and deliverables, Runtime cannot distinguish progress from activity.
Scope
This page applies to documentation, code, governance, Business, Academy, Trading, Treasury, BBA, ACS, and accountability work.
Definitions
- Milestone: defined checkpoint in a runtime or delivery lifecycle.
- Deliverable: concrete output expected from scope or milestone.
- Acceptance criteria: conditions used to validate that a deliverable meets scope.
- Checkpoint: planned review moment or status boundary.
Milestone Types
Milestones may track intake completion, classification, ACS analysis, human review, governance review, security review, scope confirmation, approval, implementation progress, validation, deployment, proposal execution, plugin activation, report publication, or archive completion.
Deliverable Types
Deliverables may include public docs pages, knowledge packs, guides, code, APIs, smart contracts, tests, proposal drafts, reason codes, execution receipts, scope documents, campaign briefs, course outlines, assessments, reward policy drafts, strategy specs, risk reports, allocation reviews, exposure reports, ACS workflows, MCP permission models, and memory updates.
Record Fields
A milestone record should include milestone identifier, runtime identifier, title, description, milestone type, owner, status, deliverables, acceptance criteria, required reviews, blockers, dependencies, evidence links, completion timestamp, and notes.
A deliverable record should include deliverable identifier, milestone identifier, runtime identifier, title, type, description, file or link, owner, status, review status, acceptance status, known limitations, and evidence links.
Milestone Statuses
Milestones may be Planned, In Progress, Under Review, Changes Requested, Accepted, Blocked, Cancelled, or Superseded.
Quality Gates
Each deliverable should be checked for scope match, completeness, required review, risk or limitation disclosure, documentation usefulness, and preserved evidence.
Anti-Patterns
Avoid treating activity as a milestone, creating milestones without acceptance criteria, hiding blockers, leaving milestones without owners, and producing deliverables without evidence.