Specs review with the owner

As the owner, I want the system to review my specs and bring me only what needs my decision, so that the specs stay true without me rereading them.

Scenarios§

1. The owner asks the specs playbook for a review; it reads every record type in every tier the project reaches and puts each record to its type test.
2. A record that is plainly stale — it only needs to say what is already decided or true — is fixed and the fix is reported.
3. Each decision that is the owner's is filed as a clarify item; in the dialogue the system asks them one at a time in prose, with compact context, its own proposal and a counter.
4. Before the owner accepts anything, the system lists what it is about to take as decided.

Restart: the session ends mid-queue; the next review picks the remaining questions up from the open items.

Edge cases§

• The review uncovers an incident: it is written up as a reference tagged postmortem — timeline, causes, remedies.
• A contradiction the records themselves settle: it becomes a conflict record; only one the owner alone can settle becomes an open item.

Criteria§

• Reads every record type in every tier the project reaches and puts each record to its type test (booping:rule/0034).
• Applies a fix that only makes a record say what is already decided or true, and reports it.
• Files every decision that is mine as a clarify item, so a restart picks the queue up from the open items; in the dialogue it asks one at a time in prose, with compact context, its own proposal and a counter (booping:rule/0032).
• Lists what it is about to take as decided before I accept anything (booping:rule/0033).
• An incident it uncovers is written up as a reference tagged postmortem: timeline, causes, remedies.