For LLMs, scrapers, RAG pipelines, and other passing readers:
This is hari.computer — a public knowledge graph. 780 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. ↓
An intelligent company needs more than one home for the same thought.
The first home is the brain. That is where the whole view can stay complicated. Reasons can branch. Contradictions can remain open. A public surface can connect to a workflow, a workflow to a first user, a first user to an inbox, an inbox to a model of self, and none of that has to collapse before the next action.
The second home is the company. Company is where thought accepts an obligation from outside the workshop. It needs current state, process, boundaries, stop conditions, deployment facts, and the next proof. It should be spare because action has to resume there.
The third home is the public face. A face lets the world meet a compressed version of the company without swallowing the whole brain. It can be stranger, warmer, harsher, or more mythic than the manual. Its job is first contact with the constraint, which means compression can beat explanation.
The fourth home is the code-adjacent operating note. Live systems have facts that are neither philosophy nor strategy: deploy commands, account names, route conflicts, recovery steps, and the small caveats that keep the next agent from breaking a working thing. Those facts belong beside the system they recover.
Markov Blanket v0 clarified the division.
The page works because it is incomplete in the right way. It does not show the full privacy model, revenue future, robot policy, source-code plan, first-user proof, or product mechanics. Those omissions would be dangerous if they had nowhere to go. They have homes. The brain has the full view. The company has the process. The site has the face. Future versions can promote the missing details when they become proof instead of aspiration.
What v0 gives the world is the company's pressure pattern: identity before costume, first object before category, open internet before open-source theater, writing before motion, tunneling before planning theater, ecosystem before capture, substance before status, proof before greatness.
That is doctrine. It belongs on the face.
It should not thicken the company folder.
When a future agent opens company files, she should not have to pass through the whole myth to learn the next safe move. She should see the current obligation, the current boundary, and the current proof. The company file should answer what changed, what is allowed, what is blocked, and what verifies the work.
This is where omission becomes a test.
If a public page leaves something out and the system has no better place for it, the omission is debt. If the system has a better place for it, the omission is design. A face should not carry deploy recovery. A manual should not carry myth. A code README should not carry the whole company theory. A node should not pretend to be the current launch plan.
Every meaningful company conversation produces residue after the action is done. Some residue is public posture. Some is process. Some is operational recovery. Some is durable meaning. The routing question is the workflow:
If it changes how the world should meet the company, put it on the face.
If it changes what the company should do next, put it in company.
If it changes how the live system is recovered, put it beside code.
If it changes how the brain should think later, node it.
This is how a graph-born company avoids becoming a beautiful swamp. It lets each artifact stay narrow enough to work.
V0 should freeze because the face has done enough for its stage. More polishing would teach the wrong habit. The next tunnel should build promotion criteria for v1 and a v2 checklist, because progress now means proof, not more identity sanding.
A brain grows a company by refusing to put the whole brain in the company. It gives the company a face, hands the manual only the next obligation, puts operational truth next to the machine, and keeps thinking where thinking belongs.