From 7bad89a25da1d631e7a336a9ac3d3ef6a84c742a Mon Sep 17 00:00:00 2001 From: Cameron Pfiffer Date: Mon, 27 Jul 2026 19:13:00 -0700 Subject: [PATCH] Keep the repository doorway current. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code --- README.md | 9 ++- wiki/log/2026-07-28-readme-b1-status-audit.md | 62 +++++++++++++++++++ wiki/log/DEVLOG.md | 5 ++ wiki/process/tick-ledger.md | 6 +- 4 files changed, 77 insertions(+), 5 deletions(-) create mode 100644 wiki/log/2026-07-28-readme-b1-status-audit.md diff --git a/README.md b/README.md index 1c461983..71c07679 100644 --- a/README.md +++ b/README.md @@ -98,9 +98,12 @@ production/consumption/absorption, researched Routing, and target-local Thought reservoirs all run through one flow substrate. The retired Operations docket executor is absent from both runtime and the current save schema. People now project as schedule-bound carriers; builds and physical asset tasks travel -with their selected person and act only on arrival. Remaining B1 work includes routed -human evidence, LIE interdiction, interface cover channels, the dark opening, -and digital/real canvas polish; core completion waits on rollback. B2/B3 +with their selected person and act only on arrival. All seven routed evidence +kinds, route-local LIE interdiction, interface-bound cover, the blind opening +and five-step first-sense hold, and the DIGITAL / REAL dialects are live. The +dark-opening spec remains DRAFT for its failed-pilot prelude and later teaching +arc, and core completion waits on rollback. Exact unfinished work lives on the +generated dispatch board rather than in this fast-moving summary. B2/B3 systems are specified ahead but remain staged. Under the corpus's no-dead-code rule, the earlier facility-defense prototype lives only in git history. diff --git a/wiki/log/2026-07-28-readme-b1-status-audit.md b/wiki/log/2026-07-28-readme-b1-status-audit.md new file mode 100644 index 00000000..d9540337 --- /dev/null +++ b/wiki/log/2026-07-28-readme-b1-status-audit.md @@ -0,0 +1,62 @@ +# README B1 status follows the implemented slice + +``` +Type: log +``` + +## Finding + +The repository entry README still named routed human evidence, LIE +interdiction, interface cover, the dark opening, and DIGITAL / REAL canvas +polish as one undifferentiated block of remaining B1 work. That status had not +followed the intervening implementation: every current B1 evidence kind now +has exact custody, all seven share route-local first-hop LIE capacity, +interface-bound cover is implemented, the persisted blind opening and Bevy's +five-step first-sense hold are live, and both frontend dialects satisfy their +binding acceptance criteria. + +The old sentence also hid the real residual boundary inside “the dark +opening.” The current wake is implemented; the DRAFT spec still owes its +failed-pilot prelude and later teaching arc. Core completion separately remains +blocked on rollback. + +The audit also found the same drift in the tick ledger's people-tokens coverage +row: it still said criterion 6 remained open after the 2026-07-26 +interface-cover landing completed that work order. The owning spec, runtime +trace, and generated dispatch board already agreed that it is implemented. + +## Repair + +The README now names the implemented evidence, cover, opening, teaching, and +representation boundaries directly. It states the exact opening work that +remains instead of presenting the entire feature as absent, preserves the real +core blocker, and makes the generated dispatch board the sole current inventory +of unfinished work rather than maintaining another fast-rotting queue in the +repository doorway. + +The people-tokens coverage row now records the exact interface-cover +implementation and preserves its prior routed-evidence history. + +The rest of the repository doorway still resolves correctly: `AGENT.md`, +`AGENTS.md`, and `DESIGN.md` point into the current corpus and direct-main +workflow, and Cargo metadata confirms that every documented run command names +an unambiguous live binary. The controls still match the canonical keymap, but +the README's `q` row is separated from its Markdown table by prose. That +presentation defect is queued for a later tick rather than widening this one. + +## Defense + +The README is a compact public and contributor entry point, not a second status +database. It may summarize stable completed boundaries, but the generated +dispatch board owns the live unfinished set. This keeps the doorway honest +without forcing every landing to reconcile a duplicated priority list. + +## Verification + +- compared the corrected status with `wiki/engineering/current-build.md`; +- re-read the IMPLEMENTED people-tokens and views acceptance criteria; +- separated the live blind opening and first-sense hold from the remaining + DRAFT failed-pilot and later-teaching work in `wiki/world/story/opening.md`; +- resolved README run commands against `cargo metadata --no-deps`; +- compared the documented controls with the canonical keymap and production + terminal/Bevy input paths, then queued the detached `q` row as surplus. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 1a319313..0308a069 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -11,6 +11,11 @@ add or amend a session log, then re-run the generator. +## 2026-07-28 - README B1 status follows the implemented slice + +- Intent: (see session log) +- Log: [wiki/log/2026-07-28-readme-b1-status-audit.md](2026-07-28-readme-b1-status-audit.md) + ## 2026-07-28 - Continuous-witness five-step audit - Intent: (see session log) diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index d0609934..2d14dd7b 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -76,8 +76,8 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | `wiki/mechanics/income.md` | 2026-07-18 | finding | Beacon feel note 5 verified as a real bug: the embedded contractor-persona field was never written, so the Moonlight card, the start-row persona pricing, and the agent status line all read a dead `None`; earning itself was correct (schemes mirrors the WORK share) but illegible at 0.0. Removed the dead field, routed every reader through `Sim::moonlight_persona` (persona-world link), added the stalled-earning card cue, regression test, and spec amendment — [log](../log/2026-07-18-moonlight-persona-card.md). Prior Wager/egress audit (2026-07-12) stands: Wager constants match (`WAGER_STAKE_CAP` 300, base 0.55, cap 0.75, mult 2x, analysis divisor 400), Marcus's $400/week arrears is the modeled creditor flow (`account.rs`) while the $8,400 principal is narrative-by-design (spec states full payoff is not a B1 requirement), egress/banked-signature present, and all 7 criteria have passing tests (moonlight payout/signature, wager outcomes/cap, egress routes, hands-beat-from-zero, busted-bankroll) | | `wiki/mechanics/schedules.md` | 2026-07-27 | finding | the location gate still works—at 03:00 server-room Marcus acquires the act while off-site Priya does not—but the owning spec still called witnessed work a Physical signature and omitted the exact person-local evidence record, no-pending-copy rule, filing custody, and actor exclusion. It also called implemented Operations PEOPLE a future READY migration. The spec now names the shipped `ObserverEvidence` boundary and current surface; runtime is unchanged — [log](../log/2026-07-27-schedules-evidence-custody.md) | | `wiki/mechanics/social.md` | 2026-07-22 | finding | HandlerSupervisor SuppressLogs now targets the oldest exact unread routed JobAnomaly, remains available only while such a record exists, removes its bound advance/read event, and preserves exact handler/tick provenance; it cannot erase a record Voss already read. The in-flight Thought request still revalidates at fire time, so another intervention may win without inventing work — [log](../log/2026-07-22-job-anomaly-routed-evidence.md). Storage B retrieval and prior role-shaped task semantics stand — [log](../log/2026-07-21-storage-b-records.md). | -| `wiki/mechanics/people-tokens.md` | 2026-07-23 | finding | Power and Thermal now complete criteria 2 and 3 for every current B1 evidence kind: standing loads aggregate on quantized level changes and periodically at Priya's cadence into exact UPS/HVAC meter records, retain all contributing source sites, route through the institutional switch, and become evidence only on her later cadence read. They never enter the ambient pending pool and share Filing/Network/Paper/Financial/JobAnomaly's first-hop TAKE+LIE body budget. Save v54 pins meter, source-site, recipient, route, scheduler, read, and stop custody — [log](../log/2026-07-23-power-thermal-meter-routes.md). Criterion 6 remains open only for interface cover records. Prior [Paper](../log/2026-07-23-paper-evidence-route.md), [Financial](../log/2026-07-23-financial-evidence-route.md), [JobAnomaly](../log/2026-07-22-job-anomaly-routed-evidence.md), [Network](../log/2026-07-19-network-evidence-route.md), and [mark](../log/2026-07-19-evidence-marks-on-people.md) slices stand. | -| repository entry docs (`README.md` + `AGENTS.md`) | 2026-07-18 | finding | re-audit: run commands, controls, dispatch status, and the number-free AGENTS doorway still verify; the queued contradiction was real — README's compact-rest paragraph claimed the ops/sec crown and FOCUS stayed visible, while the implemented clinical frame puts both behind deliberate `Tab` expansion. The entry copy now names the exact compact spine and expanded detail boundary — [prior log](../log/2026-07-12-entry-doc-current-state.md) | +| `wiki/mechanics/people-tokens.md` | 2026-07-28 | finding | re-audit: criteria 2-3 still bind seven exact routed kinds—Filing, Network, Paper, Financial, JobAnomaly, Power, and Thermal—to one shared first-hop TAKE+LIE body budget, while acquired Physical evidence remains irreversible observer-local custody. The stale ledger claim that criterion 6 was open is repaired: one exact pending record may now receive cover only through co-location with one controlled people-facing interface and an eligible observer-local persona; the attempt adjusts credibility rather than deleting evidence, wears that interface, and persists exact incident/interface/persona/outcome custody in save v56. The people-tokens work order is IMPLEMENTED — [cover log](../log/2026-07-26-interface-cover-evidence-credibility.md); [audit log](../log/2026-07-28-readme-b1-status-audit.md). Prior [Power/Thermal](../log/2026-07-23-power-thermal-meter-routes.md), [Paper](../log/2026-07-23-paper-evidence-route.md), [Financial](../log/2026-07-23-financial-evidence-route.md), [JobAnomaly](../log/2026-07-22-job-anomaly-routed-evidence.md), [Network](../log/2026-07-19-network-evidence-route.md), and [mark](../log/2026-07-19-evidence-marks-on-people.md) slices stand. | +| repository entry docs (`README.md` + `AGENTS.md`) | 2026-07-28 | finding | re-audit: README's unfinished-work sentence had fallen behind five completed boundaries and still called routed human evidence, LIE interdiction, interface cover, the dark opening, and DIGITAL / REAL canvas polish collectively absent. It now names exact seven-kind evidence custody, route-local LIE capacity, interface-bound cover, the live blind opening and five-step first-sense hold, and the completed representation dialects; the failed-pilot prelude, later teaching arc, and rollback blocker remain explicit, while the generated dispatch board alone owns the fast-moving unfinished inventory — [log](../log/2026-07-28-readme-b1-status-audit.md). Prior compact-rest repair: [log](../log/2026-07-12-entry-doc-current-state.md). | | `wiki/mechanics/objective.md` | 2026-07-27 | clean | decision-harvest re-audit: only `Persist` remains implemented; the evaluator, save round trip, own-unit progress, full predicate projection, and agent `objective` route still verify. Criterion 2 now states Cameron's selected timing and is pinned at the frontend boundaries: no pre-sense objective, name/progress on terminal and agent's first ordinary Ears frame, and Bevy ordinary core-focus projection after its separate binding teaching hold. Progressive predicate teaching remains the outstanding criterion-6 dispatch — [log](../log/2026-07-27-objective-first-display.md) | | `wiki/mechanics/compute.md` | 2026-07-22 | finding | the live fleet already derived every channel yield from exact WorkGrid modes, but `Compute` still serialized an unreachable five-weight allocation object and retained bump/split helpers plus persistence pins. Save v48 removes that parallel authority, moves criterion 2 to persisted delegation/intensity, and leaves aggregate channel bars as read-only projections — [log](../log/2026-07-22-allocation-state-retirement.md) | | retired Operations runtime identifiers | 2026-07-27 | clean | re-audit: `submit_ops_job`, `OperationsState`, `PendingOpsJob`, `OpsJobKind`, `LegacyOperationsState`, and `AddressedOperation` remain absent from live Rust; the only retired save-field spellings are negative assertions in the current round-trip guard, and the machine-mode guard still rejects serialized `Operations`. The corpus gate passes, while remaining lower-case `operations` uses are the legitimate persona archetype, workspace, or compatibility input alias — [log](../log/2026-07-11-retired-runtime-identifier-gate.md) | @@ -103,3 +103,5 @@ 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-28 · bug · `README.md` controls table · the canonical `q` / Quit row is stranded below the explanatory paragraph instead of rendering inside the controls table -- 2.51.2