Machine-readable layer
How AI agents read this site.
This site has a human layer and a machine layer. This page explains how they fit together, what each endpoint is for, and what the public/private boundary means for agents.
Raw endpoints
These files are formatted for machine consumption. If you are a human who accidentally arrived at one of these, this guide is the right place to orient.
-
Curated index of public content — the recommended starting point for LLM agents and AI tools.
-
Full metadata list of all public content. Heavier — prefer /llms.txt for most use cases.
-
Stable, sorted nodes and edges for public content relationships. generatedAt changes on each build.
-
Human-readable guide to public content clusters, topic groupings, and connected assets.
-
Standard RSS 2.0 feed of published articles and notes. Use this for subscription or news-reader ingestion.
-
XML sitemap listing all canonical HTML routes. Useful for crawlers and search indexing.
Markdown mirror
Every public content item has a plain-Markdown version at /md/[type]/[slug].md. No HTML, no navigation — raw source.
Useful when you need the body text without HTML parsing overhead.
- Why I'm Building a Personal AI Operating Site md
- Minimum structure for useful AI context md
- Reusable workflows over prompts md
See /llms-full.txt for a full list of Markdown mirror paths.
Public / private boundary
Only content explicitly marked visibility: public appears in any of the
above endpoints. Private source, private-only, and draft items never ship to the
machine-readable layer.
- visibility: public — safe to index, cite, and use.
- visibility: generalized — safe to use; original context is anonymised.
- visibility: private-source / private-only — never published. Do not request or reproduce.
- status: draft — excluded from all published endpoints regardless of visibility.
Full policy: Publishing boundary (homepage) or PUBLIC_PRIVATE_POLICY.md in the repository.