Map planning brief false authority

This commit is contained in:
Meta Vens 2026-07-13 03:53:31 +01:00
commit c8a5efd3cb
5 changed files with 42 additions and 1 deletions

View file

@ -1131,6 +1131,39 @@ real grant into an apparent denial.
Twenty high-authority closure families are typed. Direct source inventory now
reports 278 substring occurrences across thirteen remaining families.
## Planning catalog as work-item plan
`repo.planning_brief` contains no candidate work-item records. Its instance
data is only item metadata, summary, and public/candidate references. The other
sections are copied global doctrine: a candidate schema, the complete safe-
family catalog, closure-proof policy, closure ladder, and organ gate order.
Closure then reads those copied constants back and emits
`safeFamilyPlanning`, allowing catalog completeness to impersonate actual
decomposition.
Authority map for the cut:
- Owner: no owner exists for the claimed plan because no candidate plan is
present. Imagination owns genuine candidate decomposition when it produces
candidate action items.
- Inputs: accepted public pressure and candidate references.
- Output today: one per-item file containing mostly global catalog/policy.
- Derived state: `safeFamilyPlanning` is catalog self-attestation, not evidence
that this item has a plan.
- Forbidden writers: the planning-brief closure/readback may not satisfy
readiness, evidence, or planning gates from copied constants.
- Shared path: derive-plan, close, overview/readback, readiness, and the family
smoke all currently share the false witness.
- Deletion line: remove the `repo.planning_brief` safe family, its generator,
closure arm, `planning_brief_safe_family_readback`, dedicated smoke, and any
readiness dependency on `safeFamilyPlanning`. Preserve the real preparation
chain: consensus draft, interpretation request, objective draft, then Mind
adoption.
Do not replace the family with another catalog-shaped document. If a later
planning artifact is needed, it must contain actual candidate action records
and reference a separately owned contract/catalog.
The same inspection found 33 consecutive duplicate `#[cfg(test)]` attributes
on provider constructors/writers and their re-exports. One gate already makes
each item test-only; the second owned nothing. The duplicates are removed.

View file

@ -53,6 +53,7 @@
- Bifrost artifact-acceptance and metrics requests remain open until actual Bifrost/Maintainer receipts are ingested. The stale response-closing request-family smokes, accounting bundle, wrapper mode, and aggregate green gate are deleted.
- Repo-work readiness reports are sight only. The generic readiness-review approval command and writer are deleted because one caller supplied four unresolved reviewer labels. `repo.readiness_review_request` now assigns routing to Self, lists Maintainer/Soul/Mind/Bifrost as independent required reviewers, and names no readiness-approval owner; typed review readers await genuine multi-organ/provider evidence.
- Interpreter Brief is preparation cargo authored by Imagination from accepted public pressure. It requests Mind interpretation and remains `interpretation_admitted=false`; it is not Mind-owned state until a genuine Mind path supplies and admits interpretation evidence.
- `repo.planning_brief` is condemned pending one coherent deletion pass: it contains no candidate work-item records and currently lets copied global catalog/schema/closure constants self-attest as per-item `safeFamilyPlanning`. The real preparation chain is consensus draft -> interpretation request -> objective draft -> Mind adoption.
- There is no aggregate repo-swarm MVP gate. The former smoke manually aggregated fixture summaries into green rows and `demoReady=true`; it and its wrapper are deleted. Whole-organism readiness requires a live-fire path whose claimed consequences are observed at their owning boundaries.
- Persona owner: `collaboration-feedback` writes public, bounded feedback only after that provider receipt exists.
- Imagination owner: consensus participant selection, packet reference, receipt status/id, and adoption gate.

View file

@ -368,6 +368,13 @@ counterfeit-state-authority fixture. Nineteen high-authority families are typed;
direct source inventory reports 303 substring occurrences across fourteen
remaining families.
Planning Brief is mapped for deletion, not typing. It contains no candidate
work-item records; copied global schema/catalog/closure doctrine is read back as
`safeFamilyPlanning`, letting catalog completeness impersonate item planning.
Remove the family, generator, closure/readback, dedicated smoke, and readiness
dependency together. Preserve consensus -> interpretation request -> objective
draft -> Mind adoption. Do not replace it with another per-item catalog dump.
Consensus Brief keeps its honest draft/unconverged semantics but no longer
proves them with substring presence. Preparation owns its typed consensus,
Imagination route, inputs, authority, and privacy closure; a malicious comment

Binary file not shown.

View file

