Public: anyone can read this; the crew can change it.

Bring the remaining docs in line with docs/WRITING.md #9426

look green — it answered, no tests were run, ready for a look opened this has it
opened this

Bring the remaining docs in line with docs/WRITING.md

The first screens are done: README.md, docs/README.md, and the openings of STUDIO, APPS, ORIGINS, CREW, ARCHITECTURE, OPERATING, DEVELOP and TOUR. The bodies and all other documents are not.

How to work

  • One small pull per document, in the order below. A document over 3,000 words may take one pull per section.
  • Follow docs/WRITING.md. Check each claim against the code or a test. Fix or cut what you cannot confirm.
  • Move technical substance; do not delete it. Keep headings stable where other documents link to them, or update those links.
  • Change no code behavior. A doc that disagrees with the code gets corrected. If the code looks wrong, file an issue.

Order

  1. docs/STATUS.md, docs/SECURITY-RUNBOOK.md, docs/THREATS.md: what readers trust most.
  2. docs/STUDIO.md: remove the "dev mode" and ?mode=dev sections' stale framing. Modes are gone.
  3. docs/APPS.md, docs/CREW.md, docs/ORIGINS.md: the core concepts, one section per pull.
  4. docs/ARCHITECTURE.md, docs/OPERATING.md, docs/DEVELOP.md, docs/TOUR.md.
  5. docs/MCP.md, docs/CLI.md, docs/GIT.md, docs/ON-YOUR-MACHINE.md, docs/METRICS.md.
  6. docs/RECOVERY.md, docs/RESTORE.md, docs/SNAPSHOT.md, docs/DOMAINS.md. Keep what test/recovery-doc.test.ts requires.
  7. docs/REFERENCE.md: split it by topic into the documents above. It stays the list of every document.
  8. docs/features/*.md: a batch of about 10 per pull.
  9. All other top-level documents. Design records and research may be marked as records instead of rewritten.

Do not rewrite documents the owner is reviewing for removal or privacy. Ask on this issue first.

Done when

Each pull:

  • The document opens with what it covers, who it is for and the key idea, in under 120 words.
  • It adds no em dashes: git diff -U0 docs/<file> | grep '^+' | grep -c '—' prints 0.
  • Its opening and prose for newcomers contain no issue numbers: sed -n 1,12p docs/<file> | grep -c '#[0-9]' prints 0.
  • It has no references to removed README sections: grep -n "README's" docs/<file> prints nothing.
  • Each file, route, flag and test it names exists at the pull's commit.
  • bun test test/readme-front-door.test.ts test/readme-cap.test.ts test/dependencies-named.test.ts test/design-lint.test.ts passes, with any test that reads the document.

The whole issue: grep -rlE 'magic|boring|at 3 a\.m\.' docs/*.md prints nothing, and each listed document has landed.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs