01Fit confirmed
Intake
- Goal
- Clarify product truth, audience, required content and usable sources.
- Evidence
- A complete brief with explicit gaps.
- Approval
- Scope accepted before production.
INSIDE THE 72H SPRINT
Six gates. One controlled direction.
The public view shows the decisions that matter. The complete ledger remains available as read-only evidence without exposing client data or internal scratch notes.
02Direction ready
Position
- Goal
- Define Core Truth, Opposing Default, trust need and visual tension.
- Evidence
- A position that can guide visual decisions.
- Approval
- Strategy gate approved.
03Route selected
Select
- Goal
- Compare safe, distinctive and experimental routes.
- Evidence
- Selection rationale and rejected risks.
- Approval
- Human selection recorded.
04System assembled
Build
- Goal
- Connect recognition, behavior, generation and transfer codes.
- Evidence
- A focused visual direction and application logic.
- Approval
- Direction status visible.
05QA complete
Verify
- Goal
- Check continuity, contrast, claims, risk, accessibility and asset status.
- Evidence
- Repair notes and approval evidence.
- Approval
- No silent QA pass.
06Package clean
Deliver
- Goal
- Separate final client files from internal QA and working material.
- Evidence
- Readable guide, machine-readable tokens and generator-ready prompt files.
- Approval
- Versioned handoff approved.
Open the complete 34-item read-only sprint ledger
Intake
- Technical truth
- Audience
- Mandatory content
- Reference / anti-reference
Positioning
- Core challenge
- Purpose
- Brand DNA
- Trust need
- Visual tension
Directions
- Safe
- Distinctive
- Experimental
- Decision rationale
System
- Logo logic
- Color roles
- Typography
- Visual world
- Product states
Applications
- Website
- Product UI
- Pitch
- Social / launch
Proof
- Before / after
- AI control specification
- Do / Don’t
- Asset status
QA
- Content preservation
- Accessibility
- Risk guard
- Human approval
Delivery
- Core package
- Extended system
- Readme
- Next steps
Transparency: Portfolio method proof. This is not client software, an editable project board or a normal delivery file. No client data or confidential workshop notes are included.