Sample data, read only
Sample: a two-service monorepo and its brain
A sample brain for a two-service monorepo (TypeScript API and React web). This static page shows a few of its decisions. Synthetic data, not a customer record.
Sample decisions
2026-04-12
Single shared design-tokens package
The web app and the marketing site both render hero metrics. Without a single source the colours drifted (#5B7CFF vs #5C7DFF on three pages). The shared package costs one CI build step + saves a quarterly drift audit.
2026-04-30
Stripe Customer Portal over a custom dashboard
We could build a custom subscription manager but Stripe Portal handles invoice download, card update, plan change, and tax-id capture for free. The 30 hours that would've gone into a custom UI ship feature work instead.
2026-05-22
Switch from polling to SSE for the budget alert stream
Polling at 30s cost 5x the Vercel function invocations vs an open SSE connection. The alert is event-driven (Stripe webhook → push) - pulling state was the wrong shape.
What happened in this change?
This page is a static sample. The sample case follows one synthetic investigation from the instruction to the verified fix. Install RepoOps to open a case from your own repository.
Curated sample.