This repository has been archived on 2026-10-29. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Epiphany/notes/repo-work-canonical-convergence.md
2026-07-14 01:08:41 +01:00

4.5 KiB

Repo-Work Canonical Convergence

Objective

Preserve the branch-local repo-work user story without preserving its second Modeling, Self, Hands, Soul, or Mind authority. Repo-work is a workflow over one canonical RepoFrontierItem; it is not another repository model.

Authority Map

  • Owner: runtime-spine RepoModel owns repository anatomy and frontier lifecycle.
  • Inputs: an immutable work proposal; an admitted frontier identity; a typed plan candidate and Mind adoption; the current model and route; immutable Substrate/Hands consequences; Soul verification; Modeling verdict incorporation; provider publication receipts.
  • Outputs: one admitted frontier transition plus derived workflow/closure/public proof projections.
  • Derived state: filesystem plan/run/execute/close artifacts, operator rows, closure history, and public proof bundles. They may explain or export the canonical chain; they may not schedule, repair, or close it.
  • Forbidden writers: item-slug route synthesis, RepoWorkModelingRequest, RepoWorkModelingRoute, RepoWorkModelingFinding, RepoWorkMapEntry, revise-modeling, plan-derived independent Hands grants, JSON-existence phase selection, and local Verse map rows that claim current anatomy.
  • Shared path: proposal -> Modeling Evolution -> Mind frontier admission -> Self planning request -> Imagination plan candidate -> Mind plan adoption -> Self execution route -> Hands authority/consequence -> Soul verification -> Modeling verdict incorporation -> Mind final admission -> derived closure/public proof.
  • Deletion line: legacy Modeling/map writers and scheduler routes are cut before new execution is enabled. Historical documents may remain readable only as inert history.

Organ Ownership

  • Modeling authors repository claims and frontier proposals; it does not author commands or adopt its own output.
  • Self emits a typed planning request bound to one current frontier id/hash and assigns Imagination. This is not an execution route.
  • Imagination authors a candidate response bound to that planning request.
  • Mind admits the exact plan candidate.
  • Self then emits a distinct execution route that freezes the current model, frontier item, and adopted plan for Hands. Do not generalize both phases into a generic router until a shared invariant actually earns that abstraction.
  • Hands acts only from that route and the Substrate grant.
  • Soul judges the exact consequence chain.
  • Modeling incorporates Soul's verdict into the same frontier item; Mind admits the transition.
  • Bifrost/provider receipts own publication and merge truth.

Bootstrap

Direct User intake emits an immutable nonprivate proposal, not a work item. Explicit coordinator selection binds that exact proposal to one coordinator- owned typed Modeling launch projection and job. Ordinary Evolution cannot mutate frontier. Only the selected-proposal Evolution path may create exactly one proposal-citing frontier item, and Mind replays the complete persisted launch/result/review chain before making the wound real. Plan/adopt requires that admitted frontier identity; Persona prose, evidence intersection, CLI slug, filesystem path, or old close receipt may not synthesize it.

Rebuild Order

  1. Landed: refuse and delete new legacy repo-work Modeling/map mutations, retry routes, worker ingress, independent plan-adoption/Hands grant, scheduler/publication authority, and current-looking CultMesh writers. Historical readers are sight-only and cannot feed gates, actions, closure, pending Bifrost requests, or accounting. Temporary workflow outage is honest.
  2. Foundation landed: immutable inert proposal, typed Self planning request, Imagination plan candidate, and Mind plan adoption exist with exact model, admission, frontier, scope, candidate-byte, race, and retry proofs. Explicit User intake, exact coordinator selection, coordinator-owned typed Modeling launch projection, immutable job/request/proposal binding, and proposal-bound Evolution admission are also landed and Soul-approved.
  3. Bind adopted plan identity into a distinct Self execution route plus Hands authority. Re-enable execution only through that chain.
  4. Rewire verification/closure through canonical Soul and verdict incorporation.
  5. Rebuild closure/public proof as read-only joins, then delete stale map schemas and projection keys.

Do not encode plan readiness in RepoFrontierStatus. The model owns the wound; the plan owns a proposed response; Self owns their binding.