Case study · Owner-only deployment with synthetic data · public product demo
An IT portfolio workbook rebuilt as a snapshot-based web application with role-checked editing.
The FY26 IT portfolio workbook combines funding status, monthly ranks, budgets and actuals across roles with different responsibilities. Rebuilding this workflow means preserving business rules, separating PMO figures from Finance's accounting feed, and making history and editing rights explicit. Control Center replaces the synthetic workbook with a database-backed application: monthly snapshots, capital and expense reporting, lifecycle decisions, reconciliation, resource planning and presentation mode. The fictional dataset demonstrates the workflow; it does not establish organizational adoption.
Dylan supplied the HTML prototype and selected direct, authorized resource-allocation edits with an audit trail instead of an approval queue. He is the production administrator. Other domain decisions are recorded without a named decider, so this case study describes their implementation without assigning unsupported personal authorship.
Claude Code assistants implemented the API, persistence, authorization, concurrency handling, import receipts and React application. Other assistants drafted helpers and reviewed finance and permissions; review corrections were applied before acceptance. The initial schema is documented as a Copilot draft. The delivery record includes a coordinating review role whose human-versus-agent identity is not specified.
Decision 1
The prototype decided above-the-line or below-the-line status by adding up ranked forecasts against the target. The recorded decision keeps that status manual, set by the business team. Rank and remaining target headroom are shown as information only. They never fund or admit a project. This keeps accountability where funding is actually decided. The cost is losing an automation the prototype made look easy.
Decision 2
Financial lines and ranks belong to a monthly snapshot. Only the open snapshot can be edited, and captured snapshots are read-only. Capturing a snapshot copies PMO figures and ranks forward in one transaction. Totals are computed views, never stored values. Review found that two simultaneous edits of the same version both succeeded. Mutations now serialize before checking the version. Descriptive project fields still show current values in historical views.
200 + 200 → 200 + 409
Live race reproduction against the review API, September 20, 2026. Before the fix, both writes succeeded and one silently overwrote the other. After it, the second write is rejected as stale.
13 of 13 routes
Authenticated production site at 1440 px and 390 px, September 21, 2026. A functional check, not an accessibility audit.