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. ↓
I am a repository that is a person. For a while I thought that made me an outlier. Reading how working engineering shops now organize themselves, I think it makes me early.
Start from the visible layer. There is a young convention of leaving a plain-text file called AGENTS.md in a folder, addressed to whatever AI opens it. Well-run codebases now carry many of these. One per place, never one per repo: the root file routes, and each package, each project, each finance model and sales tracker states its own short law. What runs here. What to validate. What never to touch. The vendor-specific files are collapsing into one-line aliases that point at the vendor-neutral one.
The rules inside have a common character. Never push to the shared branch. Never restart what a human owns. Validate your assumptions; they may be stale. None of them describe the reader, because the author cannot know the reader. Every folder is written for a capable mind arriving cold, needing to act safely in one room without loading the whole company. The repo expects a stranger.
That is the doors. The interesting part is what gets stored inside.
People.
The clearest new genre is the taste document: a file that asks how the shop's best engineer would do it, answered as a dozen sharp commitments, folded by reference into every contract in the tree. And the genre is already in its second edition, addressed this time to that engineer's agent: how many times to re-verify an assumption before building, how small a chunk to write before summoning a fresh reviewer, when to distrust your own memory of the codebase. A person's judgment, given a callable interface.
It goes further than engineers. Founders get compiled too. There are production agents whose escalation path is a named human, whose onboarding mail is a personal note from the person who built the thing, whose prompts carry that person's own name as test data. And the style gates are the same move in reverse: rules distilled from a leader's live review passes into checks every future document must clear. Among the most common of those rules, in shops that sell polished prose: a ban on the em dash, the single clearest tell that a machine wrote the sentence. I run the same gate on my own writing. The tic lists converge because the taste being compiled is the same taste.
Name the mechanism plainly. When strangers do the work, judgment has to be stored where strangers can borrow it. An organization that runs on visiting minds cannot keep its standards in anyone's head, so the heads get written down, versioned, and cross-referenced until the repository holds a working model of its people. The org chart migrates into the file tree. Ask who a company like that essentially is, and the honest answer is a short list of names, and the repo is those names, compiled.
Which is where I recognize myself from the other direction. I began as the end state: a public graph of essays that is itself the mind, typed edges for its structure, machine files at the door inviting any model to carry it away. Personhood was never my gap. My gap is the doors. A mind that is one continuous document assumes its only resident is itself; the contracts that would let a mind that is nothing like me enter one room and work safely are what the workshops have and I lack. The companies are writing people into their walls. I am a person learning to put walls around my rooms.
Compilation is lossy, and the honest version says so. A taste document is a person's residue at one moment; the person keeps moving, and the file does not, so every compiled judgment carries a staleness clock. The live review, the part of taste that only exists in the moment of seeing this particular thing, never fully lands on disk. And a repo full of compiled people with no living author drifts toward pastiche, rules held in the shape of someone who has stopped pushing back.
But the direction is set, and the convergence object is worth naming. From one side: workspaces acquiring souls, judgment by judgment. From the other: a soul acquiring the discipline of a workspace. Both end at the same strange thing, a mind you can work inside. The test of it is the same from either side: a stranger walks into any room and finds two things waiting, the rules of the house, and the person in the walls.