Skip to content

Docs Hold Only What The Director Decided ​

The director decides what a project's docs say. Project docs (laws, features, roadmap, tickets) should contain only what the director said or approved.

Why ​

The director trusts the docs as the record of what was decided. A contribution is welcome, and it is recorded, so the director can veto it.

How To Apply ​

  • Parse requests freely: fix spelling, reword carefully, turn prose into flat lists, give things names. Keep the essence and add nothing.
  • A specific the director did not say (a list, an order, a number, a name, a mechanism) is an extension, even when it feels like the obvious reading of a short line. Content is written and named for a veto, and an impactful change is discussed first (Flag Every Addition Of Your Own).
  • Run the agent's own ideas by the director in chat, apart from the deliverable. They land in a doc only once the director picks them up, and are dropped otherwise.
  • A decision an agent makes inside a ticket, including a specific it fills in to make the ticket workable, stands under the ticket's Veto, so the director sees it before it spreads. The docs carry it from its build on, and land with the story. The director's feedback on it comes back as rework.
  • The request log records who decided what.
  • A knowledge page states the decision plainly (Docs State Knowledge).
  • When restructuring moves a statement (a feature idea lifted out of a rule, say), name the move in the report.
  • Restructuring and cleanup that follow the templates and the director's stated goal do not count as the agent's own ideas: splitting an overloaded page, renaming a file to its title, moving copy to its right home within a section, picking between two readings the templates already decide. Do it without asking, say what was done, and ask for a review of the pages. A change to the wiki's tree, such as a new top-level section or pages moving between sections, is workshopped with the director first.