Skip to main content

How to approve product scope

Use this procedure for one exact Epic or Feature.

  1. Select Approved for Solution, Deferred, or Rejected for the exact item.
  2. Carry every unresolved question by exact Q-#### ID.
  3. Record either decision_authority: Human with a trusted provider identity, or decision_authority: Delegated Project Lead with a trusted delegated-agent identity and exact authority basis.
  4. Include UTC date, exact item and state, conditions, and item-specific durable evidence.
  5. Append the hash-linked transition; never replace history. For approval, mirror it in approval.
  6. Verify generated registers, then notify Architecture only for independently approved Features.

A delegated decision includes:

decision_authority: Delegated Project Lead
actor:
  id: hermes:default
  display_name: Hermes
  identity_source:
    kind: delegated-agent
    provider: hermes
    subject_id: default
authority_basis:
  delegator_id: discord:1518725627845283888
  delegation_url: https://discord.com/channels/1518726359512387766/1537227679374508132/1538809400981196910
  scope: AeroSim full project leadership

The delegated actor makes the exact decision; the record must not say the delegator individually approved the item. Epic approval does not approve child Features. Question closure, Kanban state, documentation merge, CI, implementation, or silence is not approval. Implementation, task admission, release, and deployment remain separate exact decisions.