Add repo scheduling request work family

This commit is contained in:
Meta Vens 2026-06-20 16:12:30 +01:00
commit f90358575c
6 changed files with 638 additions and 9 deletions

View file

@ -281,15 +281,19 @@ review-required, unadopted objective proposal with Mind, Self, and Bifrost gates
before scheduling or consequence; and `--action-family repo-adoption-request`
writes a structured Mind adoption request under
`.epiphany/adoption-requests/<item>.toml`, asking Mind to adopt/refuse/request
more consensus without itself committing state or scheduling work. Its receipt
more consensus without itself committing state or scheduling work; and
`--action-family repo-scheduling-request` writes a structured Self scheduling
request under `.epiphany/scheduling-requests/<item>.toml`, naming the queue
pulse contract that may be considered only after Mind adoption receipts exist
without itself mutating the queue or scheduling work. Its receipt
includes
`epiphany.repo_work_plan_derivation.v0`, mode `append-worklog`,
`planning-note`, `checklist-note`, `section-note`, `repo-status-section`, or
`task-card`, `repo-manifest`, `repo-tool-capabilities`, or
`repo-collaboration-topic`, `repo-consensus-brief`, `repo-objective-draft`, or
`repo-adoption-request`, a `safeActionFamily`, and an authority seal forbidding
publication, merge, service lifecycle mutation, cross-repo mutation, and private
state exposure.
`repo-adoption-request`, or `repo-scheduling-request`, a `safeActionFamily`, and
an authority seal forbidding publication, merge, service lifecycle mutation,
cross-repo mutation, and private state exposure.
These deterministic families are quarantine scaffolding on the road to
model-authored Imagination, but they are no longer operator-authored shell
details.
@ -470,6 +474,20 @@ receipt requirements, `does_not_modify_state=true`, denied state commit,
scheduling, Hands action, publication, cross-body authority, and
`privateStateExposed=false`.
The next Self scheduling-boundary smoke proved scheduling request cargo:
`.epiphany-smoke\repo-scheduling-request-family-20260620-150758` ran init ->
online -> accept -> `derive-plan --action-family repo-scheduling-request
--model-ref repo-scheduling-request-family-smoke-imagination-v1 --model-authored`
-> tick through run/adopt/execute/close on a fresh repo. The plan carried
`safeActionFamily=repo.scheduling_request`; Hands committed only
`.epiphany/scheduling-requests/repo-scheduling-request-family.toml`; Soul passed
with `pathScopeMatched=true` and `familyAssertions.status=passed`; the committed
request carried `schema_version = "epiphany.repo_scheduling_request.v0"`,
`status="awaiting-mind-adoption"`, Self queue target, bounded one-item pulse,
Mind review/state-commit receipt requirements, denied Self scheduling, queue
mutation, Hands action, publication, cross-body authority, and
`privateStateExposed=false`.
### Landed Work Run Gate
The sixth front door exists as native Rust:
@ -1183,7 +1201,7 @@ temptation wearing clean robes.
| Repo Body birth | `epiphany-repo init` exists and writes repo-local stores plus branch workbench intent. | Keep birth startup-only, review-gated, and branch-oriented. |
| Local Verse online | `epiphany-swarm online` seeds repo-local CultMesh, standing-faculty SoA, topology, liveness, Eve, and tool sight. | Keep private Verse sealed while exposing operator-safe repo status. |
| Persona/Bifrost intake | `epiphany-work accept` records pressure and candidate action refs without Hands authority. `epiphany-work persona-intake` now invokes the Persona bubble speech-audit path, records public discussion and candidate-action refs, then delegates to `accept`; wrapper mode `repo-persona-intake` exposes the operator mouth. | Deepen the intake-to-Imagination interpreter so richer model-authored action items can be proposed without granting Hands, publication, or durable-state authority at the mouth edge. |
| Imagination planning | `derive-plan` now writes a typed `epiphany.repo_work_imagination_action_items_receipt.v0` before the executable plan receipt. The action-item receipt can carry model provenance, allowed safe family, requested paths, verification asks, stop conditions, escalation reasons, and private-state seals; command text remains deterministic safe-family lowering for `append-worklog`, `planning-note`, `checklist-note`, `section-note` / `repo.markdown_managed_section`, `repo-status-section` / `repo.status_section`, `task-card` / `repo.task_card`, `repo-manifest` / `repo.body_manifest`, `repo-tool-capabilities` / `repo.tool_capabilities`, `repo-collaboration-topic` / `repo.collaboration_topic`, `repo-consensus-brief` / `repo.consensus_brief`, `repo-objective-draft` / `repo.objective_draft`, and `repo-adoption-request` / `repo.adoption_request`. `plan` remains manual quarantine scaffolding. | Deepen model-authored planning and further useful repo-owned configuration classes without turning model text into arbitrary shell authority. |
| Imagination planning | `derive-plan` now writes a typed `epiphany.repo_work_imagination_action_items_receipt.v0` before the executable plan receipt. The action-item receipt can carry model provenance, allowed safe family, requested paths, verification asks, stop conditions, escalation reasons, and private-state seals; command text remains deterministic safe-family lowering for `append-worklog`, `planning-note`, `checklist-note`, `section-note` / `repo.markdown_managed_section`, `repo-status-section` / `repo.status_section`, `task-card` / `repo.task_card`, `repo-manifest` / `repo.body_manifest`, `repo-tool-capabilities` / `repo.tool_capabilities`, `repo-collaboration-topic` / `repo.collaboration_topic`, `repo-consensus-brief` / `repo.consensus_brief`, `repo-objective-draft` / `repo.objective_draft`, `repo-adoption-request` / `repo.adoption_request`, and `repo-scheduling-request` / `repo.scheduling_request`. `plan` remains manual quarantine scaffolding. | Deepen model-authored planning and further useful repo-owned configuration classes without turning model text into arbitrary shell authority. |
| Self scheduling | `tick` and `serve` prove one-step branch-local advancement, brake refusal, active-turn refusal, cooldown, and stale-turn recovery; `tick` now routes executed branch-local work through the existing Soul/Modeling/Mind `close` gate; `queue-run` selects tick-actionable rows from the typed repo-work queue and delegates to `tick`; `epiphany-swarm run` is the bounded operator mouth over that queue/tick physiology; `repo-work-service-plan` and `repo-work-service-runbook` write Idunn lifecycle receipts/artifacts for the same queue-run command without launching it. | Keep any future queue-run service launch/install behind Idunn and explicit operator authority. |
| Branch-local Hands work | `adopt` and `execute` create approved Hands gates, run planned commands, stage declared paths, commit on `epiphany/*`, and write receipts. | Keep mutation branch-contained and receipt-backed; broaden only through typed plan families, not ad hoc shell freedom. |
| Soul/Modeling/Mind closure | `close` verifies the Hands commit, writes `epiphany.repo_work_closure_review.v0`, refuses path-scope mismatches, and writes Soul, Modeling, and Mind receipts. | Deepen model-authored closure review beyond the first structured closure-review packet while preserving deterministic local closure for simple mechanical work. |
@ -1473,6 +1491,9 @@ Required organs before MVP:
`repo-adoption-request` now proves Mind-facing adoption request cargo that
asks for an adopt/refuse/more-consensus verdict without committing state or
scheduling work.
`repo-scheduling-request` now proves Self-facing scheduling request cargo that
names a bounded queue pulse after Mind adoption while granting no scheduling,
queue mutation, Hands, publication, or cross-body authority.
Remaining work is later model-authored action classes that can change more
useful repo-owned configuration without arbitrary shell authority.
- Closure depth: `close` now writes a structured

