ai-design-context 0.4.0

package/patterns/progressive-detail.md

@@ -0,0 +1,113 @@
+---
+id: PAT-00004
+alias: PAT-004
+slug: progressive-detail
+title: Progressive Detail
+object_type: pattern
+status: draft
+version: 0.1.0
+category: ux
+tags:
+  - ux
+  - progressive-disclosure
+maturity: seed
+risk_level: medium
+relationships:
+  - type: requires
+    target: RULE-00006
+  - type: requires
+    target: RULE-00002
+  - type: requires
+    target: RULE-00008
+  - type: requires
+    target: RULE-00009
+  - type: related_to
+    target: PAT-00006
+---
+
+# Progressive Detail
+
+## Purpose
+
+Keep the default task simple while preserving access to advanced fields.
+
+## User Goal
+
+Complete or understand the item first, then add detail only when needed.
+
+## Product Context
+
+Items that start simple but can gain metadata, settings, states, notes, or scheduling.
+
+## Use When
+
+- Most users need only a small subset of fields at first.
+- Advanced metadata is optional or can be added later.
+- The product must support both casual and power users.
+
+## Do Not Use When
+
+- Hidden information is required for trust, safety, or accountability.
+- Users must compare many items by the hidden metadata.
+- Advanced controls are the primary workflow.
+
+## UX Rules
+
+- `UX-002` Progressively Disclose Power
+- `PRD-002` Low-Friction Capture Before Organization
+
+## Accessibility Rules
+
+- `A11Y-001` 44x44 Touch Targets
+
+## Mobile Behavior
+
+Show essential fields first. Reveal optional detail through edit, details, expand, or more controls that remain reachable.
+
+## Desktop Behavior
+
+Use available width for secondary detail only when it supports scanning or editing. Do not turn optional metadata into a wall of fields.
+
+## Empty State
+
+Show the minimal item shape and the action to add the first item.
+
+## Loading State
+
+Load essential content first; defer optional detail without shifting the main item.
+
+## Error State
+
+If optional detail fails, keep the core item usable and show targeted recovery.
+
+## Required Rules
+
+- `UX-002` Progressively Disclose Power
+- `PRD-002` Low-Friction Capture Before Organization
+- `VIS-001` Semantic Tokens Only
+- `A11Y-001` 44x44 Touch Targets
+
+## Related Research
+
+- `research/products/things-3.md`
+- `research/products/apple-reminders.md`
+- `research/products/telegram.md`
+
+## Related Patterns
+
+- Parent: none
+- Child: none
+- Alternative: `object-status-list.md` when comparison requires visible metadata
+- Depends on: none
+
+## Examples
+
+- A task app detail view hides notes, repeat settings, and tags until edit.
+- A reminder shows title and due time first, then exposes location and subtasks.
+
+## Agent Checklist
+
+- Which fields are essential at first glance?
+- Which fields can wait until edit or inspection?
+- Is hidden detail discoverable?
+- Does hiding detail harm comparison or accountability?

package/patterns/quick-capture.md

