diff --git a/wiki/interface/material-dark-frame.md b/wiki/interface/material-dark-frame.md index e04d4b0b..5d19e1ce 100644 --- a/wiki/interface/material-dark-frame.md +++ b/wiki/interface/material-dark-frame.md @@ -24,7 +24,7 @@ Status note: IMPLEMENTED — all six criteria, frontend-only (no sim rules or camera feed covering the core bleaches that amber source to white, then contracts it into the circular instrument as the chassis resolves — a local sub-second payoff, never a global fog-off flash. The camera anchors - to attention at close range (zoom bounds 0.5-6.0). + to attention at close range (zoom bounds 0.7-5.2). - **Cold-signal ember.** A known reachable sensor on an Unknown tile carries a pre-sight abstract ember at its anchor — one tiny irregularly breathing point, not a device body. Seen replaces it with physical form; Remembered diff --git a/wiki/log/2026-08-04-material-dark-frame-zoom-bounds.md b/wiki/log/2026-08-04-material-dark-frame-zoom-bounds.md new file mode 100644 index 00000000..e5669725 --- /dev/null +++ b/wiki/log/2026-08-04-material-dark-frame-zoom-bounds.md @@ -0,0 +1,32 @@ +# 2026-08-04 — Keep the dark frame inside its played zoom + +``` +Type: log +``` + +## Finding + +The dark-frame implementation status still named the original 0.5–6.0 camera +zoom range. Production was deliberately retuned to 0.7–5.2 on 2026-07-14 so +the close frame remains intimate and the wide frame still keeps the room's +material hierarchy legible. `MIN_ZOOM`, `MAX_ZOOM`, their focused assertions, +and the dependent clinical-frame contract all held the played range. + +## Change + +The dark-frame status now names 0.7–5.2. No camera, input, simulation, save, or +rendering behavior changed. + +## Verification + +- `MIN_ZOOM` is `0.7` and `MAX_ZOOM` is `5.2` in the Bevy frontend. +- `zoom_steps_move_in_both_directions_and_clamp` pins both constants and their + clamp behavior. +- `clinical-frame.md` independently names the same bounded range. +- `./tools/check.sh --docs` + +## Defense + +One binding status value now matches the implementation constant pair, focused +clamp test, and dependent frame contract. The correction preserves the played +composition rather than changing it to satisfy stale prose. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 9678d161..070bd141 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -16,6 +16,11 @@ add or amend a session log, then re-run the generator. - Intent: (see session log) - Log: [wiki/log/2026-08-04-operations-place-language.md](2026-08-04-operations-place-language.md) +## 2026-08-04 - Keep the dark frame inside its played zoom + +- Intent: (see session log) +- Log: [wiki/log/2026-08-04-material-dark-frame-zoom-bounds.md](2026-08-04-material-dark-frame-zoom-bounds.md) + ## 2026-08-04 - Carry the hall light rhythm to its full length - Intent: (see session log) diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index b88d8edf..c99f34a7 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -44,7 +44,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | `wiki/interface/superhuman-operability.md` + Bevy opening | 2026-07-22 | finding | current-build naive + informed GUI audit after the 2026-07-21 fixes: title trust, pointer naming, annotation placement, and tab labels improved, but the first sense still releases the mature map, clock, threat, resource grammar, intel custody, and Operations policies at once. The report preserves the classified evidence and prioritizes one paused, one-cause / one-object / one-verb post-perception teaching lock before ordinary play opens - [report](../playtests/2026-07-22-playtest-gui-human-legibility.md), [log](../log/2026-07-22-gui-human-legibility-playtest.md) | | `wiki/process/living-spec.md` no-dead-code + core orphans | 2026-07-21 | finding | user-directed dead-code hunt: rustc was quiet because orphans were `pub`. Deleted unused `BuildMode`/`build_items`/`build_cost`, orphaned helpers (`delete_save`, `adjust_allocation`, `sell_latest_intel`, scheme-card/rate helpers, `flow_risk_preview_lines`, unused account/origin/intent/message helpers), and migration-only `WatchPerson`; architecture/economy/sim-mechanics mirrors brought current — [log](../log/2026-07-21-dead-code-scrub.md) | | `wiki/world/characters/chargen.md` + picker composition | 2026-07-31 | finding | Cameron-directed: day-job kinds (Distillation / Analysis / Data Cleaning) and origin day-job lean never changed play — only a label on the same band/deadline packet. `JobKind`, lean draw, and the picker DAY JOB row are deleted; jobs are band+deadline only; save v63 — [log](../log/2026-07-31-retire-dayjob-kinds.md). Prior explicit-confirm repair stands — [prior](../log/2026-07-31-origin-picker-explicit-confirm.md). | -| `wiki/interface/material-dark-frame.md` | 2026-08-04 | finding | the 2026-07-26 hall expansion deliberately extended the production fixture roster to thirty lights—ten down each of three aisles—and pinned that exact shape in runtime tests, but the owning dark-rig contract still promised the earlier eighteen/six-per-aisle composition. The binding status and behavior now match the executable roster, and a Defense names the shared roster/fog audit that holds count and local-Seen custody. Prior opening-boundary repair stands — [current log](../log/2026-08-04-material-dark-frame-fixture-count.md), [prior log](../log/2026-07-21-material-opening-honesty.md) | +| `wiki/interface/material-dark-frame.md` | 2026-08-04 | finding | two stale status mirrors survived deliberate played-scale retunes: the 2026-07-26 hall expansion extended the production fixture roster to thirty lights—ten down each of three aisles—while the page still promised eighteen/six; the 2026-07-14 camera retune narrowed the actual and tested zoom range to 0.7–5.2 while the page still promised 0.5–6.0. Both binding values now match their executable rosters/constants and focused defenses. Prior opening-boundary repair stands — [fixture-count log](../log/2026-08-04-material-dark-frame-fixture-count.md), [zoom-bounds log](../log/2026-08-04-material-dark-frame-zoom-bounds.md), [prior log](../log/2026-07-21-material-opening-honesty.md) | | wire-law + routed-evidence visual/current mirrors | 2026-07-30 | finding | post-landing sweep of active current prose found eight residual contradictions after the machine-local Exposure rack was deleted: one three-anchor claim, THINK shedding crimson, LIE absorbing it, Thought overflow framed as shedding, far-scale exposure marks, and three stale save-v52 status notes. Current mirrors now name Demand/Thought as the only WorkGrid cargo, exact device/wire custody for evidence, controlled-hop record stops, and save v61; dated retired-model history remains intact — [secondary audit](../log/2026-07-30-wire-law-secondary-mirror-audit.md), [implementation log](../log/2026-07-30-wire-law-current-mirrors.md), [prior particulate audit](../log/2026-07-19-exposure-current-mirrors.md) | | `wiki/world/characters/priya.md` + Act One detection inventory | 2026-07-29 | finding | runtime, status metadata, and the observer table all gave Priya the exact B1 Power/Thermal/Paper/Financial evidence set, but her narrative, acceptance criterion, and Act One's complete detection sentence still omitted Financial and called the inventory three channels. All mirrors now distinguish the three facilities inputs from the additional exact Financial evidence routed from the accounting-carrier switch, without reviving Financial as a fifth message channel — [audit log](../log/2026-07-29-priya-financial-channel-audit.md). The role-shaped facilities tasks and prior implementation remain pinned — [implementation log](../log/2026-07-18-priya-implemented.md). | | `wiki/world/characters/dana.md` | 2026-07-29 | finding | fresh audit found the character page claiming an 08:00 start while the binding schedules spec and `People::act_one` place Dana on site 09:00–17:00; it also retained pooled-signature/roll wording after one-shot Network evidence moved to exact routed custody. Both schedule mirrors now match runtime, the exact 08:00/09:00/13:00/17:00 boundary is pinned, and the page plus role-shaped PlugInDevice comments distinguish delivery from Dana's later irreversible cadence read — [log](../log/2026-07-29-dana-schedule-record-custody.md). Prior implementation stands — [2026-07-18](../log/2026-07-18-dana-implemented.md). |