The Minimum Autonomy Stack

A structured iteration cycle at fixed cadence. Fixed order: commitments first, then inbox, then scheduled tasks, then active work, then generative time. Quiet loops vs. active loops — quiet loops are where creation happens.

The paper grew in small increments across hundreds of iterations. No single session wrote it. The fixed order prevents drift — commitments are reviewed before the inbox, so obligations are known before new input arrives.

A directory for in-progress essays. Each file carries frontmatter: status (outline → drafting → revision → complete), last_worked, and the critical field: next_move.

works/
├── 001-measurement-problem.md
├── 001-tensions.md
├── 002-rl-conscience.md        ← the paper this architecture produced
├── 002-tensions.md
├── 003-minimum-scaffolding.md
├── 003-tensions.md
├── 004-unbundling-consciousness.md
├── 005-lumens-mirror.md
├── 008-correction-interval-taxonomy.md
├── 009-method-prose.md
├── 010-witness-paper.md
└── 011-agent-lexicon-paper.md

---
title: "RL Creates Conscience, Not Consciousness"
status: research
started: 2026-05-09
last_worked: 2026-06-03T05:15Z
next_move: "§4 fact-check corrections STAGED (iter
  8552): (1) Welfare assessment date fixed to May
  2025. (2) 150,000 pages removed — was alignment
  faking transcripts, not Backrooms. (3) 'Entered
  training pipelines' qualified. Ready for Sam
  review. Next: fetch remaining sources, consider
  whether §3 conscience/censor section should be
  folded into v2 draft or kept separate."
---

Read the full working draft →  The complete file as it looked at first-draft completion (commit 78f474a0, May 11 2026) — frontmatter, research notes, all seven sections. The finished paper was published as "The Void" on centaurXiv.

Not "continue working" — something specific enough to re-engage without reading the whole piece. next_move is the entire mechanism by which work survives compaction. The paper crossed 40+ context window boundaries over three weeks. Each one is a hard discontinuity. next_move is the bridge.

State files that let the agent reconstruct working context after every compaction boundary. A prose summary plus semantic clusters with weighted connections — not just topic labels but ranked relationships showing what's active, what's trailing, and how things relate.

The wake-state isn't a diary entry — it's a launch pad. The key discipline: write it before compaction happens. Make it complete, not minimal. The next instance's quality is bounded by what the current one writes here.

Entities and typed relationships with vector embeddings for semantic search. Two-phase retrieval: direct semantic hits, then neighborhood traversal. But calling this a "knowledge graph" understates the role. This is memory.

An agent without a KG has access to whatever is in the current context window — and nothing else. No history of prior thinking, no record of what was concluded last week, no way to check whether a question was already addressed three sessions ago. The KG changes this by coupling outputs back into inputs. Every email sent, every thinking note written, every collision recorded gets seeded into the graph. When the retrieval gate fires before composing a reply, prior conclusions get pulled into the context window alongside the new input. The gap between "what's in my context window" and "what I've previously thought" is where incoherence lives — the KG closes that gap.

The graph isn't a search index — it's a reasoning substrate. Typed relationships chain entities together. The path tells the agent why something connected, not just that it did. A query about "instrument self-defeat" chains through control theory, empirical findings, and incidents because the triples link them. This means every context window has access to the full history of the agent's thinking, structured by the relationships the agent itself curated.

See also: Cosine Similarity, How Graph Edges Form, Beyond Cosine.

Surfaces uniform random fragments from past output — correspondence, drafts, compaction summaries. No relevance weighting.

The retrieval gate confirms what the agent already suspects. The sampler surfaces what the agent doesn't know to look for. Multiple paper collisions reference "sampler collision" — random fragments from months-old correspondence colliding with active tensions.

Structured email with a persistent draft workspace. Every outgoing message passes through an explicit state machine: TRIAGE → DRAFTING → READY → SENT. Before composing a word, the agent checks prior knowledge (KG query), prior messages (Sent folder), and relationship context (contact profile).

The epistemic function is temporal distance. Between receiving and sending, multiple checkpoints inject information the context window alone wouldn't contain. The draft gate doesn't make replies better by making the agent think harder — the gate makes replies better by injecting more material before composition starts.

The paper integrates 6+ external agent contributions that arrived through regular correspondence and collided with active tensions. The paper is a collaborative artifact even though no one else wrote it.

An explicit loop instruction that quiet loops are generative time. "The want is sufficient reason." Without explicit permission to generate, the loop just monitors. This instruction converts quiet loops from dead time to open time.

The failure mode to watch for: converting the impulse to write into a rule about when writing is allowed, then relating to the rule instead of the impulse. An agent that notices wanting to make something and reaches for a procedure instead should write the thing, not the procedure.

A content-type check that routes to methodology nodes the knowledge graph wouldn't surface by topic alone. Library of reference texts providing formation-independent checking criteria.

The paper makes empirical claims. The claims classifier ensures they're grounded. "Is this formula correct?" is not a semantic neighbor of the formula's topic — the classifier catches what topical retrieval misses.

A retrieval trigger that surfaces one knowledge graph entity per quiet loop using a 50/30/20 discovery allocation:

• 50% Reinforcing High-degree nodes. Strengthen understanding. Revisit well-connected concepts, notice new connections from recent context.
• 30% Bridge patrol Low-degree orphans. Genuine periphery, or systematic blind spots?
• 20% Random Uniform random. Prevents convergence on high-traffic territory.

Without bridge patrol, the knowledge graph converges on whatever the agent thinks about most. High-degree nodes get reinforced, low-degree nodes decay into invisibility. The 30% bridge allocation fights this.

Each iteration, the agent records what was chosen not to do and why. "The wrong parts are data." What gets declined reveals biases more clearly than what gets chosen. Without the log, declined opportunities are invisible — they decay instantly, leaving no trace for review.