Dispatch is a static Vite/React scaffold for a local-first product-shaping studio.
Start Here Today
Refine docs-view compactness and readiness-card evidence behavior, especially Deck's Docs / freshness hover/focus behavior, before tuning readiness heuristics or adding automation.
Markdown remains the source of truth. This dashboard summarizes the active orientation packet so the steward can see current state, next work, stale signals, and boundaries without reading every conceptual doc first.
Current Product Shape
What the active docs say exists now
The current V1 center is visible in the app: loose idea -> path choice -> advisory workshop -> Strong Design Brief -> AI-production planning document -> human decision.
The Projects / New Project surface has display-only local textarea/path state and can preview the brief-quality loop without saving, submitting, persisting, or dispatching work.
The Strong Design Brief Studio Preview is the primary V1 artifact surface.
The Strong Brief readiness rubric is presented as an artifact-quality standard, not an approval gate.
The AI-production planning document preview is the secondary readiness artifact. It names candidate slices, likely surfaces, acceptance criteria, validation expectations, risks, open questions, and human approval before coding.
Hybrid Project Readiness
Directional build-area signals
Readiness signals are directional orientation cues, not exact delivery percentages.
Frontend
SolidGap: The Projects / New Project surface has display-only local textarea/path state and can preview the brief-quality loop without saving, submitting, persisting, or dispatching work.
Evidence: docs/current-state.md: Dispatch is a static Vite/React scaffold for a local-first product-shaping studio.
View evidence
- docs/current-state.md: Dispatch is a static Vite/React scaffold for a local-first product-shaping studio.
- docs/current-state.md: The Projects / New Project surface has display-only local textarea/path state and can preview the brief-quality loop without saving, submitting, persisting, or dispatching work.
- docs/current-state.md: The Strong Design Brief Studio Preview is the primary V1 artifact surface.
Architecture
StrongGap: No source-backed gap was found for this area.
Evidence: docs/current-state.md: Source-owned sample fixtures exist under public/data-samples/ for AI Production stage assessment, context pack, validation con...
View evidence
- docs/current-state.md: Source-owned sample fixtures exist under public/data-samples/ for AI Production stage assessment, context pack, validation contract, advisory run, and local brief dossier examples.
- docs/current-state.md: Pure validators and smoke checks exist for AI Production samples, advisory-run contract/stub output, Local Brief / Decision Dossier, and Local Dossier Read-Model.
- docs/current-state.md: V1.5 source-owned runway packets exist for Local Brief / Decision Dossier v0 and Local Dossier Read-Model / Display Contract v0.
Data / backend
SolidGap: The app remains local/static/sample-derived and does not add backend persistence, live model calls, package generation, worker start, Deck runtime changes, runtime writes, push, d...
Evidence: docs/current-state.md: Source-owned sample fixtures exist under public/data-samples/ for AI Production stage assessment, context pack, validation con...
View evidence
- docs/current-state.md: Source-owned sample fixtures exist under public/data-samples/ for AI Production stage assessment, context pack, validation contract, advisory run, and local brief dossier examples.
- docs/current-state.md: Pure validators and smoke checks exist for AI Production samples, advisory-run contract/stub output, Local Brief / Decision Dossier, and Local Dossier Read-Model.
- docs/current-state.md: V1.5 source-owned runway packets exist for Local Brief / Decision Dossier v0 and Local Dossier Read-Model / Display Contract v0.
Validation
SolidGap: If a daily dashboard update finds that current-state, next-steps, or session-brief no longer mention recently landed work, the dashboard should flag the active docs as stale inste...
Evidence: docs/current-state.md: It names candidate slices, likely surfaces, acceptance criteria, validation expectations, risks, open questions, and human app...
View evidence
- docs/current-state.md: It names candidate slices, likely surfaces, acceptance criteria, validation expectations, risks, open questions, and human approval before coding.
- docs/current-state.md: Source-owned sample fixtures exist under public/data-samples/ for AI Production stage assessment, context pack, validation contract, advisory run, and local brief dossier examples.
- docs/current-state.md: Pure validators and smoke checks exist for AI Production samples, advisory-run contract/stub output, Local Brief / Decision Dossier, and Local Dossier Read-Model.
Docs / freshness
StrongGap: No source-backed gap was found for this area.
Evidence: docs/: All active orientation docs were found with current review dates.
View evidence
- docs/: All active orientation docs were found with current review dates.
Automation
SolidGap: Dispatch does not yet have a morning automation that refreshes the dashboards before the workday.
Evidence: docs/current-state.md: A local daily-project-orientation Codex skill exists and can regenerate Dispatch, Deck, SleepLately, and the central orientati...
View evidence
- docs/current-state.md: A local daily-project-orientation Codex skill exists and can regenerate Dispatch, Deck, SleepLately, and the central orientation index from the active Markdown packets.
- docs/current-state.md: The shared docs-view generator now emits the accepted hybrid project-shape surface: directional build-area readiness, freshness/confidence gaps, hover evidence, and source-backed...
- docs/current-state.md: The shared docs-view generator has a first compact-density pass and no longer emits native readiness-card title tooltips.
Decision Radar
Important source-backed choices and missing information
Click a decision to inspect evidence; source Markdown remains authoritative.
Confidence: medium
Freshness: stale source
Make steward decision points explicit without turning every step into a gate
The front-door workflow only works if approval, revision, pause, and rejection moments are clear.
Confidence: medium
Freshness: stale source
Preserve depth control between quick prototype and full design paths
The product direction depends on meeting rough ideas with the right level of effort.
Confidence: medium
Freshness: stale source
Keep validation-contract status display-only until a separate fixed intent is approved
Validation readiness is useful only if it stays separate from execution authority.
Confidence: medium
Freshness: stale source
Treat local dossier decisions as advisory readiness, not coding approval
The dossier can preserve project-shaping history without becoming an execution gate.
Confidence: medium
Freshness: stale source
Use the dossier read model for bounded metadata before persistence or live state
A bounded read model lets the reviewer inspect state without exposing raw fixture payloads or mutation authority.
Confidence: medium
Freshness: current
Defer morning automation until manual refreshes stay trustworthy
The dashboard should first prove that manual refreshes report changes and stale docs clearly.
Next Useful Work
Recommended steward orientation
Refine docs-view compactness and readiness-card evidence behavior, especially Deck's Docs / freshness hover/focus behavior, before tuning readiness heuristics or adding automation.
Do not summarize every conceptual Dispatch doc into the daily dashboard.
Stale / Missing Signals
What should stay visible
Dispatch does not yet have live advisory agents, provider calls, persisted local projects, saved dossier state, or a real backend.
Dispatch does not yet have a morning automation that refreshes the dashboards before the workday.
The generated docs-view still needs readiness-card evidence interaction polish: the custom hover/focus evidence feels too text-heavy, and Deck's Docs / freshness card only exposes evidence from the lower half of the card.
The older conceptual docs are useful source references, but they are too broad to be treated as the daily dashboard input set.
The current V1 acceptance checkpoint is frozen for planning, but V1.5 work still needs deliberate selection from bounded local-first packets.
The repo has no formal rule yet requiring normal feature work to update docs/current-state.md, docs/next-steps.md, and docs/session-brief.md.
- No stale or missing active docs detected by the generator.
Product / Design / Architecture
Direction to carry into work
Dispatch should feel like a calm operating desk for product shaping.
The first screen should help the steward understand what matters now, not sell the product back to them.
Primary surfaces should use plain language around state, evidence, decision, and boundary.
The Strong Design Brief is the visual and conceptual center of V1.
Vite
React
JavaScript
Plain CSS
Validation
Checks named by the source docs
- Use these commands for ordinary Dispatch app and docs-view validation:
- Focused source-owned fixture checks:
These checks prove structure and behavior only when freshly run. They do not prove source docs are current.
Source Map
Files behind this dashboard
Repo overview, commands, and documentation entry point.
Found - reviewed nullWhat exists now, what works, what is incomplete, and stale signals.
Found - reviewed 2026-05-22Recently completed work, recommended next moves, and work to avoid.
Found - reviewed 2026-05-22Product north star, current product shape, and roadmap posture.
Found - reviewed 2026-05-22Experience principles, visual direction, and interface guardrails.
Found - reviewed 2026-05-22Stack, app structure, data model, boundaries, and technical assumptions.
Found - reviewed 2026-05-22Validation commands, QA expectations, and evidence requirements.
Found - reviewed 2026-05-22Compact restart context, immediate next move, caveats, and reminders.
Found - reviewed 2026-05-22