Your First Approved Design

Goal: an empty organization to an approved design, in one sitting. This is the shortest honest path; every step links to the full page when you want more.

1. Create the Package

New Design Package, titled for the solution. (Details)

2. Give It Enough Input to Matter

On Design Inputs, fifteen minutes here beats an hour of iteration later:

• A two-sentence summary of what the solution is.
• Five to ten requirements, phrased one capability each.
• Data classes the solution touches; sensitive classes are what make the security tiers appear. (Input fields)
• The regulations that apply. (Details)

3. Run the Design

Architecture → Run Automated Design. The run either completes or pauses with decisions needed; both are success. (The full loop)

4. Decide the Gaps

For each open capability, Choose an option (or type your own), then Apply. Your decisions are approved into the technology catalog and stick permanently; the re-run converges. (Gap decisions)

5. Look at What You Got

The Design segment shows components and flows; Diagrams renders the C4 views; Assurance scores every control with reasons. If a control fails, Remediate Findings feeds it back to the loop. (Compliance results)

6. Approve It

On Review & Approval: assign a reviewer, clear anything on the readiness board, and submit. The reviewer approves (where separation of duties applies, the approver is someone other than the author; invite a colleague). Approval locks the package and captures the baseline. (Reviewers and decisions)

What Just Happened

You now hold a design generated only from approved technology, scored against your controls, decided by humans where it mattered, and approved on the record; and from this moment, drift detection watches it.