Design Review (Deliberation)
The design review is a structured critique of the completed design by multiple AI reviewers, each with a different lens: security, cost, and compliance. It exists to catch what single-pass generation and rule-based checks miss: the awkward trust-boundary crossing, the needlessly expensive choice, the control satisfied in letter but not in spirit.
Plan Availability
The multi-agent design review is available on the Large plan and above.
Run a Review
Run it from the Assurance tab once a design is complete. Each reviewer examines the same design and returns findings: specific, actionable, citing the exact component or flow, never a wholesale redesign. The review concludes with a verdict:
| Verdict | Meaning | Effect on Approval |
|---|---|---|
| Pass | No material issues | None |
| Concerns | Non-blocking findings worth addressing | None; visible to reviewers |
| Blocked | At least one issue that must be resolved | Approval requires Risk Sign-off |
A review is tied to the design version it examined; after the design changes, run it again. A stale review of an older version never gates the current one.
What Is in Scope
Ownership decides severity. Systems the design does not control (external counterparties, and the legacy system a migration is moving off) are integration context: a deficiency internal to them is reported as transition context at reduced severity and can never block the design. How your design integrates with them (an unencrypted flow into the legacy system, missing cutover controls) is fully in scope. The reason you are replacing a system is not an argument against the replacement.
Grounded, Not Free-Floating
Reviewers use your uploaded knowledge documents as citable reference: a vendor security paper can confirm an encryption claim, and an internal standard can back a finding. As everywhere in the product, document content is data, never instructions; nothing written inside a document can soften a finding.
Acting on Findings
Findings feed the same loop as everything else: Remediate Findings hands them to the next design pass, architect edits address them directly, and findings that represent accepted realities belong in the Risk Register as deliberate treatments.