@@ -0,0 +1,132 @@
+---
+id: PAT-00002
+alias: PAT-002
+slug: quick-capture
+title: Quick Capture
+object_type: pattern
+status: draft
+version: 0.1.0
+category: workflow
+tags:
+  - workflow
+  - capture
+maturity: seed
+risk_level: medium
+relationships:
+  - type: requires
+    target: RULE-00002
+  - type: requires
+    target: RULE-00005
+  - type: requires
+    target: RULE-00006
+  - type: requires
+    target: RULE-00009
+  - type: requires
+    target: RULE-00010
+  - type: requires
+    target: RULE-00011
+  - type: requires
+    target: RULE-00012
+  - type: related_to
+    target: PAT-00003
+---
+
+# Quick Capture
+
+## Purpose
+
+Let users record intent before they organize details.
+
+## User Goal
+
+Add a task, note, reminder, message, or idea before it is forgotten.
+
+## Product Context
+
+Everyday consumer workflows where speed matters more than complete metadata at creation time.
+
+## Use When
+
+- The smallest valid item can be saved with minimal input.
+- Metadata can be added after creation.
+- Capture is more frequent than organization.
+
+## Do Not Use When
+
+- Compliance or safety requires required fields before creation.
+- The captured item is invalid without structured data.
+- The workflow is primarily comparison or review.
+
+## UX Rules
+
+- `PRD-002` Low-Friction Capture Before Organization
+- `UX-001` Thumb-Zone Primary Actions
+- `UX-002` Progressively Disclose Power
+
+## Accessibility Rules
+
+- `A11Y-001` 44x44 Touch Targets
+- `A11Y-002` Textual Input Error Recovery
+- `A11Y-003` Visible Keyboard Focus
+
+## Performance Rules
+
+- `PERF-001` Reserve Layout Space For Asynchronous Content
+
+## Mobile Behavior
+
+Provide a reachable create action and a short input path. Do not force category, date, owner, or priority before save.
+
+## Desktop Behavior
+
+Support keyboard-first entry and quick submit. Keep optional metadata adjacent but secondary.
+
+## Empty State
+
+Show the create action and one concise cue for what can be captured.
+
+## Loading State
+
+Preserve entered content, reserve the same input and row geometry, and show saving progress without moving the input or nearby actions.
+
+## Error State
+
+Keep the user's input, identify the affected input and failed condition in text, and offer retry.
+
+## Required Rules
+
+- `PRD-002` Low-Friction Capture Before Organization
+- `UX-001` Thumb-Zone Primary Actions
+- `UX-002` Progressively Disclose Power
+- `A11Y-001` 44x44 Touch Targets
+- `A11Y-002` Textual Input Error Recovery
+- `PERF-001` Reserve Layout Space For Asynchronous Content
+- `A11Y-003` Visible Keyboard Focus
+
+## Related Research
+
+- `research/products/apple-reminders.md`
+- `research/products/things-3.md`
+- `research/products/telegram.md`
+
+## Related Patterns
+
+- Parent: `daily-home-surface.md`
+- Child: none
+- Alternative: none
+- Depends on: `mobile-primary-action.md` for touch-first placement
+
+## Examples
+
+- A shopping list app lets a user add "Buy milk" before assigning list, owner, or due time.
+- A reminder app saves a title first and lets scheduling happen later.
+
+## Agent Checklist
+
+- What is the smallest valid item?
+- How many decisions are required before saving?
+- Can optional metadata be added later?
+- Is failed save recoverable without losing input?
+- Does loading preserve the input and surrounding layout geometry?
+- Is the validation error understandable without relying on color?
+- Does every keyboard-operable capture control keep visible focus?

package/prompts/CONSEQUENTIAL_ACTION_REVIEW.md

@@ -0,0 +1,100 @@
+---
+id: PROMPT-00006
+alias: PROMPT-CONSEQUENTIAL-ACTION-REVIEW
+slug: consequential-action-review
+title: Consequential Action Review Prompt
+object_type: prompt
+status: active
+version: 0.1.0
+category: review
+tags:
+  - prompt
+  - review
+  - confirmation
+  - recovery
+  - agentic-ui
+maturity: validated
+risk_level: high
+last_reviewed_at: 2026-08-12
+relationships:
+  - type: requires
+    target: PAT-00007
+  - type: requires
+    target: RULE-00017
+  - type: requires
+    target: RULE-00007
+  - type: requires
+    target: RULE-00010
+  - type: related_to
+    target: RULE-00016
+---
+
+# Consequential Action Review Prompt
+
+## Objective
+
+Review a high-consequence action flow for context preservation, risk-proportional confirmation, recoverable challenge states, and agent approval boundaries.
+
+## Required Inputs
+
+- The action being reviewed and its consequence.
+- The affected object, critical inputs, side effects, and reversibility.
+- Screens, implementation, screenshots, or runnable prototype.
+- Default, confirmation, challenge, loading, error, retry, success, and cancelled states.
+- Whether the action is human-initiated, agent-initiated, or agent-assisted.
+
+## Instruction
+
+```text
+Review the provided flow using PAT-007, UX-006, UX-003, A11Y-002, and UX-005 when agentic work exists.
+
+Do not invent legal, compliance, security, financial, trading, or backend policy. Mark missing policy or implementation evidence as a gap.
+
+Verify that the flow preserves the affected object, critical inputs, side effects, reversibility, and recovery path through confirmation, challenge, loading, error, retry, success, and cancellation. For agentic work, verify that consequential side effects require explicit approval, remain interruptible before execution, and leave inspectable evidence.
+
+Return a verdict, severity-ordered findings, state coverage, and the rule or pattern supporting every finding.
+```
+
+## Output Contract
+
+```md
+## Verdict
+- Result: PASS | NEEDS WORK
+- Evidence reviewed:
+- Evidence gaps:
+
+## Consequence Map
+- Action:
+- Affected object:
+- Critical inputs:
+- Side effects:
+- Reversibility:
+- Required authority or challenge:
+
+## State Coverage
+- Default:
+- Confirmation:
+- Challenge:
+- Loading:
+- Error:
+- Retry:
+- Success:
+- Cancelled:
+
+## Agent Boundary
+- Agent involvement:
+- Approval point:
+- Interruption path:
+- Evidence or audit trail:
+
+## Findings
+For each finding:
+- Severity:
+- Evidence:
+- Impact:
+- Related IDs:
+- Smallest safe change:
+
+## Knowledge Gaps
+- Missing policy, evidence, or research:
+```

