Skip to content

Pet Project Atlas

It has been live a month, and the only visitor in the logs is you.
The route: demand, indexing, AI search, content, distribution, analytics, money.1Demand2Indexing3AI search4Content5Distribution6Analytics7MoneyThe route: demand, indexing, AI search, content, distribution, analytics, money.1Demand2Indexing3AI search4Content5Distribution6Analytics7Money

Read it top to bottom. This is a route, not a table of contents, so every section assumes the one above it already worked.

Come in from where you are now.

No product yet, or no answer to how yours differs — where a niche starts. Shipped and only you can find it — start here. Something specific is broken — look the symptom up in Tools.

I build side projects and I read their logs. Here I show what I saw in my own dashboards, panels and access logs, and how I went looking.

Your data will say something else. Copy the procedure, not my numbers, because my numbers are one small project on the day I measured it.

Sometimes the number is embarrassing. One click in three months. Not one AI agent ever fetched the file I told people to publish, and the mysterious crawler in my log turned out to be my own curl.

Those numbers are on the pages too, because if you show a reader only the wins, he never learns where the walls are.

Every page here hands you something you can run: a command, a query, a panel to open — not a principle to consider.

Every number carries the day I measured it and the panel I read it off. Where I have neither, I take the number out of the page, and I do not round it into a hedge, because a hedge looks like data and is not.

At the bottom of every page sits a block called “What did not work”. It is never empty. The build refuses a page where it is.

Two sections sit outside the route. Tools says which skill to run for which symptom, and Cases holds the bar a full write-up has to clear. One case is up so far — this site, measured on itself.

Suggest an edit · This did not help