Dispatch Daily Orientation

30-second project scan

Product-shaping studio exists. Next slice needs direction.

Dispatch is a static Vite/React scaffold for a local-first product-shaping studio. The useful PM view is: Turn rough project ideas into implementation-ready briefs. Main blocker: Steward decision on the next slice.

Project stage: Product shaping
Main blocker: Steward decision on the next slice
Business goal: Turn rough project ideas into implementation-ready briefs
Docs health: 1 docs need review

Best next agent request

Refine the next product-shaping dashboard slice.

Refine docs-view compactness and readiness-card evidence behavior, especially Deck's Docs / freshness hover/focus behavior, before tuning readiness heuristics. Keep an eye on the weekday refresh/deploy automation after the new central overview deploy step.

Do not delegate yet

Execution authority or overbroad scope.

Do not turn generated dashboards into the source of truth, runtime workers, package handoffs, or a dump of every conceptual doc.

Milestone Gates

What has to become true before the next milestone

These are delegation checkpoints for a nontechnical project manager.

Gate 1

Project direction

Confirm the business goal and current stage before assigning new work.

Ask: restate the project direction in plain language.

Gate 2

Source freshness

Check whether active docs are current, missing, or old but quiet.

Ask: list source docs that need attention.

Gate 3

Main blocker

Identify the blocker that prevents the next milestone from being treated as done.

Ask: explain the main blocker and evidence.

Gate 4

Safe next request

Choose one agent request that moves the project without crossing authority boundaries.

Ask: propose the smallest safe next task.

Gate 5

Validation proof

Name the checks or reviews needed before claiming the work is complete.

Ask: prepare validation evidence.

Gate 6

Avoid list

Keep unsafe, premature, or out-of-scope work visible before delegation.

Ask: summarize what not to delegate.

Work Lanes

Where the office PM can point agents

Each lane turns project state into a safe, plain-language request.

Project intake

Idea capture, path choice, brief direction

The front-door concept is visible but still needs careful gate language.

Ask an agent: Review the intake docs and suggest the smallest next UI slice.

Avoid: Turning advisory screens into execution authority.

Brief quality

Strong Design Brief and AI-production planning

The quality bar is defined as artifact readiness, not approval to code.

Ask an agent: Check whether the current brief workflow exposes approval and revision moments clearly.

Avoid: Making every step feel like a hard gate.

Local dossier

Context packets, read models, decision history

Dossier concepts should stay display-safe until persistence is approved.

Ask an agent: Summarize which dossier fields are safe to show next.

Avoid: Adding storage, workers, or package handoff behavior without a separate decision.

Validation

Source checks, dashboard refresh, evidence

Validation should explain what changed without implying authority.

Ask an agent: Run safe validation checks and name stale or missing source docs.

Avoid: Treating generated HTML as the source of truth.

Automation

Manual refresh first, morning automation later

Manual dashboard refreshes should stay trustworthy before scheduling automation.

Ask an agent: List what must be proven before morning refresh automation.

Avoid: Automating before freshness signals are easy to trust.

Agent Context

Evidence belongs below the scan

Useful for agents and audits; secondary for the office PM.

What exists

Dispatch is a static Vite/React scaffold for a local-first product-shaping studio.
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.

What is not proven

Dispatch does not yet have live advisory agents, provider calls, persisted local projects, saved dossier state, or a real backend.
The generated docs-view still needs general clarity and scanability polish as the PM-cockpit layout settles, especially around how much proof appears in the agent-context section versus the fast scan above it.
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.