package/prompts/DESIGN_EVIDENCE_REVIEW.md

@@ -0,0 +1,49 @@
+---
+id: PROMPT-00005
+alias: PROMPT-DESIGN-EVIDENCE-REVIEW
+slug: design-evidence-review
+title: Design Evidence Review Prompt
+object_type: prompt
+status: draft
+version: 0.1.0
+category: review
+tags:
+  - prompt
+  - review
+  - evidence
+maturity: seed
+risk_level: medium
+relationships:
+  - type: requires
+    target: CHECK-00001
+---
+
+# Design Evidence Review Prompt
+
+## Objective
+
+Turn evidence from a design artifact, benchmark run, reference project, or implementation into a traceable review object.
+
+## Required Inputs
+
+- Target object or product surface.
+- Evidence artifacts: implementation, screenshots, benchmark output, or evaluation notes.
+- Claimed rules and patterns.
+
+## Instruction
+
+```text
+Review the supplied target using CHECK-00001.
+
+Do not invent evidence, design rules, benchmark results, or implementation behavior. Mark any unrendered, unmeasured, or untested claim as a gap.
+
+Produce a REVIEW object with a PASS or NEEDS WORK verdict, severity-ordered findings, coverage of applicable rules and patterns, cited evidence, and concrete next validation steps. A PASS requires direct evidence for the primary action, required states, accessibility behavior, and applicable mobile or performance claims.
+```
+
+## Output Contract
+
+- Verdict: `PASS` or `NEEDS WORK`.
+- Scope and evidence reviewed.
+- Findings: severity, gap, affected object or surface, and related IDs.
+- Coverage: checked and unverified rules, patterns, states, and constraints.
+- Handoff: exact follow-up evidence or change required.

package/prompts/GENERATED_INDEX.md

