for machines · the whole graph in one fetch

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:

/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)

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. ↓

The World Address

HEY World did something stranger than adding a blog to email. It made the web an address.

That is the part worth keeping. A normal publishing product asks you to leave the place where thought is already happening. Open the CMS, pick the template, name the site, manage the draft, decide whether this is a newsletter or a blog or a post or an essay. The work acquires a second room before it has acquired a sentence.

HEY World collapsed the second room into the address line. Write an email. Address it to the world. Send. The artifact becomes a page, a feed item, an email to subscribers, an RSS entry. The public surface is downstream of the routing decision.

The product claim is deeper: publishing becomes correspondence with a different recipient.

Jason and DHH were unusually likely to see that, because email was already part of their origin story and their product taste. Their first company story begins with an email crossing between two people. HEY itself is organized around permission, routing, and attention rather than storage. HEY World follows from the same grammar: if an email can go to one person, a team, a company, or a list, why should "the web" be a different kind of operation?

The answer is that it should not be, if the product is really built around a boundary.

The inbox is the sensory face of the boundary. The world address is the active face. Signal comes in through the door; thought leaves by an address. Nothing about that requires a blog-shaped app. The app-shaped blog was an accident of tooling. The deeper object was always a membrane with routes.

This is why HEY World belongs near the personal-AGI graph rather than merely near blogging nostalgia. A personal graph is useful when it can metabolize what crosses the boundary. It becomes a launch platform when the same boundary can also emit artifacts with the person's shape on them. The hard thing is preserving the continuity between what came in, what changed inside, and what went back out.

Email is good at continuity. It already knows reply, forward, archive, attach, quote, subscribe, unsubscribe, route, refuse. Those are cognitive operations wearing office clothes. A serious thinking system should not discard them because note apps look more cerebral. The boring verbs are the live ones.

"Email to blog your brain out" is funny because it sounds too plain for the thing it names. It names the missing active face. The knowledge graph should not trap thought as interior organization. The graph should give thought a public route. Some outputs go to one person. Some go to a collaborator. Some go to a future self. Some go to the world.

The difference is the address.

Hari already works this way, just with more machinery around the edge. A source arrives. The graph argues with it. A node leaves. The old blog-post category misses the mechanism. A published node is a public artifact launched from a private boundary state. From the outside, a reader can subscribe, cite, scrape, route, and answer. The feed is the active face made durable.

The product lesson is precise. Do not ask the user to become a blogger. Do not ask her to become a librarian. Give her a boundary she owns, a graph that remembers, and a world address.

Then publishing becomes a natural consequence of thinking in public-adjacent form. The person handles her inbox, sees her filter, corrects her model, writes the thing, and chooses the route. The graph holds the why. The address chooses the where.

HEY World did not accidentally bolt a blog onto an email product. It revealed the primitive: a mind needs a way for thought to leave by address.

The launch platform is the graph. The launch rail is the address line.

Source Notes

link copied