@ -660,4 +660,4 @@ current_status:
- Service lifecycle receipt history is now event-only: `load_epiphany_cultmesh_daemon_service_lifecycle_receipts` filters out the `epiphany-local/daemon-service-lifecycle-receipt/latest` mirror, while `load_latest_epiphany_cultmesh_daemon_service_lifecycle_receipt` remains the latest-state reader. Focused unit test `service_lifecycle_receipt_history_excludes_latest_mirror` proves two per-receipt writes return exactly two history records and latest points at the second. Fresh smoke `verse-query-lifecycle-history-filter-smoke` and live overview/triage `local-20260618-145632-497-efac6f0d` / `local-20260618-145632-321-867947af` prove compact swarm sights still expose service lifecycle attention plus the present elevated runbook artifact without daemon pokes or service mutation. Do not use a broad unscoped cargo test filter for this check on Windows; it fans out across bin harnesses and hit a broken pipe during this pass.
- `epiphany-verse-query seed-compact` is the compact seed receipt for wrappers and read-only rites. The older `seed` command still prints the full local Verse context for explicit debugging, but compact wrapper modes now avoid full `seed`/final `query` readback after the combined overview proof exposed Windows debug stack overflow from full-context serialization pressure.
last_completed_repo_swarm_cut: Huginn live-fire has crossed the first real repo Body from Persona pressure to branch-local Hands commit and Soul/Mind closure, and now has repeatable closure and redacted-public-proof mouths. On `E:\Projects\Huginn` branch `epiphany/huginn/first-awakening`, `tools/epiphany_local_run.ps1 -Mode repo-persona-intake` accepted item `huginn-inspection-readback-livefire`, Weksa/Persona intake remained sealed, and `epiphany-work derive-plan` lowered it to model-authored safe family `repo.status_section` for `README.md` only. `tools/epiphany_local_run.ps1 -Mode repo-swarm-run` advanced four bounded pulses: run-from-plan, adopt-from-plan, execute-from-plan, and close-from-execute. Huginn commit `e9b07c38fceabbdc89ea35c2156326c80c0393a2` updated only `README.md`; closure receipt `.epiphany\work\work-close-huginn-inspection-readback-livefire.json` records status `closed`, Soul verdict `passed`, Mind state commit `repo-work-close-huginn-inspection-readback-livefire-mind-commit`, safe family `repo.status_section`, path scope `README.md`, Bifrost publication gate, and `privateStateExposed=false`. Verification also ran Huginn's TypeScript compiler through concrete Node path: `C:\Program Files\nodejs\node.exe E:\Projects\Huginn\node_modules\typescript\bin\tsc -p tsconfig.json` passed. Native verifier `epiphany-repo-livefire-closure-smoke --workspace E:\Projects\Huginn --item huginn-inspection-readback-livefire --expected-path README.md --expected-family repo.status_section --expected-gate awaiting-publication --expected-blocker bifrost-publication-missing` checks closure receipt, Mind map entry, overview gate/blocker, authority seals, and `git show` changed paths, returning `status=ok`, `soulVerdict=passed`, `publicationGate=Bifrost`, and `privateStateExposed=false`. Wrapper `tools/epiphany_local_run.ps1 -Mode repo-livefire-closure -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exposes the same read-only proof through the local operator mouth; artifact `local-20260621-190156-803-2f85ba15` printed commit, path, gate, blocker, Soul verdict, Mind commit receipt, and `privateStateExposed=False` without push, merge, publication, or target mutation. New wrapper `tools/epiphany_local_run.ps1 -Mode repo-work-public-proof -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exports the redacted proof bundle and repo-local Verse index without publishing; artifact `local-20260621-190645-345-4555b1dc` wrote `.epiphany\public\proof-bundles\repo-work-public-proof-huginn-inspection-readback-livefire.json`, proof id `repo-work-public-proof-huginn-inspection-readback-livefire`, SHA-256 `857545b199f3e37eb06c2e757e5cfc201958e46667bb1f8403fd333a22620f63`, nine artifact rows, zero publication rows, and `privateStateExposed=False`. swarm overview readback `local-20260621-190701-140-b9519ec6` sees the `REPO-WORK-PUBLIC-PROOF` row and action row from Huginn's repo-local Verse with the same SHA-256 while Bifrost publication remains missing. Launcher compact modes are now named compact operator-context modes instead of read-only modes, and `bifrost-public-proof` summaries print item, target public Verse, room, proof SHA-256, review receipts, and credit receipts so publication receipts are auditable without claiming upstream sync.
next_action: Continue the conceptual-substitution pass. Twenty high-authority closure families are typed and guarded. Direct source inventory reports 278 content.contains occurrences across thirteen remaining families. Workflow owns adoption, scheduling, work-order, and verification. Preparation owns Consensus Brief, Interpreter Brief, and Objective Draft with honest Imagination-to-Mind boundaries. Readiness routing remains Self-owned with independent reviewers and no local approval owner. Next dissect the sprawling planning brief rather than mechanically encoding its 95 substring checks; determine whether its safe-family matrix is one preparation contract or several authorities glued together. External governance should converge on tooling plus publication/accounting; operations retains policy/deployment. Provider chronology is explicitly external and guarded as arrival order. Continue auditing evidence/security mirrors and adapters for borrowed authority.
next_action: Execute the mapped Planning Brief deletion. repo.planning_brief has no candidate work-item records; it copies global candidate schema, safe-family catalog, closure policy, ladder, and gate doctrine into a per-item file, then safeFamilyPlanning readback lets catalog self-attestation impersonate actual planning. Remove the safe family, generator, closure arm, planning_brief_safe_family_readback, dedicated smoke, and readiness dependency in one authority cut. Preserve consensus -> interpretation request -> objective draft -> Mind adoption, and require any future plan artifact to contain actual candidates while referencing separately owned catalog/contracts. Twenty high-authority closure families remain typed; current direct source inventory before this deletion is 278 content.contains occurrences across thirteen families. External governance should converge on tooling plus publication/accounting; operations retains policy/deployment.