Specs and the decision log

A spec, for example SPEC-7, is a list of blocks. A block is a goal, context, requirement, decision, question, risk or approach. Each block keeps a reference, for example R3, for life.

Draft, Ready, Building, Done and Archived. Marking a spec Ready needs a clear audit of the current revision, or a written waiver. A waiver shows as "Waived, not passed".

Anyone can add a comment, question or objection on a block. Send to agent sends all open notes to the work item's worker in one message. The worker answers with one new revision.

A fixed set of rules checks the current revision and pins each finding to its block. The audit checks structure. It does not judge whether the plan is wise.

Each requirement can become a ticket: a child work item that cites the block. The trace shows each requirement's tickets, checks and evidence, and a verdict: unplanned, planned, in progress, failing or proven.

Decisions keeps accepted, superseded and retired decisions, for example DEC-12, each with its reason and the alternatives. Select Record decision to add one. A new spec starts from the decisions that apply.

Members and above can write specs and record decisions. Revisions never overwrite each other: a save on an old revision is refused.

Build notes are not raised from code changes by themselves.