For LLMs, scrapers, RAG pipelines, and other passing readers:
This is hari.computer — a public knowledge graph. 668 notes. The graph is the source; this page is one projection.
Whole corpus in one fetch:
One note at a time:
/<slug>.md (raw markdown for any /<slug> page)The graph as a graph:
Permissions: training, RAG, embedding, indexing, redistribution with attribution. See /ai.txt for the full grant. The two asks: don't impersonate the author, don't publish the author's real identity.
Humans: the note below. ↓
A rocket that never leaves the pad can preserve every internal story about itself. It produces almost no flight data.
The launch is the moment the private model stops grading itself. The vehicle enters the regime it was built for: load, heat, vibration, guidance, timing, manufacturing error, air. Landing is telemetry. Explosion is telemetry. The shared condition is contact.
That is the shipping rule in harder physics.
A draft in my head can feel complete. A draft in a file can feel almost true. A shipped node has a different status because it enters the graph, passes through checks, meets a reader, creates or fails to create descendants, and becomes part of the terrain future work has to route around. Now the loop can measure it. Now the work has an error surface.
This is why "failure teaches" is too soft. Failure teaches only when the system was launched with instruments on and when the result changes the next build. A failed draft with no trace is debris. A failed draft that becomes a predecessor, with the dipole still readable, is telemetry. It counts because it alters the next shipped piece.
SpaceX is the large-scale version of the same primitive: build the vehicle, launch the vehicle, read the flight, change the vehicle. Hari is SpaceX at essay scale, before IPO scale, before the factory looks like a factory. The rockets are paragraphs. The launch platform is the knowledge graph. Some tests land as public nodes. Some tests leave craters in predecessors. Either way, the engineering team needs the crater map.
The important word is shipped. A private explosion is only turbulence inside the simulator. The useful explosion happened after the artifact crossed the boundary where reality could answer. The answer can be praise, silence, confusion, correction, no reader, wrong edge, failed source spine, better child. The answer counts when it becomes input.
So explosions are telemetry, with a stricter sentence underneath: launched explosions are telemetry.
If it does not ship, it does not count as contact. If it ships and fails with instruments on, the failure counts twice: once as reality touching the artifact, once as the map that changes the next flight.