StrategiQ Atlas

Guides to how our more complicated client websites work, so troubleshooting does not depend on one person being available.

Finding things

Use the search box, or ask Claude from inside any codebase that has run atlas init — it can search and read Atlas directly.

Writing things

Do not edit pages here by hand. Write from the codebase the page is about:

atlas push notes.md --site checkout --type runbook --title "Stripe webhook fails"

atlas fills in the owner, the source repository, and the verification date, then commits and pushes. The site redeploys within about a minute.

What belongs here

Architecture, features, runbooks, integrations, and onboarding for each site. A feature page explains how one feature works, in enough detail that someone covering the project — or Claude, asked to change it — can act without reading the whole codebase. /atlas-audit in a wired repository writes a set of them from the code.

Never credentials — the write path blocks anything credential-shaped. Never unpatched vulnerabilities either; those belong in the ticket tracker, not in a document that describes exactly how to exploit us.

Coverage

The health dashboard shows which sites are documented and which pages have gone stale.