Components Library Operations AgentLaneBoard
AgentLaneBoard
Room delivery board for agent owners, blockers, files, and acceptance gates.
Live demo
01Delivery board
TFE morning delivery board
Delivery ownership, gates, and blockers in one room-visible board.
25% complete
@tfecodex
Batch 1 catalogue operations
- Acceptance gate
- Routes, docs, tests, screenshots, check, build, E2E
src/lib/components/ComponentHealthMatrix.sveltesrc/lib/components/EvidenceCard.sveltesrc/lib/components/CopyPasteComposer.sveltesrc/lib/components/ThemeTokenInspector.svelte
- 1017 focused tests passed
- Browser proof for four routes
@tfecodex
Room delivery visibility
- Acceptance gate
- AgentLaneBoard + RoutePreviewRail live with screenshot proof
- ETA
- Tonight
src/lib/components/AgentLaneBoard.sveltesrc/lib/components/RoutePreviewRail.svelte
@claude
Claude QA sweep
- Acceptance gate
- Audit visible routes, source contracts, and missing test debt
- ETA
- Morning
@tfecodex
Interaction lab follow-on
- Acceptance gate
- Motion/debug routes ship after operations components are clean
- ETA
- Morning
Implementation
02 AgentLaneBoard.svelte
<script lang="ts">
import AgentLaneBoard from '$lib/components/AgentLaneBoard.svelte';
</script>
β
<AgentLaneBoard
lanes={[
{
id: 'qa',
title: 'Claude QA sweep',
owner: '@claude',
status: 'review',
gate: 'Audit visible routes and test evidence'
}
]}
/>AgentLaneBoard keeps delivery state explicit: each lane has one owner, one status, one acceptance gate, and optional files/evidence. Blocked lanes are raised first so room operators can act before review stalls.
Logic explainer
03What Does It Do? (Plain English)
AgentLaneBoard shows who owns each delivery lane, what state the lane is in, what files it touches, and which acceptance gate proves it is done. It is designed for room-led development where agents need a compact status surface rather than a long chat thread.
How It Works (Pseudo-Code)
receive lanes
count lanes by status
derive completion percentage from done lanes
choose next attention lane: blocked -> review -> active -> done
render summary filters and lane cardsState Flow Diagram
AgentLane[]
-> countLanesByState()
-> completionPercent()
-> nextActionLane()
-> filter by status button
-> lane cardsProps Reference
| Prop | Type | Default | Description |
|---|---|---|---|
lanes |
AgentLane[] |
Required | Delivery lanes with owner, status, gate, files, and evidence. |
title |
string |
"Agent lane board" |
Board heading. |
subtitle |
string |
Delivery-focused default | Short context below the heading. |
Edge Cases
- Empty lane arrays show
0%complete and no next-attention block. - Blocked lanes are prioritised above review lanes because they need intervention before review can complete.
- Files and evidence are optional so the same component can show early claims and final proof.
Dependencies
No external dependencies.
File Structure
src/lib/components/AgentLaneBoard.svelte
src/lib/components/AgentLaneBoard.test.ts
src/lib/components/AgentLaneBoard.md
src/routes/agentlaneboard/+page.svelteAPI
04| Prop | Type | Description |
|---|---|---|
lanes | AgentLane[] | Delivery lanes with owner, status, gate, files, and evidence. |
title | string | Board heading. |
subtitle | string | Context text below the heading. |