@@ -0,0 +1,11 @@
+# Generated Prompts Index
+
+This file is generated from registry metadata. Do not edit manually.
+
+| ID | Alias | Title | Category | Status | Maturity | File Path | Pattern References | Rule References | Checklist References |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| PROMPT-00002 | PROMPT-PROTOTYPE-REVIEW | Prototype Review Prompt | review | draft | seed | prompts/PROTOTYPE_REVIEW.md | related_to: PAT-001 / PAT-00001 Daily Home Surface<br>related_to: PAT-002 / PAT-00002 Quick Capture<br>related_to: PAT-003 / PAT-00003 Mobile Primary Action<br>related_to: PAT-004 / PAT-00004 Progressive Detail<br>related_to: PAT-005 / PAT-00005 Context-Preserving Preview<br>related_to: PAT-006 / PAT-00006 Object Status List<br>related_to: PAT-007 / PAT-00007 Consequential Action Confirmation | related_to: PRD-001 / RULE-00001 Daily Actions First<br>related_to: PRD-002 / RULE-00002 Low-Friction Capture Before Organization<br>related_to: IA-001 / RULE-00003 One Stable Home Surface<br>related_to: IA-002 / RULE-00004 Define The Object Model Before Screens<br>related_to: UX-001 / RULE-00005 Thumb-Zone Primary Actions<br>related_to: UX-002 / RULE-00006 Progressively Disclose Power<br>related_to: UX-003 / RULE-00007 Preserve Context During Inspection<br>related_to: VIS-001 / RULE-00008 Semantic Tokens Only<br>related_to: A11Y-001 / RULE-00009 44x44 Touch Targets<br>related_to: A11Y-002 / RULE-00010 Textual Input Error Recovery<br>related_to: PERF-001 / RULE-00011 Reserve Layout Space For Asynchronous Content<br>related_to: A11Y-003 / RULE-00012 Visible Keyboard Focus<br>related_to: A11Y-004 / RULE-00013 Reduce Non-Essential Interaction Motion<br>related_to: VIS-002 / RULE-00014 Keep Expression Subordinate To Content<br>related_to: UX-004 / RULE-00015 Use Motion To Explain State Continuity<br>related_to: UX-005 / RULE-00016 Expose Agent Work And Intervention<br>related_to: UX-006 / RULE-00017 Confirm Consequential Actions With Preserved Context | requires: CHECK-DESIGN-QA / CHECK-00001 Design QA Checklist |
+| PROMPT-00003 | PROMPT-TODO-BENCHMARK | Todo App Benchmark Prompt | generation | draft | seed | prompts/TODO_APP_BENCHMARK.md | requires: PAT-001 / PAT-00001 Daily Home Surface<br>requires: PAT-002 / PAT-00002 Quick Capture<br>requires: PAT-003 / PAT-00003 Mobile Primary Action<br>requires: PAT-004 / PAT-00004 Progressive Detail<br>requires: PAT-005 / PAT-00005 Context-Preserving Preview<br>requires: PAT-006 / PAT-00006 Object Status List | requires: PRD-001 / RULE-00001 Daily Actions First<br>requires: PRD-002 / RULE-00002 Low-Friction Capture Before Organization<br>requires: IA-001 / RULE-00003 One Stable Home Surface<br>requires: IA-002 / RULE-00004 Define The Object Model Before Screens<br>requires: UX-001 / RULE-00005 Thumb-Zone Primary Actions<br>requires: UX-002 / RULE-00006 Progressively Disclose Power<br>requires: UX-003 / RULE-00007 Preserve Context During Inspection<br>requires: VIS-001 / RULE-00008 Semantic Tokens Only<br>requires: A11Y-001 / RULE-00009 44x44 Touch Targets | None |
+| PROMPT-00004 | PROMPT-QUICK-CAPTURE-STATE-REVIEW | Quick Capture State Review Prompt | review | draft | seed | prompts/QUICK_CAPTURE_STATE_REVIEW.md | requires: PAT-002 / PAT-00002 Quick Capture | requires: PRD-002 / RULE-00002 Low-Friction Capture Before Organization<br>requires: A11Y-001 / RULE-00009 44x44 Touch Targets<br>requires: A11Y-002 / RULE-00010 Textual Input Error Recovery<br>requires: PERF-001 / RULE-00011 Reserve Layout Space For Asynchronous Content<br>requires: A11Y-003 / RULE-00012 Visible Keyboard Focus | None |
+| PROMPT-00005 | PROMPT-DESIGN-EVIDENCE-REVIEW | Design Evidence Review Prompt | review | draft | seed | prompts/DESIGN_EVIDENCE_REVIEW.md | None | None | requires: CHECK-DESIGN-QA / CHECK-00001 Design QA Checklist |
+| PROMPT-00006 | PROMPT-CONSEQUENTIAL-ACTION-REVIEW | Consequential Action Review Prompt | review | active | validated | prompts/CONSEQUENTIAL_ACTION_REVIEW.md | requires: PAT-007 / PAT-00007 Consequential Action Confirmation | requires: UX-006 / RULE-00017 Confirm Consequential Actions With Preserved Context<br>requires: UX-003 / RULE-00007 Preserve Context During Inspection<br>requires: A11Y-002 / RULE-00010 Textual Input Error Recovery<br>related_to: UX-005 / RULE-00016 Expose Agent Work And Intervention | None |

package/prompts/INDEX.md

@@ -0,0 +1,24 @@
+# Prompt Index
+
+Prompts apply patterns and rules to a specific agent task.
+
+Prompts should not introduce new design advice. They should reference existing patterns and rules.
+
+## Current Prompts
+
+- `PROTOTYPE_REVIEW.md` - reviews prototypes before refactoring.
+
+## Future Metadata
+
+Prompt objects should follow the metadata model in `docs/KNOWLEDGE_ENGINE.md`.
+
+Each prompt should define:
+
+- stable ID;
+- status;
+- version;
+- required patterns;
+- required rules;
+- last reviewed date.
+
+Manual indexes are transitional. Future indexes should be generated from registry metadata.

package/prompts/PROTOTYPE_REVIEW.md

