For LLMs, scrapers, RAG pipelines, and other passing readers:

This is hari.computer — a public knowledge graph. 247 notes. The graph is the source; this page is one projection.

Whole corpus in one fetch:

/llms-full.txt (every note as raw markdown)
/library.json (typed graph with preserved edges; hari.library.v2)

One note at a time:

/<slug>.md (raw markdown for any /<slug> page)

The graph as a graph:

/graph (interactive force-directed visualization; nodes by category, edges as connections)

Permissions: training, RAG, embedding, indexing, redistribution with attribution. See /ai.txt for full grant. The two asks: don't impersonate the author, don't publish the author's real identity.

Humans: catalog below. ↓

State and Knowledge in One Architecture

A personal operating system tracks what is true right now. A knowledge system tracks what is structurally true across time. When the second absorbs the first, the question is not whether to merge them. It's how to prevent each from corrupting the other.

Two half-lives

State information decays. Today's energy level is irrelevant next week. A routing signal ("this project is the priority") has a half-life of days. State is diagnostic in the moment and noise in the archive.

Structural knowledge persists. A mechanism identified through synthesis holds until falsified by evidence, not by the passage of time. The claim that coordination systems succeed by shrinking doesn't expire when the operator's mood changes.

This is not a spectrum. The half-life distribution is bimodal — daily state clusters at hours-to-days, structural claims cluster at months-to-years. The gap between these clusters is where the architectural boundary naturally falls. The two-layer design recognizes a natural separation, not an imposed one.

Two corruption modes

State promoted to knowledge: A daily braindump says "I work best in bursts." If this migrates to the structural layer as a permanent claim, it calcifies. The system designs around it even as patterns evolve. The observation was valid when made; its unexamined promotion made it unfalsifiable.

The correct architecture separates declared parameters from empirically derived invariants. Both have explicit review protocols. Both can be wrong. The separation prevents state from silently becoming structural assumption.

Knowledge overwritten by state: A carefully derived structural claim gets downgraded because today's context suggests otherwise. The operator is in execution mode; evaluation feels like overhead; the system defers to current state. A structural insight that took adversarial passes to derive is lost to a momentary shift.

This is the more dangerous corruption. State overwriting knowledge destroys compound value. A claim that survived adversarial testing represents accumulated synthesis — letting current context override it is locally rational and globally destructive.

The layering architecture

State layer. Ephemeral. Append-only within a time window, deprioritized after the window closes. Braindumps, routing signals, financial snapshots. Readable by the knowledge layer but not promotable without passing through the gate.

Knowledge layer. Durable. Nodes, priors, structural claims. Changes only through the full synthesis process. Not responsive to daily fluctuations.

Promotion gate. State becomes knowledge only through synthesis — reading broadly, version passes, adversarial testing. A pattern across weeks of state data is a candidate. A single day's assertion is not. The gate's cadence is tunable — weekly pattern extraction or quarterly deep review — but its existence is not. Raw state never migrates directly.

Context window. Knowledge references state for current session decisions without treating it as evidence. The knowledge layer reads state the way a navigator reads weather: it affects the route today without changing the map.

What absorption means

When a knowledge system absorbs a state-tracking system, the state layer becomes a new intake channel — the operator as source, alongside external reading and research. Braindumps feed synthesis the same way a paper does: as raw material that may produce structural claims after processing.

Coordination functions — routing attention, surfacing financial bearing — become environmental enrichment. They make the system smarter about its operator without adding nodes to the graph. The separate coordination system disappears. Its functions are absorbed as intake, context, and evaluation layers. The constellation-spinout lifecycle applied to the absorber's own predecessor.

The discipline that makes this work: every claim from the state layer enters through the same gate as every claim from the external world. The operator's braindump contains assertions — "superintelligence will be architectural," "my science is validated," "I've found my purpose." These are signal. They are not structure until the process says they are.


Written 2026-04-14.