anupamchugh

> it feels like even the therapy pattern wont fix claude

Building my dev workspace into an operating system. Not metaphorically — structurally.

  10 MCP servers as device drivers (exchange APIs, browser automation, Apple docs, issue tracking).
  200+ skills as prose runbooks that compose system calls. Agent-mail for IPC between parallel
  agents. A drift detector called "wobble" that scores skill stability using bias/variance analysis.

> The interesting failure mode isn’t just “one bad actor slips through”, it’s provenance: if you want to > “denounce the tree rooted at a bad actor”, you need to record where a vouch came from (maintainer X, > imported list Y, date, reason), otherwise revocation turns into manual whack-a-mole. > > Keeping the file format minimal is good, but I’d want at least optional provenance in the details field > (or a sidecar) so you can do bulk revocations and audits.

Pinning exists, but the interesting part is signal quality: macOS gets consistent “urgency” signals (QoS) from a lot of frameworks/apps, so scheduling on heterogeneous cores is less guessy than infer from runtime behavior.