View file

@ -125,6 +125,7 @@ remembers doctrine; the branch remembers the blade.
- 2026-06-20: `repo-consensus-brief` is now live as draft Imagination consensus cargo. `epiphany-work derive-plan --action-family repo-consensus-brief` writes `.epiphany/consensus-briefs/<item>.toml` with safe family `repo.consensus_brief`, draft consensus state, public discussion refs, candidate action refs, non-authoritative candidate action semantics, review requirement, Mind/Bifrost gates, and seals against objective adoption, Hands action, publication, cross-body mutation, and private Verse rummaging. Soul closure assertions inspect schema, family, summary, draft state, Imagination route, public/candidate inputs, authority gates, and private-state seal. Focused smoke `.epiphany-smoke\repo-consensus-brief-family-20260620-144212` ran init -> online -> accept -> repo-consensus-brief derive-plan -> tick run/adopt/execute/close; Hands committed only `.epiphany/consensus-briefs/repo-consensus-brief-family.toml`, Soul passed with `pathScopeMatched=true`, `familyAssertions.status=passed`, `candidateActionsNonAuthoritative=true`, `mindAdoptionRequired=true`, `bifrostPublicationRequired=true`, and `privateStateExposed=false`. Current remaining repo-swarm MVP organs are richer model-authored planning depth beyond deterministic safe-family lowering, more useful repo-owned configuration/action families, and Idunn-owned queue-run service lifecycle under explicit operator authority.
- 2026-06-20: `repo-objective-draft` is now live as review-required Objective Draft cargo. `epiphany-work derive-plan --action-family repo-objective-draft` writes `.epiphany/objective-drafts/<item>.toml` with safe family `repo.objective_draft`, draft status `review-required`, `objective_adopted=false`, objective statement, acceptance criteria, public/candidate refs, and Mind/Self/Bifrost gates before adoption, scheduling, or publication. Soul closure assertions inspect schema, family, summary, draft review state, acceptance criteria, inputs, authority gates, and private-state seal. Focused smoke `.epiphany-smoke\repo-objective-draft-family-20260620-145012` ran init -> online -> accept -> repo-objective-draft derive-plan -> tick run/adopt/execute/close; Hands committed only `.epiphany/objective-drafts/repo-objective-draft-family.toml`, Soul passed with `pathScopeMatched=true`, `familyAssertions.status=passed`, `draftReviewRequired=true`, `objectiveAdopted=false`, `mindAdoptionRequired=true`, `selfSchedulingAuthorized=false`, and `privateStateExposed=false`. Current remaining repo-swarm MVP organs are richer model-authored planning depth beyond deterministic safe-family lowering, more useful repo-owned configuration/action families, and Idunn-owned queue-run service lifecycle under explicit operator authority.
- 2026-06-20: `repo-adoption-request` is now live as Mind-facing adoption request cargo. `epiphany-work derive-plan --action-family repo-adoption-request` writes `.epiphany/adoption-requests/<item>.toml` with safe family `repo.adoption_request`, status `awaiting-mind-review`, allowed verdicts `adopted|refused|needs-more-consensus`, Mind review/state-commit receipt requirements, objective/consensus antecedents, and seals against objective adoption, state commit, Self scheduling, Hands action, publication, cross-body mutation, and private Verse rummaging. Soul closure assertions inspect schema, family, summary, request state, decision contract, inputs, authority gates, and private-state seal. Focused smoke `.epiphany-smoke\repo-adoption-request-family-20260620-145823` ran init -> online -> accept -> repo-adoption-request derive-plan -> tick run/adopt/execute/close; Hands committed only `.epiphany/adoption-requests/repo-adoption-request-family.toml`, Soul passed with `pathScopeMatched=true`, `familyAssertions.status=passed`, `awaitingMindReview=true`, `doesNotModifyState=true`, `stateCommitAuthorized=false`, `selfSchedulingAuthorized=false`, and `privateStateExposed=false`. Current remaining repo-swarm MVP organs are richer model-authored planning depth beyond deterministic safe-family lowering, more useful repo-owned configuration/action families, and Idunn-owned queue-run service lifecycle under explicit operator authority.
- 2026-06-20: `repo-scheduling-request` is now live as Self-facing scheduling request cargo. `epiphany-work derive-plan --action-family repo-scheduling-request` writes `.epiphany/scheduling-requests/<item>.toml` with safe family `repo.scheduling_request`, status `awaiting-mind-adoption`, Objective Draft/adoption request refs, Mind review/state-commit receipt requirements, a bounded one-item queue pulse contract, and seals against Self scheduling, queue mutation, Hands action, publication, cross-body mutation, and private Verse rummaging. Soul closure assertions inspect schema, family, summary, request state, queue contract, receipt contract, authority gates, and private-state seal. Focused smoke `.epiphany-smoke\repo-scheduling-request-family-20260620-150758` ran init -> online -> accept -> repo-scheduling-request derive-plan -> tick run/adopt/execute/close; Hands committed only `.epiphany/scheduling-requests/repo-scheduling-request-family.toml`, Soul passed with `pathScopeMatched=true`, `familyAssertions.status=passed`, `awaitingMindAdoption=true`, `queueMutationAuthorized=false`, `selfSchedulingAuthorized=false`, and `privateStateExposed=false`. Current remaining repo-swarm MVP organs are richer model-authored planning depth beyond deterministic safe-family lowering, more useful repo-owned configuration/action families, and Idunn-owned queue-run service lifecycle under explicit operator authority.
- `service-execution-runbook` makes that next cut repeatable: it generates the exact elevated wrapper command sequence without mutating the service manager, continues after per-step failure to preserve more receipts, runs `service-execution-audit` in `finally`, exits nonzero if any step failed, and seals a typed runbook lifecycle receipt. Run the generated artifact only with explicit operator authority.
- `service-execution-audit` is the non-mutating acceptance proof after the elevated rite: it reports `complete` only when typed lifecycle receipts prove the runbook witness plus expected elevated chain, and otherwise reports the missing/failed sealed checks.
- `service-tick` is the non-elevated scheduler pulse proof: it writes the latest daemon scheduler receipt through durable policy ownership and local wrapper receipts.