Define Task Capsule contract for Memory Bank orchestration

[dapi]

Parent: #104 — Add durable orchestration and Task Capsule model for Memory Bank

Goal

Define the persisted state contract for an active task so a new session, machine, or agent can resume safely without reconstructing the full chat transcript.

Scope

• Define required fields: task_id, route, stage, current_role, next_role, artifact refs, completed/current/next action, assumptions, risks, evidence, stop conditions, and last handoff diagnostic.
• Define ownership of each field for Feature and Epic packages.
• Map the capsule to existing Feature and Epic lifecycle documents.
• Decide whether state lives in frontmatter, a dedicated handoff document, or a minimal combination.
• Ensure any task registry is only a projection and never a second source of truth.

Out of scope

• Runtime orchestration.
• Temporal integration.
• Automatic validators.

Acceptance criteria

• Capsule schema/example is documented.
• Feature and Epic storage locations are defined.
• Field ownership and lifecycle update rules are explicit.
• Resume inputs are sufficient without the full previous transcript.
• Canonical owner and SSoT boundaries are preserved.

References

• Article
• Feature Flow
• Epic Flow
• Session Handoff template