Noether Capital - Build Activity

⚠ PAGE STATUS: BUILD SPECIFICATION

This page contains the build specification for the Build Activity dashboard. The specification below defines exactly what must be implemented. To build this dashboard, give Claude Code the instruction: “Read the build specification on factory-build-activity.html and implement it.”

Build Specification: Build Activity Dashboard

Specification Source: Hilbert Factory Sections 14 (Builder Agent), 15 (Verifier Agent), 18 (Build Orchestrator) + Dashboard Spec View 2

Panel 2.1 — Agent Pool Status

Chart Type: Status Grid (Custom HTML/CSS)

Data Source: GET /api/orchestrator/agents — returns all agent instances with status

Refresh Rate: REALTIME (every 5 seconds)

Display: Grid of agent cards. Each: agent_id, type (Builder/Verifier/Chief Engineer), status (IDLE=green, BUSY=blue, UNRESPONSIVE=red), current packet if busy, elapsed time, last heartbeat.

Interaction: Click UNRESPONSIVE agent → show last known state + trigger health check

Panel 2.2 — Live Packet Tracker

Chart Type: Data Table (React Table with sorting/filtering)

Data Source: GET /api/orchestrator/queue?status=active — returns all non-terminal packets

Refresh Rate: FREQUENT (every 30 seconds)

Columns: packet_id, capability_block name, phase, status (colour-coded), assigned agent, elapsed time, retry count, last activity timestamp

Default Sort: By status (EXECUTING first, then VERIFYING, ASSIGNED, QUEUED)

Row Colours: EXECUTING=blue, VERIFYING=purple, FAILED=red, REPAIRING=orange, QUEUED=grey

Interaction: Click any row → full execution history: every state transition, every API call, every error

Panel 2.3 — Execution Timeline

Chart Type: Gantt Timeline (D3.js)

Data Source: GET /api/orchestrator/timeline?hours=24 — returns state transitions for all packets over 24 hours

Refresh Rate: PERIODIC (every 5 minutes)

Display: Horizontal bars per packet. Colour segments show time in each status. Red diamonds mark failure events.

Interaction: Hover → tooltip with packet details. Click → drill-down to packet history.

Performance: Canvas rendering for > 50 concurrent packets. Paginate by phase if > 100 packets.

Panel 2.4 — Queue Analytics

Chart Type: Metric Cards + Line Chart (Recharts)

Data Source: GET /api/orchestrator/queue/analytics — returns queue depth, wait times, throughput

Refresh Rate: FREQUENT (every 60 seconds)

Display: Current queue depth (number), average wait time (number), longest-waiting packet (with alert if > 60 min). Line chart: queue depth over past 24 hours.