Design-Led Autonomy
A visible path
to proof.
One agreed goal moves from the Maya brief through Susie design, Sam implementation, and reviewable proof. This page explains the intended route; it does not launch a mission.
See the workflow01 / The handoff route
Autonomy.
With a clear
line of sight.
One agreed goal. Six deliberate handoffs. Each owner moves the mission forward with something the next person can inspect.
Sequence matters. Design comes first.- 01
Maya / Agreement
Make the goal explicit.
Agree one outcome, acceptance criteria, and the boundaries of the mission.
Handoff: an agreed brief
- 02
Susie / Design
Give the goal a shape.
Supply the design before Sam implements: hierarchy, responsive states, and interaction intent.
Handoff: the approved design guide
- 03
Sam / Implementation
Build within the boundary.
Turn the design into a working page within the agreed scope.
Handoff: a reviewable build
- 04
Quinn / Behavior
Check what it actually does.
Check behavior, including keyboard use, retry limits, reset, and cancellation.
Handoff: recorded functional findings
- 05
Chromium + Susie / Rendering
Look at the real result.
Chromium captures desktop and narrow rendering. Susie then reviews those actual screenshots for hierarchy, spacing, typography, and overflow.
Handoff: captures and visual findings
- 06
Maya / Verified preview
Report the proof.
Report a verified preview only after behavior checks and screenshot review, with evidence and remaining limitations.
Handoff: a preview worth reviewing
02 / The mission controls
A retry has
a boundary.
Progress needs a stopping rule.
Try the policy in three attempts.
Ready. This illustration allows two retries after an initial failed check.
Retries used: 0 of 2.
03 / What counts as proof
Evidence.
Before confidence.
A beautiful concept is the beginning. A verified preview needs a record of the build and the checks behind it.
Required evidence for a verified preview
- Design suppliedRequired
- Implementation reviewedRequired
- Behavior checkedRequired
- Desktop capturedRequired
- Narrow capturedRequired
- Screenshots reviewedRequired
- Maya reportRequired
This ledger describes the evidence required. It does not claim that these checks have passed.
The principle
Small scope. Clear ownership.
Reviewable proof.
Verification is reported only after behavior checks and actual screenshot review.
The public pages explain the intended route; they do not launch a mission. Check what is available and what access a real start requires.
Check access and setup requirements