Skip to content

M3 decision package

Decision: Approved by Hector after independent M1 verification on 2026-07-26. Evidence: PR #14 approval record.

Approval authorizes bounded implementation issues and PRs; it does not authorize project-state or production mutation.

D-04. GitHub runtime mode

Recommendation

Keep authenticated gh CLI as the operator-mediated GitHub read path for M3. Do not create a dedicated unattended credential merely to complete the vertical slice. If later deployment requires unattended reads, treat that as a separate runtime-security decision with least privilege, rotation, audit, and degraded mode.

D-05. Plan and authorization identity

Recommendation

Use canonical JSON and SHA-256 for the proposed plan digest. Bind authorization to:

  • authorization ID;
  • plan ID and digest;
  • Initiative and workstream IDs;
  • stage and role;
  • exact targets and permitted operations;
  • corpus and prepared-context revisions;
  • conditions, expiry, and evidence requirements.

Authorization records are immutable. Changes create a new plan and a new authorization rather than editing the old record.

D-05. Review statuses

Recommendation

Use exactly:

  • not-reviewed;
  • changes-requested;
  • authorized;
  • refused.

Keep deterministic findings, supervisory judgment, and human escalation separate. Never encode authorized as human approval.

D-05. Material invalidation

Recommendation

Invalidate on any change to operation, target, Initiative, workstream, stage, role, plan digest, required evidence, corpus revision, prepared-context revision, authorization conditions, or expiry. Cosmetic presentation changes outside canonical plan serialization do not invalidate.

D-06. Compact-pack behavior

Recommendation

Use a bounded initial pack organized by:

  1. exact task and state bindings;
  2. binding gates and authority;
  3. relevant estate and accepted precedents;
  4. permitted tools and targets;
  5. named gaps, freshness, and source limitations.

Return expansion handles for omitted source material. Expansion creates a new context revision and invalidates authorization if the added context is material.

D-11. Feedback boundary

Recommendation

Feedback records execution result, evidence, deviations, unresolved items, and next action against one authorization. It may create observations or governed proposal candidates, but cannot alter active corpus or authorize follow-on execution.