Skip to main content
A document has a content status and a review state. The Blueprint also has one global approval state.

​
Document content statuses

While any document is being created, Project Health shows Generating instead of its normal review badge. Blueprint Summary polls the stored run state while it is open, so finished cards and Project Health update without reloading the whole page.

​
Not yet reviewed and Reviewed

  • Not yet reviewed means you have not opened the current version of one of the 10 document cards.
  • Reviewed means you opened that current document page. It records review only; it is not an approval signature.
  • A regenerated, restored, or newly published version can return a document to Not yet reviewed.
Review does not automatically settle an explicit decision. After the decision is genuinely resolved and the owning document has no remaining actionable item, its content status returns to the green Ready state. A reviewed document with no genuine open decision must not remain Ready — your decision needed.

​
Sign Approve Blueprint

There is one approval for the complete current document set. There is no per-document Sign Approve action.
1

Finish generation

Wait until the document spinners stop and Project Health no longer shows Generating.
2

Review all 10 current documents

Open every current document card until each shows Reviewed. This includes opening a Not Required stub once.
3

Clear approval blockers

Resolve any Needs Repair or Blocked item. Regenerate affected documents and review their new versions.
4

Approve the current set

In Blueprint Documents, select Sign Approve Blueprint. This accepts the current Blueprint as one connected package.
Project ZIP remains locked until global approval succeeds. If regeneration, restore, or a new version changes the current set, review it and approve again before exporting another ZIP.

​
Project health and before-go-live items

The Project Health panel collects blockers, review notes, and work 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 attention; it does not automatically mean a document is broken;
  • a Before go-live item may be completed during implementation;
  • a blocker prevents dependent work;
  • a repair means the current document cannot safely join an approved Blueprint.
The Review Notes number counts visible review-note items across the Blueprint. Open the related document to read each item. Global approval accepts the notes visible in the complete current set; it does not silently remove them.

​
Reported Problems in App Structure

Reported Problems are unresolved consistency findings returned with App Structure, such as a navigation link that references a feature missing from the map. The badge is the total number of findings, even when the panel shows only a shorter preview. These findings are not automatically resolved because the canvas rendered successfully. Review every finding before global approval. Correct the product decision or source context when necessary, then use an Assistant proposal and regenerate the affected document. A repaired finding no longer appears in the current unresolved list.
Do not approve a Blueprint with a Blocked or Needs Repair document. Approval represents your acceptance of the complete current document set.