Skip to content

M2 decision package

These decisions define the migration envelope. Approval authorizes proposal creation and implementation planning, not direct corpus edits outside the governed workflow.

Decision: Approved by Hector on 2026-07-26. Evidence: issue #3 approval comment

D-10. Corpus packaging and precedence

Recommendation

Use typed, addressable units with:

  • stable id;
  • kind;
  • status: draft, active, deprecated, or archived;
  • explicit version;
  • dependency IDs and compatible versions;
  • layer: core or organization;
  • supersession metadata where applicable.

Resolution order:

  1. canonical core invariant;
  2. organization overlay at an explicitly allowed extension point;
  3. stage and role selection;
  4. inventory bindings;
  5. referenced standards and patterns;
  6. examples as non-authoritative guidance.

Conflicts, missing dependencies, cycles, and unauthorized core overrides fail closed. Archive content is never considered during live resolution.

D-11. Migration method

Recommendation

Use an incremental governed migration:

  1. Generate a read-only contradiction inventory.
  2. Group related corrections into bounded proposals.
  3. Require exact Conductor-Approval: approve per proposal.
  4. Implement each approved proposal in a PR.
  5. Keep old units active until their replacement is approved and validated.
  6. Deprecate before archiving; do not delete recovery history.
  7. Regenerate docs and run consistency checks in every migration PR.

Avoid a single wholesale corpus rewrite.

Organization overlays

Recommendation

Keep universal workflow and authorization semantics in core. Keep Hector's estate names, role assignments, tools, hosts, domains, approval identity, and provider bindings in an organization layer. Organization overlays may fill declared extension points but may not weaken core authority or safety rules.

Stage completeness

Recommendation

A stage is compilable only when entry, bindings, roles, artifacts, evidence, exit, next stages, validation mode, and recovery are present. Missing sections produce a named gap and prevent a deterministic-valid claim; they do not automatically forbid judgment-led exploratory planning.

Pattern mode

Recommendation

Require known, adapt, or novel for material implementation-pattern selection. adapt records differences and validation. novel records assumptions and review points. Examples never bind a choice by themselves.

Generated documentation

Recommendation

Treat generated docs as deterministic, provenance-labelled build output. CI fails when generated output is stale or contradicts designated canonical invariants. Generated pages remain navigable but cannot override their source units.

Approved decisions

  1. typed unit metadata and fail-closed dependency resolution;
  2. core/organization overlay boundary;
  3. complete-stage contract;
  4. known/adapt/novel pattern mode;
  5. incremental proposal-based migration;
  6. deterministic generated-doc and contradiction checks.

Approval does not replace the exact Conductor-Approval: approve required on each bounded proposal before its binding corpus changes are implemented.