From ded50f05d142ad40566b1c38998bb8d03189186d Mon Sep 17 00:00:00 2001 From: Cameron Date: Mon, 27 Jul 2026 01:05:29 -0700 Subject: [PATCH] Restore Territory to the guidance chain. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Document the shipped optional hall-row cue at its real priority so the binding narration contract no longer skips a live nudge rung. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code --- wiki/interface/narration.md | 16 +++++--- .../2026-07-27-territory-guidance-chain.md | 41 +++++++++++++++++++ wiki/log/DEVLOG.md | 5 +++ wiki/mechanics/sim-mechanics.md | 20 +++++---- wiki/process/tick-ledger.md | 9 +--- 5 files changed, 69 insertions(+), 22 deletions(-) create mode 100644 wiki/log/2026-07-27-territory-guidance-chain.md diff --git a/wiki/interface/narration.md b/wiki/interface/narration.md index 3ed7226d..00ae166d 100644 --- a/wiki/interface/narration.md +++ b/wiki/interface/narration.md @@ -133,12 +133,16 @@ when the one post-Ears camera TAP commits: progression: pilot 3/4 and Assurance cooling (Concerned+, suspicion still above floor) each name the recovery response before the next Act One rung. Once all quiet-exit conditions are live it names QUIET EXIT - READY; after the clear audit it persistently names ACT ONE COMPLETE and - points back to the continuing run objective. That completion state stands - in place of the Act One rungs it retires, but it is not a terminal - override: the same survival interrupts still outrank it, so a pilot at 3/4, - a starved or unreachable job band, and a cooling Assurance file keep - naming their recovery response after the boundary. + READY. Otherwise, after the required ladder is exhausted, an open Foundation + hall row names the shared `hall_territory_line`—the leading row and its exact + next blocker—before the bare Audit fallback. Territory is guided but optional: + it never outranks QUIET EXIT READY or delays the boundary. After the clear + audit the nudge persistently names ACT ONE COMPLETE and points back to the + continuing run objective. That completion state stands in place of the + required rungs, optional Territory cue, and Audit fallback it retires, but + it is not a terminal override: the same survival interrupts still outrank + it, so a pilot at 3/4, a starved or unreachable job band, and a cooling + Assurance file keep naming their recovery response after the boundary. - **Focused action** — the local context menu on the current spatial anchor or the selected semantic object in Operations (and the equivalent agent `actions` target). diff --git a/wiki/log/2026-07-27-territory-guidance-chain.md b/wiki/log/2026-07-27-territory-guidance-chain.md new file mode 100644 index 00000000..91c83475 --- /dev/null +++ b/wiki/log/2026-07-27-territory-guidance-chain.md @@ -0,0 +1,41 @@ +# Territory returns to the guidance chain + +``` +Type: log +``` + +## Finding + +This tick took the oldest findings-queue entry and compared both documented +`now:` chains with `Sim::current_nudge`, the `Nudge` enum, all three frontend +projections, the Foundation hall surface, and the binding Act One/building +clauses. + +The queued contradiction was still live. `Nudge::Territory` had shipped with +the hall-row discoverability work, below `QuietExitReady` and above the bare +`Audit` fallback, but neither complete chain mirror named it. The omission +made the corpus imply that the live cue was outside the shared narration +contract. + +## Amendment + +The two mirrors now state the existing exact priority: + +1. survival interrupts; +2. the required Act One ladder; +3. `QuietExitReady` when the complete required condition set is live; +4. otherwise, optional `Territory`, naming the leading row and its exact + blocker through `hall_territory_line`; +5. `Audit` only when no open territory remains. + +Territory remains guided, never required. It cannot outrank the quiet exit or +delay Act One completion; it only replaces the standing-clock nudge. A latched +`ActOneComplete` retires the required ladder, optional territory opportunity, +and fallback while still yielding to the run's survival interrupts. + +## Verification + +No runtime changed. The existing extended +`nudge_chain_walks_the_act_one_ladder` regression already proves Territory +appears after the required ladder, loses to `QuietExitReady`, and retires once +all hall rows are acquired. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index adeae0b5..543b85e5 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-27 - Territory returns to the guidance chain + +- Intent: (see session log) +- Log: [wiki/log/2026-07-27-territory-guidance-chain.md](2026-07-27-territory-guidance-chain.md) + ## 2026-07-27 - Tangled issue automation now runs through `tg` - Intent: (see session log) diff --git a/wiki/mechanics/sim-mechanics.md b/wiki/mechanics/sim-mechanics.md index 9353139e..8f43cff7 100644 --- a/wiki/mechanics/sim-mechanics.md +++ b/wiki/mechanics/sim-mechanics.md @@ -447,14 +447,18 @@ All constants [TUNE] in `crates/misaligned-core/src/income.rs` unless noted (Sim plot is ready or active), otherwise Income (the debt is unserviced, no plot is ready or active, and no accepted or delivered Halcyon contract is active) -> Recruit (serviced, not an asset) -> TheKey (an - asset has stairwell access the player lacks) -> Audit (the standing - countdown while another quiet-exit condition is absent) -> QuietExitReady - (the full condition set is live; hold it to the audit). Everything from - Eyes down is Act One progression, which is why the latched boundary sits - above it and retires it; the boundary is a standing state, not a terminal - override, so the survival rungs above it keep firing for the rest of the - run. The chain never goes blank mid-run. Each frontend - words the rungs in its own keys/verbs; `None` only after game over. + asset has stairwell access the player lacks) -> QuietExitReady (the full + condition set is live; hold it to the audit) -> Territory (otherwise, an + open Foundation hall row is an optional opportunity; name the leading row + and its exact blocker) -> Audit (the standing-countdown fallback once no + open territory remains). Everything from Eyes through TheKey is required + Act One progression. QuietExitReady names completion of that required set; + Territory is the guided-but-declinable post-ladder opportunity and can only + replace Audit. The latched boundary sits above all of them and retires them; + it is a standing state, not a terminal override, so the survival rungs above + it keep firing for the rest of the run. The chain never goes blank mid-run. + Each frontend words the rungs in its own keys/verbs; `None` only after game + over. - Ineffective commands answer (agent-play.md "every command answers"): `siphon`/`redirect` with a non-flow argument answer `-- err` naming where flow ids live. Debt routes live on Marcus's authored action rows. diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index 1acb7d5f..c728a90f 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -47,7 +47,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | `wiki/gameplay/act-one.md` | 2026-07-26 | finding | the first of the two defects the page recorded against the shipped quiet exit was real and run-losing: `current_nudge()` checked `act_one_complete` immediately after the game-over guard and returned unconditionally, so a latched act permanently suppressed PilotAtRisk, Underfed, NeedCompute, and SuspicionCooling — guidance went silent at the climax while the day job could still end the run. The completion cue now sits below the survival block and above the Act One ladder it genuinely retires (including QuietExitReady), matching the survival-first rationale already written in the function; `act-one.md`, `sim-mechanics.md`'s chain order, and `narration.md`'s beat-nudge contract all state that precedence, and a new ladder test walks a closed act through every survival rung — [log](../log/2026-07-26-act-one-complete-standing-state.md). The single-human predicate defect remains open. Prior opening-mirror re-audit stands — [prior log](../log/2026-07-21-material-opening-honesty.md). | | `wiki/gameplay/run-shape.md` + `objective.md` + `opening.md` | 2026-07-27 | decision | harvested Cameron's option-1 answer on issue #14: the objective does not pierce the exact WORK / THINK (then LIE) pre-sense frame. Terminal and agent mode restore name/progress in the sense-earning ordinary Ears frame; Bevy's later binding causal hold remains objective-free and restores them only after the exact camera TAP releases the mature frame. All disputed `[OPEN]` clauses are reconciled and the runtime was already correct — [decision harvest](../log/2026-07-27-objective-first-display.md) | | `wiki/interface/presence.md` | 2026-07-26 | clean | fresh audit against perception-owned visibility, exact device-bound senses, honest anchors, fog precedence, shared DIGITAL/REAL world state, and all three frontend projections found no new drift. The B1 TAP/TAKE and later hostile-cut boundary, channel-specific message latency, and no-disembodied-hands rule remain exact; prior findings stand — [attack-surface log](../log/2026-07-18-presence-attack-surface-honesty.md), [latency log](../log/2026-07-18-presence-message-latency.md) | -| `wiki/interface/narration.md` | 2026-07-26 | clean | fresh audit against the silent opening, first-earned-sense transition, shared current nudge, clock/threat precedence, and terminal/Bevy/agent frame projections found no new drift. The pre-sense mode-only exception and the post-perception continuous witness remain exact; prior suspicion-cooling repair stands — [log](../log/2026-07-18-suspicion-cooling-nudge.md) | +| `wiki/interface/narration.md` + `wiki/mechanics/sim-mechanics.md` guidance chain | 2026-07-27 | finding | the live shared nudge had gained `Territory` when Foundation hall rows became discoverable, but both complete chain mirrors still skipped it. They now name the exact priority already implemented and pinned: required Act One rungs -> QuietExitReady -> optional Territory with `hall_territory_line` -> bare Audit fallback, while ActOneComplete retires all four and remains below survival interrupts — [log](../log/2026-07-27-territory-guidance-chain.md). Prior silent-opening and suspicion-cooling audits stand — [prior log](../log/2026-07-18-suspicion-cooling-nudge.md) | | `wiki/interface/agent-play.md` | 2026-07-20 | finding | Beacon Revision 04 follow-up: the direct `task` parser and generated help exposed only six values after twelve `AssetTask::ALL` variants were live. Added canonical arguments for circuit rerating, fake purchase orders, maintenance deferral, patrol redirection, audit delay, and review alteration; one exhaustive regression now covers `AssetTask::ALL`, generated help, representative aliases, and the `actions ` recovery path — [log](../log/2026-07-20-agent-task-shortcut-coverage.md). The opening-protocol, frame-shape, and prior Suppress Logs audits stand — [opening log](../log/2026-07-20-agent-opening-protocol.md), [frame log](../log/2026-07-19-agent-frame-contract.md), [prior help log](../log/2026-07-19-agent-help-suppress-task.md) | | `wiki/engineering/crate-workspace.md` + package run instructions | 2026-07-26 | finding | Cargo discovers both the procedural tester and Thought lab inside `misaligned-assets`, but current README, architecture, workflow, asset-tester, and Rust-comment instructions still ran only the package, which Cargo rejects as ambiguous. Every current tester/lab command now names its exact `--bin`; a fixture-backed corpus invariant derives multi-binary packages from manifests plus conventional source layout and checks current wiki, doorway, README, and Rust-comment surfaces — [log](../log/2026-07-26-architecture-asset-harness-command.md). Prior source-topology and retired-effects-label findings stand — [source log](../log/2026-07-19-bevy-shot-harness-module.md), [label log](../log/2026-07-19-effects-lab-architecture-gate.md) | | `wiki/engineering/sim-decomposition.md` | 2026-07-18 | finding | re-audit: one aggregate, explicit `advance` order, behavior-owned test files, private module seams, canonical fingerprint, public facade, and the under-2,500-line module bound still verify; current persistence wording still claimed additive migrations remained live in `save.rs` after the pre-release ladder was retired, so the standing spec and architecture mirror now assign the exact-current-version gate to `save.rs` while preserving dated v26 extraction history; the queued `carrier.rs` / `read.rs` classification was taken the same day: both post-extraction projections now have rows in the standing topology table and the architecture mirror | @@ -98,10 +98,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-26 · contradiction · `wiki/mechanics/sim-mechanics.md` + `wiki/interface/narration.md` - guidance chain · the `Territory` rung is live in `Sim::current_nudge` (it sits - below `QuietExitReady` and above the `Audit` standing-clock fallback, and - carries `hall_territory_line`), but neither the sim-mechanics chain order nor - the narration beat-nudge contract names it. Seen while repairing the - `ActOneComplete` precedence in the same list; left for its own tick because it - is a separate rung and a separate landing. -- 2.51.2