Best next agent request
Plan the next controlled orchestration slice.
Use the read-only Deck project-export collector result as T5b evidence, including the current blocked state when no approved safe aggregate source exists.
30-second project scan
Dashboard exists. Orchestration still gated.
The active packet names current project work. The useful PM view is: Coordinate local AI-assisted project work without losing human control. Main blocker: Authority boundaries and source freshness.
- Project stage
- Controlled orchestration planning
- Main blocker
- Authority boundaries and source freshness
- Business goal
- Coordinate local AI-assisted project work without losing human control
- Docs health
- 7 docs need review
Do not delegate yet
Worker-like authority or runtime writes.
Do not start workers, create packages, import data, commit, push, deploy, or mutate runtime state from a display surface.
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.
Mission control
Project context, status, and next actions
The dashboard can orient work, but source data freshness still matters.
Ask an agent: Identify which project status surfaces need review before new control features.
Avoid: Letting stale source data drive decisions.
Manual orchestration
Gatekeeper planning and visible handoffs
The next phase is controlled coordination, not autonomous execution.
Ask an agent: Summarize the gatekeeper plan and the next safe manual orchestration step.
Avoid: Starting worker-like behavior before controller gates are explicit.
Runtime data
JSON bridge, local sources, NAS status
Runtime data can inform the dashboard when ownership is clear.
Ask an agent: Check which runtime data sources are current and which are advisory only.
Avoid: Treating bridge output as permission to mutate files or repos.
Authority boundaries
Controller scripts, workers, packages
Boundaries are central to whether Deck stays trustworthy.
Ask an agent: Review the authority docs and list the non-negotiable no-action zones.
Avoid: Importing, committing, pushing, or deploying from a display surface.
Validation
Builds, docs checks, output proof
Validation should stay explicit and repeatable.
Ask an agent: Run safe checks and report what is proven versus merely displayed.
Avoid: Collapsing validation evidence into approval.
Agent Context
Evidence belongs below the scan
Useful for agents and audits; secondary for the office PM.
What exists
- No validation guidance found in the active docs.
What is not proven
- No validation guidance found in the active docs.
Source packet
- Generated 2026-07-10 from the active Markdown packet.
- Markdown remains the source of truth; this dashboard adds no execution authority.
Source Health
Files behind this dashboard
- Missing active docs
- 0
- Needs review
- 7
- Old but quiet
- 0
Freshness check
- Needs review: docs/current-state.md (2026-06-05)
- Needs review: docs/next-steps.md (2026-06-05)
- Needs review: docs/product-plan.md (2026-06-05)
- Needs review: docs/design-direction.md (2026-05-22)
- Needs review: docs/architecture.md (no review date)
- Needs review: docs/validation.md (2026-06-04)
- Needs review: docs/session-brief.md (2026-06-05)
Repo overview, commands, and documentation entry point.
FoundWhat exists now, what works, what is incomplete, and stale signals.
Needs review - reviewed 2026-06-05Recently completed work, recommended next moves, and work to avoid.
Needs review - reviewed 2026-06-05Product north star, current product shape, and roadmap posture.
Needs review - reviewed 2026-06-05Experience principles, visual direction, and interface guardrails.
Needs review - reviewed 2026-05-22Stack, app structure, data model, boundaries, and technical assumptions.
Needs review - no review dateValidation commands, QA expectations, and evidence requirements.
Needs review - reviewed 2026-06-04Compact restart context, immediate next move, caveats, and reminders.
Needs review - reviewed 2026-06-05