Skip to content

2026-09-02 Factory campaign dashboard review

Adversarial review found bounded-dispatch and stale snapshot-contract mismatches in the Factory dashboard.

Work Done

Reviewed the staged Factory campaign-controller prototype in virdx/mono without editing it. Compared the restructured controller, contracts, worker packaging, Argo submission, and dashboard integration with the previous histo and viseg implementation. Found that the dashboard reports all selected or open cases as submitted even though the controller admits only one bounded worker batch, and that the page still describes a removed one-hour server snapshot contract. Verified controller locks, tests, lint, typecheck, builds, worker lock consistency, dashboard typecheck, and dashboard tests.

Lessons Learned: Pitfalls

The product workstream has no SOP index. Current Factory knowledge is split across several same-day infrastructure and histo inbox entries, so a fresh review must reconstruct the controller-to-dashboard contract from code. Multiple linked worktree agents can stage fixes during review, so findings must be checked against the index again before reporting.

Lessons Learned: Improvements

Document the campaign dispatch contract in one durable Factory page. State that a dispatch request admits only the cases that fit currently free worker slots, and require API responses or dashboard copy to identify the admitted cases. Document whether campaign status reads are fresh, cached, or batched so the dashboard does not preserve stale snapshot language after backend changes.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close