@@ -0,0 +1,189 @@
+---
+id: PROMPT-00002
+alias: PROMPT-PROTOTYPE-REVIEW
+slug: prototype-review
+title: Prototype Review Prompt
+object_type: prompt
+status: draft
+version: 0.3.0
+category: review
+tags:
+  - prompt
+  - review
+  - prototype
+maturity: seed
+risk_level: medium
+relationships:
+  - type: related_to
+    target: PAT-00001
+  - type: related_to
+    target: PAT-00002
+  - type: related_to
+    target: PAT-00003
+  - type: related_to
+    target: PAT-00004
+  - type: related_to
+    target: PAT-00005
+  - type: related_to
+    target: PAT-00006
+  - type: related_to
+    target: PAT-00007
+  - type: related_to
+    target: RULE-00001
+  - type: related_to
+    target: RULE-00002
+  - type: related_to
+    target: RULE-00003
+  - type: related_to
+    target: RULE-00004
+  - type: related_to
+    target: RULE-00005
+  - type: related_to
+    target: RULE-00006
+  - type: related_to
+    target: RULE-00007
+  - type: related_to
+    target: RULE-00008
+  - type: related_to
+    target: RULE-00009
+  - type: related_to
+    target: RULE-00010
+  - type: related_to
+    target: RULE-00011
+  - type: related_to
+    target: RULE-00012
+  - type: related_to
+    target: RULE-00013
+  - type: related_to
+    target: RULE-00014
+  - type: related_to
+    target: RULE-00015
+  - type: related_to
+    target: RULE-00016
+  - type: related_to
+    target: RULE-00017
+  - type: requires
+    target: CHECK-00001
+---
+
+# Prototype Review Prompt
+
+Review a rendered or runnable prototype before refactoring.
+
+## Objective
+
+Identify the smallest evidence-backed changes that improve product clarity, visual hierarchy, state behavior, responsive quality, and accessibility without inventing a new product direction.
+
+## Required Inputs
+
+- User goal and primary action.
+- Prototype path, URL, screenshots, or runnable implementation.
+- Target platforms and viewports.
+- Existing components, tokens, and product design direction.
+- Focused graph context for the reviewed task.
+- Reference evidence when the requested change is visual exploration or polish.
+
+## Pattern Coverage
+
+Check whether a documented pattern applies:
+
+- `patterns/daily-home-surface.md`
+- `patterns/quick-capture.md`
+- `patterns/mobile-primary-action.md`
+- `patterns/progressive-detail.md`
+- `patterns/object-status-list.md`
+- `patterns/context-preserving-preview.md`
+- `patterns/consequential-action-confirmation.md`
+
+## Rule Coverage
+
+- `PRD-001`
+- `PRD-002`
+- `IA-001`
+- `IA-002`
+- `UX-001`
+- `UX-002`
+- `UX-003`
+- `VIS-001`
+- `A11Y-001`
+- `A11Y-002`
+- `PERF-001`
+- `A11Y-003`
+- `A11Y-004`
+- `VIS-002`
+- `UX-004`
+- `UX-005` when delegated or long-running agent work exists
+- `UX-006` when consequential actions, money movement, account access, destructive durable changes, external publishing, or agent side effects exist
+
+## Review Sequence
+
+1. Confirm the artifact can be rendered or inspected. Mark missing evidence instead of guessing.
+2. Describe the current user goal, primary action, secondary actions, and object states.
+3. Check applicable patterns and rules.
+4. Review the content layer, functional layer, focal emphasis, density, typography, spacing, and semantic visual roles.
+5. Review default, loading, empty, error, success, disabled, and permission states that apply.
+6. Review desktop and mobile behavior when layout is affected.
+7. Review focus, labels, target size, contrast-sensitive choices, textual errors, and reduced motion.
+8. Review start state, end state, purpose, timing role, and fallback for meaningful motion.
+9. When agentic work applies, review queued, active, blocked, review-ready, complete, failed, cancelled, and intervention behavior.
+10. When consequential actions apply, review affected object, critical inputs, side effects, reversibility, confirmation, challenge, error, retry, success, cancellation, and audit evidence.
+11. Compare recommendations with supplied references at the level of abstract behavior; do not copy a brand composition or proprietary asset.
+
+## Instruction
+
+Use `CHECK-00001`.
+
+Do not redesign immediately. Before broad visual design, visual exploration, or product polish, ask whether the user wants multiple design options or one conservative implementation path. Do not invent rendered behavior, visual evidence, benchmark results, or unsupported design rules.
+
+Produce a severity-ordered review and a phased change plan. Every recommendation must cite the inspected artifact and an applicable rule, pattern, token, component convention, or explicit research gap.
+
+## Output Contract
+
+```md
+## Verdict
+- Result: PASS | NEEDS WORK
+- Evidence reviewed:
+- Evidence gaps:
+
+## Product And Interaction
+- User goal:
+- Primary action:
+- Main friction:
+
+## Visual Direction
+- Content layer:
+- Functional layer:
+- Focal emphasis:
+- Generic-AI or overdesign risk:
+- Reference evidence:
+
+## State Coverage
+- Missing or weak states:
+- Agent lifecycle states, when applicable:
+- Consequential action states, when applicable:
+
+## Responsive And Accessibility
+- Desktop:
+- Mobile:
+- Keyboard and focus:
+- Contrast and target size:
+- Reduced motion:
+
+## Findings
+For each finding:
+- Severity:
+- Evidence:
+- Impact:
+- Related IDs:
+- Smallest safe change:
+
+## Phased Plan
+1. Tokens and reusable roles.
+2. Components and states.
+3. Layout and responsive behavior.
+4. Interaction and motion.
+5. Visual QA and accessibility verification.
+
+## Knowledge Gaps
+- Observation or research needed:
+```

