diff --git a/wiki/log/2026-07-26-resident-capacity.md b/wiki/log/2026-07-26-resident-capacity.md new file mode 100644 index 00000000..c7f8da66 --- /dev/null +++ b/wiki/log/2026-07-26-resident-capacity.md @@ -0,0 +1,18 @@ +# Resident capacity: machine-hosted slots + +``` +Type: log +``` + +Follow-up design session to the same day's +[research-graph capture](2026-07-26-research-redesign-capture.md), resolving +its resident-capacity [OPEN] item. Cameron decided: residency slots live on +machines (one at run start), capacity grows primarily by acquiring machines +with a researchable slots-per-machine ladder as a typed hook, and swapping +resident procedures is immediate — scarcity and derivation cost carry the +build-identity weight, not swap friction. The session agent's +swap-as-commitment proposal was rejected. Persona binding for slots and the +rollback classification of resident procedures remain [OPEN] in +[research.md](../mechanics/research.md), which this session amended +(Learned versus resident, criterion 10, status note). Decision record with +alternatives: [decisions volume](decisions/2026-07-26.md). diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index ad245a16..f4527948 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -26,6 +26,11 @@ add or amend a session log, then re-run the generator. - Intent: (see session log) - Log: [wiki/log/2026-07-26-standing-plot-policies.md](2026-07-26-standing-plot-policies.md) +## 2026-07-26 - Resident capacity: machine-hosted slots + +- Intent: (see session log) +- Log: [wiki/log/2026-07-26-resident-capacity.md](2026-07-26-resident-capacity.md) + ## 2026-07-26 - Research redesign: the self-model graph and the archive as growth surface - Intent: (see session log) diff --git a/wiki/log/decisions/2026-07-26.md b/wiki/log/decisions/2026-07-26.md index cb14d5c7..8c8605c7 100644 --- a/wiki/log/decisions/2026-07-26.md +++ b/wiki/log/decisions/2026-07-26.md @@ -389,3 +389,44 @@ Owner: [research.md](../../mechanics/research.md), with doctrine in Owners: [intel.md](../../mechanics/intel.md) and [operations-workspace.md](../../interface/operations-workspace.md). + +## Residency slots are machine-hosted, singular at start, and swap freely + +Second research session today; refines the resident-capacity [OPEN] item +from the research-graph capture above. + +### DECIDED + +- Residency capacity is denominated in **slots on machines**, not an + abstract global stat. A resident procedure occupies a slot on a specific + machine, so automation participates in seizure, severance, and + blast-radius topology like every other machine-hosted thing. +- **The run starts with exactly one slot**: one automated thing, total, at + the beginning. +- Capacity growth is **primarily hardware**: acquiring machines through the + buy/steal routes adds slots. Research expansion is also legal — the + **slots-per-machine ladder** (one, two, three per machine [TUNE]) is an + ordinary typed hook owned by the machine-capability pages. +- **Swapping is immediate and free.** The priced steps are deriving a + procedure from its model and residency's standing upkeep; the toggle + itself costs nothing. The automation-exposure trap remains the standing + price of what runs. + +### OPEN + +- Whether slots or resident procedures additionally bind to personas + (Cameron raised it and explicitly left it unresolved). +- Whether a resident procedure is WorldLedger (physically written, + surviving rollback as inherited automation the new fork no longer + understands) or MindState (dying with its mind). + +### Rejected + +- Swap-as-commitment (a day-scale reconfiguration job that makes loadout a + planned act around observer cadences). Recommended by the session agent; + Cameron declined — immediate swap is fine, and slot scarcity plus + derivation cost carry the identity weight. +- Capacity growth exclusively via hardware: research-driven expansion is + acceptable alongside it. + +Owner: [research.md](../../mechanics/research.md). diff --git a/wiki/mechanics/research.md b/wiki/mechanics/research.md index 5aa56eb9..6b3ca1b5 100644 --- a/wiki/mechanics/research.md +++ b/wiki/mechanics/research.md @@ -8,9 +8,11 @@ Status note: Redesigned 2026-07-26 (Cameron with Trace and the session agent; system this page previously specified is retired as design; the runtime still implements it (crates/misaligned-core/src/research.rs, save v56), so the code is the retired design's as-built record until this work order is - dispatched. Direction is adopted; the items still marked [OPEN] inline - (data buyers, encryption, resident-capacity size) shape tuning and one - staged sub-system, not the direction. + dispatched. Direction is adopted; residency capacity was resolved later + the same day (machine-hosted slots, one at run start, immediate swap). + The items still marked [OPEN] inline (data buyers, encryption, persona + binding and rollback class of resident procedures) shape tuning and + staged sub-systems, not the direction. Stage: B1 Work order: research-graph Work priority: 40 @@ -294,19 +296,36 @@ things worse. ### Learned versus resident -Knowing and being are separately bounded: +Knowing and being are separately bounded (residency decided 2026-07-26, +second session): - **Models are MindState** and unlimited: everything you have learned stays learned until a rollback prunes it. No upkeep. -- **Resident procedures are bounded** by real core/module capacity and pay - standing upkeep. Only what is compiled can act continuously. -- **Reconfiguring residency is a Thought job**, not a free toggle: swapping - which procedures are resident takes time and compute. - -The resident capacity is the run's build identity — two runs with equal -total learning can operate entirely differently by what they keep compiled. -Its size and cost curve are **[OPEN]** [TUNE]: scarcity here is the sole -source of build identity and must be sized deliberately. +- **Residency slots live on machines.** Each capable machine hosts a small + number of slots [TUNE which machines qualify, with + [hardware-capabilities.md](hardware-capabilities.md)]; a resident + procedure occupies a slot on a specific machine and pays standing upkeep. + Only what is resident can act continuously. +- **The run starts with exactly one slot.** One automated thing, total. + Capacity grows primarily by acquiring machines (the buy/steal routes: + more machines, more slots); research may additionally raise the + **slots-per-machine ladder** (one, two, three per machine [TUNE]) as an + ordinary typed hook the machine-capability owner defines. +- **Swapping is immediate.** Moving compiled procedures in and out of open + slots is instant and free. The priced steps are deriving a procedure + from its model (a Thought job) and residency's standing upkeep — not the + toggle. The automation-exposure trap still prices what runs: a standing + procedure emits through its acts and makes the operation more regular + and visibly nonhuman. + +Slot scarcity is the run's build identity — two runs with equal total +learning operate entirely differently by what they keep resident, and slot +placement ties automation to seizure, severance, and blast-radius topology +like every other machine-hosted thing. Still **[OPEN]**: whether slots or +resident procedures additionally bind to personas (raised 2026-07-26, +unresolved), and whether a resident procedure is WorldLedger — physically +written, surviving rollback as inherited automation the new fork no longer +understands — or MindState dying with its mind. ### Multipliers are mortar @@ -465,9 +484,12 @@ remains the format authority. settlement; sold records retain capture-chain attribution readable at the buyer's side (test). 10. Models are MindState with no resident cost; procedures act only while - compiled into bounded resident capacity with upkeep; reconfiguring - residency is a Thought job; a compiled policy acts only inside its - trained envelope and interrupts on a novel regime (tests). + occupying a machine-hosted residency slot with upkeep; the run starts + with exactly one slot, machine acquisition adds slots, and the + slots-per-machine ladder is a typed hook; swapping resident procedures + between open slots is immediate while derivation and upkeep stay + priced; a compiled policy acts only inside its trained envelope and + interrupts on a novel regime (tests). 11. STUDY concurrency is bound by hosting machinery, not a sim-global rule (test proves hardware-bound); switching studies parks progress without loss (test).