Skip to main content

Concepts

ASF50 has its own vocabulary. Most of these terms are defined directly in code (scripts/goal-runner/*.py). The pages below are the canonical mental model.

TermOne-linerSee
GoalA bounded unit of work, durable and Git-tracked.Goals
ProgramA long-running goal that orchestrates many IMPs.Goals
PhaseEither a PHASE-XX program-roadmap phase or an IMP-XX execution phase.Phases
TaskA declared unit of work inside a goal.Goals
RunA single dispatched attempt to complete a task.Goals
AgentA role-bound actor (Planner, Builder, Tester, Auditor, …).Agents
RoleThe named capability set a run is dispatched under.Agents
WorktreeA detached Git working tree used to isolate dispatch.Agents
ReceiptA durable artifact written when a task transitions.Receipts
EvidenceAny file in evidence/<GOAL_ID>/ that proves an assertion.Receipts
Runtime stateThe SQLite-backed state owned by RuntimeStore.State
Canonical stateThe Git-tracked source of truth (contracts, evidence).State
Human gateA scoped owner decision required before a destructive step.Human Gates
Owner authorizationThe provenance channel for an approval.Owner Authorization
Gate scopeWhat kind of decision a gate represents.Human Gates
Gate sourceWhere the approval came from (GitHub, signed ticket, CLI).Owner Authorization
Dispatch consumptionA gate is consumed by a run; consumption is recorded.Human Gates
Production subjectThe exact subject_sha a release is bound to.Signed Tickets
PromotionA signed-ticket-driven production authorization.Signed Tickets
Signed ticketAn OpenSSH-signed authorization payload.Signed Tickets
DeviationA recorded non-blocking event that must be accounted for.Deviations
RollbackA governed undo of a release.Playbooks → Rollback

Continue with Goals.