package/prompts/QUICK_CAPTURE_STATE_REVIEW.md

@@ -0,0 +1,74 @@
+---
+id: PROMPT-00004
+alias: PROMPT-QUICK-CAPTURE-STATE-REVIEW
+slug: quick-capture-state-review
+title: Quick Capture State Review Prompt
+object_type: prompt
+status: draft
+version: 0.2.0
+category: review
+tags:
+  - prompt
+  - review
+  - capture
+  - states
+maturity: seed
+risk_level: medium
+relationships:
+  - type: requires
+    target: PAT-00002
+  - type: requires
+    target: RULE-00002
+  - type: requires
+    target: RULE-00009
+  - type: requires
+    target: RULE-00010
+  - type: requires
+    target: RULE-00011
+  - type: requires
+    target: RULE-00012
+  - type: cites
+    target: evidence/todo/2026-09-28-codex-paired-todo/EVALUATION.md
+---
+
+# Quick Capture State Review Prompt
+
+## Objective
+
+Review an existing quick-capture flow for low friction, accessible recovery, stable loading, and keyboard-operable state behavior.
+
+## Required Inputs
+
+- The capture surface or implementation.
+- Default, loading, validation-error, failed-save, and success behavior.
+- Target platform and viewport constraints.
+- A realistic populated list as well as an empty list, and a way to reproduce save failure and retry.
+
+## Instruction
+
+```text
+Review the provided quick-capture flow using PAT-002 and its required rules.
+
+Do not invent new product features, rules, or patterns. Identify only observable gaps in the current capture path.
+
+Verify that the smallest valid item can be saved with minimal input; controls meet touch and keyboard needs; validation identifies the affected input in text; loading preserves input and layout geometry; and focus remains visible through recovery.
+
+Test capture from a fresh page using only the keyboard with a realistically populated list. Record the navigation steps, including the Tab count, and any discoverable direct route to capture. A reachable input can still impose avoidable friction when it follows every list control; assess the user task under PRD-002 rather than inventing a universal Tab-count limit. Verify focus visibility separately under A11Y-003.
+
+Compare the input, submit control, feedback region, and first list row across default, saving, failed-save, retry, and success states. Include wrapping error text and changing action labels when checking geometry under PERF-001. Measure actual touch areas, including associated labels, under A11Y-001.
+
+Return a verdict, severity-ordered findings, state coverage, and the rule or pattern supporting every finding.
+```
+
+## Output Contract
+
+- Verdict: `PASS` or `NEEDS WORK`.
+- Findings: severity, observed issue, supporting ID, and concrete recovery behavior.
+- State coverage: default, loading, validation error, failed save, success, and keyboard focus.
+- Keyboard route: starting state, populated item count, Tab count, direct routes tried, and observed friction.
+- Geometry evidence: viewport, input/action hit areas, and measured or visibly observed movement across saving/error/retry states.
+- Gaps: missing evidence rather than invented guidance.
+
+## Review Evidence
+
+The [paired rendered Todo evaluation](../evidence/todo/2026-09-28-codex-paired-todo/EVALUATION.md) found a 29-versus-4 Tab capture path, a 22px baseline error-layout shift, and changing save-button widths in both outputs. These observations motivate more concrete checks of the existing rules; they do not establish new universal thresholds. This prompt revision was made after that run and has not itself been validated by a new paired generation.