Eleven days, thirty-one sessions, eight subsystems

2026-04-14

Over 11 calendar days, the sprint that built Composure's core infrastructure logged 31 sessions: 3,151 active minutes (52.5 hours), 9,577 tool calls, 1,797 file touches, 380 tasks created.

What shipped in that window: authenticated content delivery with PKCE OAuth; a TypeScript rules engine with CLI and MCP transports; the Cortex memory server with 9 database migrations and four transport paths — built and verified end-to-end in a single 191-minute session; a 244-file ecosystem standardization campaign executed in four pre-scoped stages; plus the debugging passes that kept it all honest.

Every number above comes from the session records the system writes about itself — the same telemetry the product ships.

Aggregated from 31 session records in the Composure plugin repo, April 3–14.

You can stop reading and start checking.

This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.

Install it Next: I didn't have to guess what the room knew.