Troubleshooting and FAQ

The questions that actually come up, with the short answer first.

The run keeps pausing and asking for technology decisions

That is the loop working: each open capability needs a decision once. Choose options and Apply; applied decisions are approved into the catalog and stick permanently, so the next run selects them automatically. If the same capability re-asks after an apply, check the catalog entry exists and carries the right capability; and note that selections must be applied, not just clicked. (Gap decisions)

Approve is disabled and I don't see why

Approve enables only when the readiness board is clear. Open it: every blocker names its condition and links to the surface that resolves it: gaps, open risks, missing sign-off, or an undecided scope proposal.

A re-run added components I didn't ask for

Additions that cited a driving control or requirement land with the citation shown; anything uncited is quarantined as a proposal on the Architecture tab; accept or discard each. Check Preserve Scope on the next run to tighten further. (Scope guard)

My delivery export stopped partway

Run it again. Exports are resumable: items already created are skipped, never duplicated, and per-item errors are shown on the items so the rest completes. (Delivery export)

A drift finding won't clear

Findings auto-resolve when their condition clears, so a persistent finding means the condition persists; use its detail to see what is still true. If the divergence is understood and accepted, Acknowledge it: recorded, visible, never blocking. (The playbook)

The diagram looks wrong

Diagrams regenerate from the design, so a wrong picture means the design (or your rendering standards) says something wrong. Fix it there; there is no picture to edit, on purpose.

A settings page shows a lock

Your plan does not include that feature yet; the lock links to Billing, and the plans overview shows what arrives where. Nothing is hidden; gated is visible by design.

Someone edited an approved design

Nothing prevents it (emergencies are real); drift detection raises a Design Changed finding instead. If the change should stand, cut a revision and make it official; if not, restore the design and the finding resolves itself.