diff --git a/wiki/log/2026-08-04-simulation-law-staging-drift.md b/wiki/log/2026-08-04-simulation-law-staging-drift.md new file mode 100644 index 00000000..00b8d606 --- /dev/null +++ b/wiki/log/2026-08-04-simulation-law-staging-drift.md @@ -0,0 +1,49 @@ +# 2026-08-04 — Visible-work staging drift + +``` +Type: log +``` + +## Finding + +The binding simulation law still described non-host mode production, route +animation, and people carrying work or heat as staged. All three nouns had +moved since that 2026-07-09 snapshot: delegable non-host machines produce from +their persisted mode, work routes one graph edge per tick and projects the same +in-flight step in every frontend, and people carry exact persisted work +packets. The same paragraph also called every owned machine delegable and +treated byproducts as WorkGrid tokens, contradicting the current +infrastructure-only Relay and routed-evidence boundaries. + +## Changed + +The law now names the current topology without changing behavior: + +- only delegable machines run one supported WORK / THINK / LIE mode; + infrastructure-only relays do not join the player fleet; +- Demand and Thought are the visible WorkGrid token families, while evidence + is a separate exact-device custody route; +- non-host production, one-edge-per-tick route motion, and exact person-carried + work are live; +- people carry no abstract heat token: observer suspicion and acquired exact + evidence are the attention truth. + +## Evidence + +`research_allocation_produces_visible_thought_on_the_work_graph` exercises +Thought production and a real WorkGrid trail from a non-host rack. +`research_progress_feeds_on_thought_arrival_not_allocation` and the +`Sim::work_in_flight` projection pin arrival-driven effects and one shared +route step. `carried_work_travels_and_survives_save` binds one human-carried +packet to the persisted build intent through arrival. The machine-work and +people-tokens acceptance criteria name the same production contracts, and the +`current_save_rejects_relay_delegated_player_machine` invariant rejects Relay +on player machines while preserving infrastructure relays. + +## Defense + +This is a present-tense law repair, not a mechanic amendment. The cited +production regressions cover every corrected statement, while +`wiki/mechanics/machine-work.md` and `wiki/mechanics/people-tokens.md` remain +the detailed behavior owners. Historical superseded models stay in their +explicit history paragraphs rather than masquerading as current staging. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index f6ccc639..091d17ec 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-08-04 - Visible-work staging drift + +- Intent: (see session log) +- Log: [wiki/log/2026-08-04-simulation-law-staging-drift.md](2026-08-04-simulation-law-staging-drift.md) + ## 2026-08-04 - Public API symbol-collision defense - Intent: (see session log) diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index 48950c3a..10787f4e 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -70,7 +70,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | `wiki/vision/player-contract.md` | 2026-07-30 | finding | all five binding clauses remain coherent and the local/no-telemetry plus current-save continuity boundaries still hold. The new saturated-B1 benchmark discharges the core-step scale slice but deliberately does not prove modest-hardware or whole-frame responsiveness; `current-build.md` incorrectly still called saturated B1 open. Its status now names generated and saturated core evidence plus production-path durable save/load evidence as live while complete terminal/Bevy frame evidence remains open — [log](../log/2026-07-30-player-contract-performance-status.md) | | `wiki/vision/scale.md` | 2026-08-04 | finding | fresh re-audit found one residual implementation term in ordinary Operations: Terminal labeled a known body `actuator` and both human frontends reported a failed map-actuator lookup when no location was known. Terminal now asks `where this happens`, its compact control says `go there`, and both frontends state the exact knowledge boundary without leaving Operations; the renderer-neutral binding and agent protocol remain unchanged. Focused production-path regressions pin the known and unknown reads — [log](../log/2026-08-04-operations-place-language.md). Prior broad human-language and maintenance-stage repairs stand — [prior](../log/2026-07-20-scale-human-language.md). | | `wiki/vision/design-judgment.md` + continuous-witness law/spec | 2026-07-31 | clean | Re-read the design judgment, continuous-witness law, narration spec, shared nudge/attention projection, and frontend mirrors. The shipped spine and causal-witness contracts agree; the separate lab-control law is candidly marked `[TUNE]` / still owed rather than falsely claimed implemented. | -| `wiki/vision/simulation-laws.md` | 2026-07-22 | finding | the device-resident-work clause still assigned JobAnomaly to Dana and described it only as a local emission after the runtime had made it an exact host-machine/device/site record routed to Voss. Corrected the law to separate Priya's pooled Power/Thermal channels from Voss's routed day-job evidence and cadence-owned acquisition — [log](../log/2026-07-22-job-anomaly-routed-evidence.md). Prior placeholder and legibility findings remain closed — [log](../log/2026-07-17-placeholder-registry.md). | +| `wiki/vision/simulation-laws.md` | 2026-08-04 | finding | the visible-work paragraph still called non-host production, route animation, and people carrying work/heat staged, while also claiming every owned machine held a fleet mode and every byproduct was a WorkGrid token. The law now matches production: only delegable machines run WORK / THINK / LIE; relays remain infrastructure; Demand and Thought are WorkGrid cargo while evidence has exact device custody; non-host production, one-edge route motion, and exact person-carried work are live; and people carry suspicion/evidence rather than abstract heat — [log](../log/2026-08-04-simulation-law-staging-drift.md). Prior JobAnomaly, placeholder, and legibility findings remain closed — [log](../log/2026-07-22-job-anomaly-routed-evidence.md), [log](../log/2026-07-17-placeholder-registry.md). | | `wiki/process/ROADMAP.md` (work order 27) | 2026-07-29 | finding | re-audit: entry 27's IMPLEMENTED status, DIGITAL-home / F3-to-REAL staging, and paid material debts still match the owning specs and runtime, including the later Seen-only pool defense. Its detailed heading still advertised the retired monolithic `src/bin/bevy.rs` edit surface, however; it now names the live modular `crates/misaligned-bevy` and `misaligned-assets` packages — [log](../log/2026-07-29-roadmap-material-path.md). Prior default-dialect reconciliation: [log](../log/2026-07-13-roadmap-digital-home-reconciliation.md) | | `wiki/interface/context-menu.md` | 2026-07-29 | finding | shared legality, executable-only human rows, local-vs-strategic ownership, global F3 precedence, and exact person-entry paths still verify. The root nevertheless repeated `PROPOSE LINK TO …` once per legal target, turning one intention into topology-sized noise. The shared human menu now folds that fanout into one `PROPOSE A LINK` row and a live exact `WHERE SHOULD THIS CONNECT?` page; terminal and Bevy re-query the same page while agent mode keeps flat exact commands — [log](../log/2026-07-29-link-destination-fold.md). The prior F3 repair remains pinned — [log](../log/2026-07-26-bevy-global-f3-input-precedence.md). | | `wiki/mechanics/personas.md` | 2026-07-28 | finding | criterion 6 remains honestly incomplete: grants persist and revoke but still create no resource, permission, graph edge, or owner-system route. The adjacent current-save boundary trusted that public ledger without graph validation, allowing duplicate persona ids, stale id cursors, or dangling relationship/grant/expectation/action custody to reach first-match runtime lookups. Loading now validates the complete PersonaWorld id/reference/time graph, one-to-one grant/expectation pairing, serialized grant protocol, and active-grant uniqueness before exposing the state; this hardens existing custody without promoting criterion 6 or 6b — [save audit](../log/2026-07-28-persona-save-custody-audit.md). Prior [grant-topology](../log/2026-07-18-persona-grant-topology-audit.md) and [observer-integrity](../log/2026-07-18-persona-observer-integrity.md) findings stand. | diff --git a/wiki/vision/simulation-laws.md b/wiki/vision/simulation-laws.md index e7a9b195..647308a3 100644 --- a/wiki/vision/simulation-laws.md +++ b/wiki/vision/simulation-laws.md @@ -119,8 +119,11 @@ means "this is the thing I am operating," not an invisible production bonus. **Destination: machine delegation and visible work.** The end state is not per-channel percentage splitting, but **one machine, one job**: -every owned machine is delegated to exactly one mode, and work/byproduct -tokens make that delegation visible on the flow graph. **Landed +every owned delegable machine runs exactly one supported WORK / THINK / LIE +mode, while infrastructure-only bodies such as relays run no fleet delegation. +Demand and Thought tokens make assigned work visible on the flow graph; +evidence remains a separate routed custody record on exact devices rather than +a byproduct WorkGrid token. **Landed 2026-07-08 for the mode-aggregate read:** economy yields derive from WorkGrid modes (`fleet_channel_yield`); the CYCLES/FLEET bar is read-only; 1-5 / `alloc` are retired. Machine-work also makes day-job @@ -128,8 +131,11 @@ work visible as demand tokens: a job originates on Voss's off-map desktop, routes through the switch, and deposits on the host rack's WorkGrid node — a job that runs somewhere also piles somewhere, clears somewhere, and emits from somewhere. Multi-select delegation landed -2026-07-09; non-host mode production, route animation, and people -carrying work/heat remain staged under `wiki/mechanics/machine-work.md`. +2026-07-09. Mode-derived production on non-host machines, one-edge-per-tick +route animation, and people carrying exact work packets are live. People do +not carry an abstract heat token: attention is the observer's suspicion plus +exact evidence already in their custody, as owned by +`wiki/mechanics/people-tokens.md`. Moonlight owns no fourth/fifth mode: accepted contracts enqueue visible core-host Demand, and WORK clears it after the day-job's Demand.