Field notes
Field notes from real work.
Short write-ups of work we can show. How machines read this site, how its build checks its own words, and how our research keeps from fooling itself. Each one sticks to what we did and how.
This page’s own structure, drawn at build from its HTML.
People read the top layer, crawlers follow the middle one and machines parse the bottom one.
6 headings · 50 links · 5 schema nodes
◆ BuildThe notes
What we’ve written so far.
Each one takes a few minutes. The notes about this site describe code anyone can read in its public repository (the code and its full history, kept in one place).
-
What AI crawlers read.
What a search crawler or an AI answer engine is handed when it fetches a page, and how this site makes sure that’s the whole page.
-
A build that refuses to overclaim.
How this site’s build stops on hype, invented numbers and counts of clients, and what writing under those checks costs.
-
Research that can’t fool itself.
The checks our market research runs against fooling itself, with AI agents doing the work and a person deciding at every step. Method only, no numbers.
Start here
Tell us what’s slow, or what can’t be found.
One paragraph is plenty. Tell us what you want built, the step that costs the most, or the page that should rank and doesn’t. If you know why the obvious fix hasn’t worked, say that too.
Daniel reads and answers these himself, usually within a day or two. No sequence, no drip, and nothing sold to anyone.