diff --git a/wiki/log/2026-07-27-opening-ledger-status-reconciliation.md b/wiki/log/2026-07-27-opening-ledger-status-reconciliation.md new file mode 100644 index 00000000..1dab217b --- /dev/null +++ b/wiki/log/2026-07-27-opening-ledger-status-reconciliation.md @@ -0,0 +1,51 @@ +# The opening coverage trace follows the corrected frame + +``` +Type: log +Date: 2026-07-27 +Status: COMPLETE +``` + +## Intake + +The tick brief still surfaced decision-made issues #14 and #15 first. Both +answers are already converted into the binding corpus and runtime. A live +attempt to close #14 failed before mutation because `tg` could not unlock the +login keyring, so the converted issues remain visible as an authentication +blocker rather than being treated as fresh design work. + +The findings queue then supplied one recorded contradiction in the tick ledger. + +## Finding + +**Contradiction.** The opening coverage row still described the first issue-#15 +implementation as current: renderer-neutral sparse interoception plus a +frontend-local input echo. Fire #33 had already removed +`OpeningInteroception`, its `Sim::opening_interoception` producer, and the +standing SENSES / DELEGATION / THOUGHT / EARS block after Cameron rejected the +composed result. + +The current contract is narrower. Before perception, WORK / THINK (then LIE) +are the only standing copy. Each attempted input receives one terse +frontend-local echo. No self-state, parser help, or world knowledge appears. +The binding opening and its dependent interface, roadmap, test, and corpus-gate +mirrors already stated that corrected boundary; only the audit ledger was +stale. + +## Act + +The coverage row now names the corrected Fire #33 boundary and links both the +runtime correction and this reconciliation. The consumed findings-queue line +is removed. No law, runtime, or player surface changed. + +## Defense + +`wiki/world/story/opening.md` owns the blind pre-sense frame and explicitly +removes the superseded self-state projection. The audit ledger must describe +that current contract rather than preserving an earlier implementation as +present truth; the dated boot-voice log remains available as history. + +## Left open + +- Close Tangled issues #14 and #15 when authenticated `tg` can unlock its + keyring. Their decisions are already fully harvested. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 633a8edb..1e6ea44d 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -71,6 +71,11 @@ add or amend a session log, then re-run the generator. - Intent: (see session log) - Log: [wiki/log/2026-07-27-room-approaches-meet-doors.md](2026-07-27-room-approaches-meet-doors.md) +## 2026-07-27 - The opening coverage trace follows the corrected frame + +- Intent: (see session log) +- Log: [wiki/log/2026-07-27-opening-ledger-status-reconciliation.md](2026-07-27-opening-ledger-status-reconciliation.md) + ## 2026-07-27 - Opening boot voice implemented - Intent: (see session log) diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index 541ede1a..99f26b15 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -21,7 +21,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | Slice | Last audited | Verdict | Trace | |---|---|---|---| | `wiki/interface/terminal-first.md` temporal visibility | 2026-07-27 | finding | first audit against the persisted earned-perception opening found the law still required day and tick “always,” while the binding opening, terminal spec, agent protocol, production render boundary, and tests deliberately expose only available mode words plus one terse input echo before the first sense. The law now scopes its clock promise to the perceived world and explicitly restores it on the sense-earning input; runtime was already correct — [log](../log/2026-07-27-terminal-first-opening-clock-boundary.md) | -| `wiki/world/story/opening.md` + boot-voice status mirrors | 2026-07-27 | finding | fresh audit after issue #15 option 1 shipped: `Sim::opening_interoception`, opening criterion 4, and all three frontends implement sparse shared interoception plus frontend-local input echo, but `narration.md` still said the pre-witness voice "remains unimplemented" / implementation debt and `digital-read.md` still listed it as debt. Both status notes now state implemented under opening.md without reopening the mature DIGITAL/witness spine — [log](../log/2026-07-27-boot-voice-status-honest.md). Issues #14/#15 remain open only for tracker close once `tg` auth unlocks. | +| `wiki/world/story/opening.md` + pre-sense status mirrors | 2026-07-27 | finding | the issue-#15 boot-voice implementation was superseded after Cameron saw the composed frame: Fire #33 removed `Sim::opening_interoception` and the standing SENSES / DELEGATION / THOUGHT / EARS block, leaving WORK / THINK (then LIE) plus one frontend-local input echo as the complete pre-sense surface. The opening, narration, DIGITAL, terminal, Bevy, agent, witness, objective, roadmap, and corpus-defense mirrors already carried that correction; this follow-up repairs the coverage row that still described the rejected implementation — [runtime correction](../log/2026-07-27-blind-opening-choice-and-receipt.md), [ledger reconciliation](../log/2026-07-27-opening-ledger-status-reconciliation.md). Issues #14/#15 remain open only because authenticated `tg` closure cannot unlock the login keyring. | | `wiki/process/tick.md` + issue automation | 2026-07-27 | finding | the queued retired-client violation held across binding procedure, both skill mirrors, four active prompt templates, tick intake, project status, and doctor. `tools/tangled_issues.py` now keeps repository discovery and authenticated issue writes on canonical Go `tg`, reconstructs deterministic display numbers from public issue records, folds public label-op history, and provides fail-closed structured list/view/create/edit/comment/close/label operations. A same-day live harvest exposed one wrong record assumption: comments are cross-account `sh.tangled.feed.comment` records linked through `subject.uri`, not issue-local child records. The repaired helper follows that backlink into the author's PDS and returns the markup text; a fixture pins the exact shape, and live issue #15 now returns Cameron's choice `1` — [migration and repair log](../log/2026-07-27-tangled-issue-client-migration.md) | | `wiki/world/places/basement-map.md` room topology | 2026-07-27 | finding | the queued five non-hall corridor cuts remained, and an executable all-room perimeter audit exposed the same dead-door shape at the loading-dock entry plus fixed objects blocking the interior faces of the roll door, HVAC door, both storage doors, Janitor door, and stairwell. Every non-hall approach now reaches its authored door from outside the prefab, every other perimeter tile remains closed, doorway interiors are clear, and the roll, sealed, tier-2, and tier-3 boundaries retain their exact kinds — [room-approach log](../log/2026-07-27-room-approaches-meet-doors.md). Prior [west-approach](../log/2026-07-26-west-hall-approach.md) and [hall-density](../log/2026-07-26-foundation-hall-density.md) repairs stand. | | `wiki/mechanics/sensor-network.md` generated sensor population / criteria 1-5 | 2026-07-27 | finding | criterion-2's traveling rule still placed every generated room camera at the geometric center without checking the tile or another device, so a later prefab could silently put its physical body and sight origin inside a fixture. Room cameras now choose the nearest free ordinary Floor tile with deterministic ties; the toy lab carries a center bench and pins the fallback. The same audit corrected the stale criterion-1 test comment left after exact badge passage custody landed — [placement repair](../log/2026-07-27-room-camera-floor-placement.md), [passage implementation](../log/2026-07-27-badge-reader-passage-custody.md), [prior audit](../log/2026-07-27-sim-advance-phase-defense.md), [population foundation](../log/2026-07-27-sensor-population-foundation.md) | @@ -100,5 +100,3 @@ Format: `- YYYY-MM-DD · type · slice · one-line statement of the finding`. Types are the five from [tick.md](tick.md): violation, contradiction, question, bug, insecurity — plus `gate` for a checker owed to the recurrence-promotes-to-the-gate rule. - -- 2026-07-27 · contradiction · `wiki/process/tick-ledger.md` opening status · the opening coverage row still claims sparse shared interoception from issue #15 is implemented after Fire #33 removed that projection and restored mode words plus input echo as the complete pre-sense surface