Independent decision mandates in Agent Morphogenesis

Select the route that the policy actually requires

The decision reference lists local policy, authorized agent, authorized person, collective and composite routes. It does not inherently prefer one route or require a person in every case.

For an illustrative organizational change, decide whether the policy calls for an independent specialist, a human reviewer, a quorum or a combination. A generic approval button should not conceal which route and conditions were required.

A mandate is more specific than a role label

Membership or a role can identify a participant without authorizing this decision. A mandate must apply to the proposal's scope and current coordinates, including relevant epochs, policy and expiry.

A reviewer approved for one project should not automatically approve a similar-looking change in another. Preserve the exact binding so the decision can be checked against the proposal actually prepared for execution.

Make independence an enforceable condition

The governance guide allows proposer–decider separation and independent assessment. Policy can prohibit an agent from approving its own creation, promotion, authority expansion or descendant creation.

In an illustrative composite review, two records signed by the same underlying principal do not satisfy a requirement for distinct actors merely because they came from separate interface sessions. Apply the configured identity and independence checks, rather than counting approval events without their principals.

Resolve Room review into the exact binding

The Room integration reference states that ordinary Room participation or generic approval is insufficient for Morphogenesis authority. The adapter must resolve the exact current decision binding before preparation.

This keeps a useful collaboration interface from becoming a shortcut around the specialized decision contract. Show the reviewer which proposal and epoch the action addresses, and reject a stale screen rather than silently binding it to newer work.

Retain execution authorization as a later boundary

A decision binding approves exact proposal coordinates. Separate execution authorization and the owning subsystem receipts still matter. The operational threat list includes self-approval and dependent reviewer collusion alongside stale records.

• Test an authorized current reviewer.
• Reject a principal lacking the exact mandate.
• Exercise self-review where policy forbids it.
• Reject stale or cross-scope decision reuse.
• Confirm approval alone does not execute the effects.