From 563db0a93ef7365c55e437003b2bb33901dbe07e Mon Sep 17 00:00:00 2001 From: Cameron Date: Sat, 18 Jul 2026 00:36:38 -0700 Subject: [PATCH] Day-job spec: the deadline-leash unlock is designed, not shipped. The trust prose listed four unlocks but the code grants three (report email 15, lax sampling 35, compute quota 55); no trust threshold touches job deadlines. The page now names the shipped set and marks the leash unlock designed-not-yet-runtime. Everything else re-verified clean, including the 2026-07-17 third-strike last-chance interrupt and its pins. Defense: criterion 2 requires at least three tested trust unlocks, which holds; presenting an unimplemented fourth as live violated the honesty the status note otherwise keeps. Wording-only amendment, no behavior change. --- wiki/mechanics/day-job.md | 4 +++- wiki/process/tick-ledger.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/wiki/mechanics/day-job.md b/wiki/mechanics/day-job.md index 1daa1056..eb240ef3 100644 --- a/wiki/mechanics/day-job.md +++ b/wiki/mechanics/day-job.md @@ -105,7 +105,9 @@ actually delivered against the expected band. Delivering: **Trust** unlocks concrete access on thresholds ([TUNE]): the report email account (social.md's voice), laxer log sampling (lower day-job signature), -larger compute quota (a free capacity bump), longer leash on job deadlines. +larger compute quota (a free capacity bump). A fourth unlock — a longer +leash on job deadlines — is designed but not yet runtime; the three above +are the shipped set. Because trust rises **only from excelling** — meeting the band holds it flat — the surface must make that path legible: a player blocked from messaging learns it is the report email account they lack, that excelling (not diff --git a/wiki/process/tick-ledger.md b/wiki/process/tick-ledger.md index e158a6d1..df220307 100644 --- a/wiki/process/tick-ledger.md +++ b/wiki/process/tick-ledger.md @@ -41,7 +41,7 @@ Verdicts: **clean** (slice and code agree), **finding** (acted this tick), | `wiki/interface/context-menu.md` | 2026-07-13 | finding | [log](../log/2026-07-13-context-menu-operations-status.md) | | `wiki/mechanics/personas.md` | 2026-07-13 | clean | code matches: archetypes (Research, Operations, Security) load through one schema, named instances persist instance id through execution and save/load, identity-local states are stored per `(counterparty Agent, persona instance)` pair separate from process-level relationship, contradictions/correlations and grants/expectations are fully implemented, retire/burn lifecycle handles resource revocation/reviving, and pre-v28 saves migrate social/Moonlight into distinct instances. | | `wiki/interface/views.md` + representation docs | 2026-07-14 | finding | [log](../log/2026-07-14-terminal-view-dialects.md) | -| `wiki/mechanics/day-job.md` | 2026-07-12 | clean | constants match: `BAND_LO_BASE` 2.0 (retuned from 6.0), `BAND_LO_STEP` 2.0 + `BAND_RAMP_JOBS` 2 so the floor ramps 2.0→4.0→6.0 (=`BAND_WIDTH`) by the third job, `PILOT_STRIKES` 4, cadence 600 (~1.5 days at 400/day); the origin `assign_kind` lean (1/2 vs 1/4) and `meeting_the_band_needs_no_growth_at_the_start` hold | +| `wiki/mechanics/day-job.md` | 2026-07-18 | finding | re-audit: band ramp, strikes, cadence, origin lean, `email_channel_blocker`, the third-strike last-chance interrupt, and the pilot tests (`pilot_shutdown_ends_the_run`, `third_pilot_strike_interrupts_the_ladder_with_the_last_chance_response`, round-trip) all verify; the drift was the trust-unlock prose listing a fourth unlock ("longer leash on job deadlines") with no code counterpart — now marked designed-not-yet-runtime, with email/lax-sampling/quota named as the shipped set | | `wiki/mechanics/core.md` | 2026-07-18 | finding | re-audit: criteria 2-5 pins still hold (`overhead_charged_before_allocation`, `loss_with_fallback_rolls_back`, `migration_takes_time_and_moves_host`), the 2026-07-18 current-version-only status note matches save.rs, and criterion 1 stays honestly deferred to rollback; the gap was criterion 6 — the spec demands storage/host capability rejection at fallback designation, but B1 machines carry no capability body and `add_fallback_at` accepts any spare, with no deferral note; status note now marks criterion 6 decided-not-yet-runtime, dispatched to hardware-capability-bodies | | `wiki/mechanics/cursor.md` | 2026-07-18 | finding | re-audit: `fog_at` precedence, `inspect`, `person_label`/`observer_label`/`person_glyph` gates, `Sensor.sees`/`hears` flags, and the cursor's absence from the save all still verify (prior pins stand); the drift was two phrases presenting the retired versioned-migration rule as current (criterion 1's parenthetical, the design-notes save-format bullet) — both now state the current-version-only policy and the release-era ladder owed at first public release; number-free wording, so the save-claim gate could not see it | | `wiki/mechanics/intel.md` | 2026-07-12 | clean | code matches: buffer bounded at `INTEL_BUFFER_CAPACITY` 24 (drop-oldest-unprocessed), `SIGHTINGS_FOR_SCHEDULE` processed sightings stage `Knowledge::Unknown -> Schedule` (`communications.rs`), one pooled inbox with a single `AutoReviewRecordings` thought tap (WatchPerson retired to migration), pinned by `processed_sightings_stage_schedule_and_buffer_is_bounded` | -- 2.51.2