Skip to content

Docs State Knowledge ​

A knowledge page (feature docs, specs, design pages, laws, architecture, overview) stands on its own and states what is true, the way an encyclopedia does: no attribution markers, no dates of decisions, no quoted sentences of the director's, no account of how a decision came about or what it replaced.

The provenance lives in the request log, where every message is written first, and in the process records that point back to it: user tests, changelogs, activity, the plan, the refine list, and any other record the project keeps. Those may name who said what and when.

Why ​

A knowledge page reads as what is true now. The log holds who said what and when.

How To Apply ​

  • Writing or editing a knowledge page: state the fact in plain present tense. Leave the attribution, the date and the quote in the log.
  • The director's say over the docs still holds (Docs Hold Only What The Director Decided): only what the director said or approved goes in. The check is the log, never a marker on the line.
  • Organize a page by topic, broad to specific, the way an encyclopedia article is. Never a running list in the order things were decided.
  • Briefs tell agents the same. A brief never asks an agent to mark what it quotes.
  • The project's hygiene suite can enforce it: no attribution markers and no dated attribution outside the log and the process records.