The notes system
The repo has two documentation systems with different jobs. Knowing which is which prevents duplication and stale content.
This handbook (docs-site/)
Section titled “This handbook (docs-site/)”Durable, evergreen knowledge: how the business runs, what was built, why
decisions were made. Organized by function. This is the single source of truth
for business facts and the canonical upstream for the bot pack and llms.txt.
notes/ (working notes)
Section titled “notes/ (working notes)”Time-stamped, in-flight work with its own ship-then-archive lifecycle:
notes/current/- active, decision-relevant work (audits, marketing punch lists, session handoffs, evergreen reference docs).notes/current/INDEX.md- the map of everything innotes/.notes/drafts/- content awaiting boss review.notes/archive/- shipped or superseded work, kept for provenance.
Convention (from INDEX.md): when a doc’s recommendations ship, it moves to
notes/archive/ rather than going stale in current/. Anonymized aggregate
data only; raw CSVs/PII live outside the repo at ~/TILT-private-data/.
What goes where
Section titled “What goes where”| Content | Home |
|---|---|
| ”How TILT sells / delivers / supports / runs” | Handbook |
| ”Why we decided X” | Handbook (Decisions) |
| A specific copy audit being acted on right now | notes/current/marketing/ |
| A session handoff / paste order for a shipping round | notes/current/ then archived |
| Evergreen reference (resume, voice samples, links, WPForms) | notes/current/reference/ (handbook links to it) |
| Anything with raw client data or PII | ~/TILT-private-data/ (never the repo) |
Rule of thumb: if it has a ship date and then becomes irrelevant, it is a note. If it stays true and someone would look it up months later, it is handbook.