Establish Codex app product and design source-of-truth docs

[nisavid]

This was generated by AI during triage.

Summary

Establish root PRODUCT.md and root DESIGN.md as the accepted product and design source-of-truth docs for Codex app UI and visual-design work.

This repository currently has no root PRODUCT.md or DESIGN.md; $impeccable reports NO_PRODUCT_MD. Before backlog issues change UI layout, visual hierarchy, typography, spacing, color, iconography, motion, screenshots, settings UI, mobile setup UI, empty/error states, or user-facing UI acceptance criteria, the repo needs Codex-specific product and design docs that future work can cite.

Required Workflow

• Run $impeccable init from the repo root and follow its interview flow before writing PRODUCT.md.
• Ground PRODUCT.md in existing repo docs and maintainer context, including README, domain docs, support-routing guidance, threat-model/security backlog material, and the README visual-capture contract.
• Set the default register to product unless the Impeccable interview explicitly chooses otherwise.
• Create root PRODUCT.md with users, product purpose, brand personality, anti-references, design principles, and accessibility/inclusion requirements.
• Create root DESIGN.md in a Stitch-compatible structure.
• Ground DESIGN.md in existing docs, actual source, generated app output or screenshots where available, and Stitch-compatible design-system synthesis.
• Use exact observed color, typography, spacing, component, and visual-state facts where known. Record unresolved evidence gaps instead of inventing design language.
• Run any local linter or validator that exists for these docs. If none exists, record that no validator was found and perform a reviewer pass against Impeccable and Stitch requirements.

Gate

This issue blocks UI and visual-design work only, including:

• UI layout and visual hierarchy
• typography, spacing, color, iconography, and motion
• screenshots and visual acceptance criteria
• settings UI and mobile setup UI
• empty states, error states, connected-state presentation, and user-facing UI copy where copy shapes the interface

Mixed issues may proceed for non-visual work, but their UI or visual-design portions must wait until PRODUCT.md and DESIGN.md are accepted and cited.

Non-goals

This gate does not block strictly non-visual security review, packaging work, updater work, runtime hardening, test work, evidence gathering, or non-visual implementation planning.

Acceptance Criteria

• Root PRODUCT.md exists and reflects an Impeccable init interview plus repo-grounded evidence.
• Root DESIGN.md exists and is Stitch-compatible.
• The PR or issue notes record the docs, source, visual evidence, and validator/review evidence used.
• A review verifies both docs are Codex-specific, use this fork's terminology, and do not read like generic app-design boilerplate.
• Future UI/visual backlog work can cite these docs for vocabulary, design constraints, and acceptance criteria.

Known Dependent Issue

• Review experimental remote-control and Codex mobile host boundary #59 definitely overlaps because it includes remote-control UI copy, mobile setup flow, connected-state presentation, empty/error states, and visual acceptance risk.

[coderabbitai]

🔗 Related PRs

#12 - docs: audit fork divergence docs [merged]
#44 - docs: capture upstream README sync guidance [merged]
#45 - docs: prune stale backlog sources [merged]
#68 - docs(backlog): migrate backlog items to issues [merged]
#82 - docs(readme): define visual capture contract [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!