Define digital role contracts and handoff protocol

[dapi]

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

Goal

Define reusable contracts for digital roles and the protocol by which one role hands work to another.

Scope

• Define role contract fields: inputs, allowed tools/skills, outputs, forbidden changes, next roles, exit criteria, and stop conditions.
• Define handoff payload and required artifact/evidence references.
• Define how a role reports incomplete work or a blocked transition.
• Define boundaries between role execution and workflow ownership.
• Keep contracts generic and suitable for downstream Memory Bank projects.

Out of scope

• Implementing a runtime agent runner.
• Temporal integration.
• Project-specific role names or product workflows.

Acceptance criteria

• A role contract format is documented.
• Handoff input/output requirements are explicit.
• Allowed and forbidden transitions are defined.
• Failure diagnostics include a machine-readable reason and next action.
• The contract aligns with routing, lifecycle, autonomy, and SSoT rules.

Dependencies

• Depends on Task Capsule contract subissue.

References

• Article
• Task Routing
• Autonomy boundaries
• Lifecycle Protocol template