Project Board (Kanban)
Project Board turns goals into durable plans, task cards, source-backed evidence, and review loops.
Project Board
The Project Board gives long-running work durable cards, status, evidence, and review context.
When To Use Project Board
Use Project Board when a request is too large, ambiguous, or important to live only in chat. It is built for work that needs decomposition, source grounding, pause/resume, review, and proof.
A developer might start with: implement a feature across several files, investigate a regression, compare architecture options, validate release readiness, or turn a vague product request into ordered implementation cards.
End-To-End Flow
Capture the objective and sources
Ambient records the goal, relevant files or artifacts, known constraints, and open questions. This gives the planner a bounded context instead of a giant prompt dump.
Review Draft Inbox candidates
The Draft Inbox holds proposed cards and clarifications before they become committed work. Developers can accept, refine, defer, or reject proposed cards.
Execute cards on the board
Accepted cards carry status, dependencies, budgets, source references, artifacts, retries, and validation expectations. Work can pause and resume without losing the shape of the plan.
Inspect map and proof surfaces
The map view shows relationships between cards and artifacts. Proof surfaces attach commands, screenshots, source paths, and final notes to the work product.
Review the Git handoff
When code changes are involved, Git summary and review surfaces connect the board result to branch state, diffs, and acceptance criteria.
UI Anatomy
Draft Inbox
A staging area for candidate cards, implementation choices, and clarifying questions. It prevents the board from filling with unreviewed or low-confidence work.
Kanban Board
The main execution surface. Cards expose status, scope, source evidence, validation, owner/runtime context, and next actions.
Map View
A relationship view for dependencies, artifacts, cards, and decisions. It helps developers see whether work is converging or branching.
Proof And Review
A compact record of what changed, what was validated, what remains risky, and which evidence supports the final answer.
Card State And Evidence
Project Board is effective because cards are not just labels. They are durable units of work that preserve why the work exists, where evidence came from, what was attempted, which artifacts were produced, and how completion was judged.
- Source references identify the files, docs, screenshots, traces, or external facts that shaped the card.
- Status fields distinguish proposed, accepted, active, blocked, review, and complete work.
- Validation fields record the commands or product checks that should prove the card.
- Artifact links keep generated documents, screenshots, logs, and diffs attached to the plan.
- Review notes preserve PM judgment, proof quality, and follow-up risks.
Developer FAQ
When is Project Board better than normal chat?
Use chat for small single-step tasks. Use Project Board when the work has multiple dependent steps, needs user review before execution, or must preserve proof across pauses and restarts.
Can Ambient create cards automatically?
Yes. Ambient can propose cards from a goal and source context, but the Draft Inbox exists so developers can review and shape the plan before committing it.
How does this relate to durable goals?
Durable goals preserve the overall objective and continuation state. Project Board gives that goal a visible card structure with evidence and review surfaces.
Can I rely on Project Board today?
It is a Developer Preview surface with substantial implementation and release-gate coverage. The core workflow is usable, while some advanced states and live validation lanes are still being hardened.