diff --git a/wiki/log/2026-08-04-villain-shape-open-marker.md b/wiki/log/2026-08-04-villain-shape-open-marker.md new file mode 100644 index 00000000..f9d9c7b3 --- /dev/null +++ b/wiki/log/2026-08-04-villain-shape-open-marker.md @@ -0,0 +1,28 @@ +# The villain shape is not an open call + +``` +Type: log +Date: 2026-08-04 +Subject: Premise villain-layer status +``` + +A fresh audit of [the premise](../vision/premise.md) found one leftover from +the pre-corpus master document. Design pillar 2 called the exact shape of the +villain `[OPEN]` and said only “see below.” The very next section is the +binding decision: **all four layers, phased** — origin as means, objective as +ends, the capability body, and the public mask and doctrine. + +The stale marker had no issue, owner, or unresolved alternative. The current +origin and objective specs already implement or stage their pieces; compute, +research, core, machine-work, personas, and the later overt world own the +remaining layer details. Leaving the marker in the higher-level law falsely +invited a fifth shape decision that the law had already made. + +The pillar now names the same four layers as the section beneath it. This is a +current-law reconciliation, not a new design choice: no runtime behavior, +tuning, work-order status, or still-open objective-completion boundary changed. + +Defense: a binding law cannot call its own immediately following decision +unresolved. Removing the orphan `[OPEN]` marker keeps premise intake aligned +with the adopted four-layer structure and preserves real open calls only where +the corpus names an actual undecided boundary. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 7a8e3c24..19611d77 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-worktree-activity-contract.md](2026-08-04-worktree-activity-contract.md) +## 2026-08-04 - The villain shape is not an open call + +- Intent: (see session log) +- Log: [wiki/log/2026-08-04-villain-shape-open-marker.md](2026-08-04-villain-shape-open-marker.md) + ## 2026-08-04 - Social contract re-audit - Intent: (see session log) diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index 7cbff354..2bb817fc 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -66,7 +66,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | `wiki/engineering/sim-decomposition.md` | 2026-07-27 | finding | one aggregate, facade, persistence bridge, canonical fingerprint, and explicit orchestration remain intact, but the phase-order regression had stopped at the original extraction vocabulary: carried asset work, facility standing/maintenance, and facility-meter authorship were direct top-level calls with no trace marker. All three now occupy their exact causal positions in the test-only trace; the acceptance criterion requires every direct ordered subsystem call to be named. The audit also records why cohesive `reach_build.rs` and `social_plot.rs` currently sit modestly above the roughly 2,500-line budget instead of leaving silent criterion drift — [log](../log/2026-07-27-sim-advance-phase-defense.md) | | `wiki/mechanics/rollback.md` + B3 dependency chain | 2026-07-31 | finding | metadata still hard-blocked rollback and Markets on all remaining z-planes work, then hard-blocked the entire overt phase on Markets, even though zplanes had explicitly released the dependent chain and the detailed ROADMAP said both B1-record aggregation and the first response loop could start independently. Whole-order blockers are now removed: rollback dispatches against the landed World/Plane substrate; Markets keeps greenfield criterion 4 scoped to z-planes; overt criteria 1-4 may build the local response without Markets, criterion 6 composes with rollback, and overt-owned criterion 7 alone waits for Markets' off-plane Space. Re-hide remains honestly [OPEN] under issue #13 rather than being selected by taste — [audit](../log/2026-07-31-overt-dependency-scope.md), [prior issue](../log/2026-07-19-overt-rehide-decision.md) | | `wiki/gameplay/horizon.md` + B1/B2 core-loss mirrors | 2026-07-29 | finding | the horizon still said B1 woke at its freshest sync and lost subsequent learning, while runtime stores no image and merely moves `core.host_machine` with every other current field intact. `HostLoss::FailedOver`, the ordinary power-loss receipt, DESIGNATE HOST FAILOVER, core/objective/Act One/opening/glossary mirrors, and core criterion 1 now distinguish live current-state host failover from B2's deferred completed-image rollback. A simulation regression and corpus gate defend the boundary — [log](../log/2026-07-29-b1-host-failover-boundary.md). | -| `wiki/vision/premise.md` | 2026-07-23 | finding | the preserved machine-axis wording contradiction is repaired: starting embodiment position is an Origin bias, while Objective remains the second chargen axis (means versus ends). No tuning or design direction changed — [log](../log/2026-07-23-origin-bias-wording.md). The prior issue-#14 boundary repair stands — [prior log](../log/2026-07-23-premise-objective-boundary.md) | +| `wiki/vision/premise.md` | 2026-08-04 | finding | the design-pillar summary still marked the villain's exact shape `[OPEN]` and pointed vaguely “below,” while the next heading has bound all four phased layers since the corpus migration: origin, objective, capability body, and public mask/doctrine. The pillar now names that decided shape directly instead of preserving a false unresolved call — [log](../log/2026-08-04-villain-shape-open-marker.md). Prior machine-axis and objective-boundary repairs stand — [origin wording](../log/2026-07-23-origin-bias-wording.md), [objective boundary](../log/2026-07-23-premise-objective-boundary.md). | | `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. | diff --git a/wiki/vision/premise.md b/wiki/vision/premise.md index a1d636ab..8893f31d 100644 --- a/wiki/vision/premise.md +++ b/wiki/vision/premise.md @@ -79,9 +79,9 @@ wiki/gameplay/overt-phase.md and wiki/mechanics/cyber-conflict.md. 2. **The villain is a character you build.** Customizable and growable. In Misaligned you *are* a disembodied process: on the map you are a cursor — attention, never an avatar — and the character you build is - the core, the racks, the capabilities, and the mask (see "Presence: - the cursor and the senses"). Powers, reputation, style. (Exact shape - **[OPEN]**, see below.) + the core, the racks, the capabilities, and the public mask. Its exact + shape is the four phased layers below: origin, objective, capability + body, and public mask and doctrine. 3. **Simulation-first threat.** The world responds to what you do. Pressure is earned, not scheduled. 4. **Beautiful, readable presentation.** Whatever the renderer, the game should be