Statuses and approval

Understand what each document status means and what to do next.

A status describes the document, not how far along the whole project is.

Status	What it means	What to do
Ready	The document answers everything it owns. Nothing is waiting on you.	Read it, then sign approve it.
Ready — your decision needed	The document is complete and buildable, but one decision is yours.	Open the document, read the open item, and settle it. You may approve first if it does not block development.
Needs Repair	A required section is missing, contradictory, or not buildable as written.	Regenerate the document before approving it.
Blocked	Work on this subject cannot begin until a dependency is resolved.	Open the blocking item and resolve it before approval.
Pending	The document has not been generated yet.	Wait for or start Blueprint generation.
Not Required	Your product does not need this document.	No action is required.

Signed and superseded documents

When you sign a document, you accept the current version and its visible notes. If a later regeneration changes that document, the earlier approval becomes superseded.

1. Open the changed document

   Read the new content and compare the reason for regeneration.

2. Resolve new open items

   Use the Assistant if a decision or correction is needed.

3. Approve the current version

   Re-approve only after the current document reflects your decision.

Project health and before-go-live items

The Project Health panel collects warnings, blockers, review notes, and tasks that should be completed before production launch. These are not all equal:

• a review note is a visible assumption, decision, risk, or warning that deserves your attention; it can be accepted and tracked and does not automatically mean the document is broken;
• a before-go-live item may be completed during development;
• a blocker prevents dependent work;
• a repair means the document cannot safely be approved as written.

The Review Notes number counts the currently visible review-note items across the Blueprint. Open the related document to read each item. Signing a document accepts the notes visible in that version; it does not silently remove them.

Reported Problems in App Structure

Reported Problems are unresolved consistency findings returned with the App Structure, such as a navigation link that references a feature missing from the map. The badge is the total number of findings in the list, not the number of feature cards. These findings are not automatically resolved just because the canvas rendered successfully.

Review every finding before approval. Correct the product decision or source context when necessary, then use the Assistant proposal and regenerate the affected document. A repaired finding no longer appears in the current unresolved list.

Do not sign a Blocked or Needs Repair document only to make the progress counter turn green. Approval represents your acceptance of that exact version.