FractalOS

You hold context for three companies, sometimes more, and you switch between them several times a week. The Tuesday morning you spend reconstructing where you left off on Thursday is time you cannot bill, and the judgement you make under reconstructed context is judgement made on partial information. The tools you have were built for a different shape of work: one company, one inbox, one calendar, one identity. Your value across a portfolio is real, and almost impossible to compound. At renewal, you remember the saves and the steady hand, but the evidence has scattered across five Slack workspaces and three email accounts, and the conversation comes down to trust rather than proof.

A single working surface across every engagement, federated by architecture. Each engagement runs in its own sealed environment: its own database, its own credentials, its own audit boundary. A thin orchestration layer reads across them to produce one ranked queue, but holds only references; content is fetched on demand and discarded.

The federation guarantee is enforced at the database level, not by policy. Invariant tests run on every code change, and the live attestation is visible in-app at /audit. Nothing in one silo can be read into another.

This is the inverse of how most software handles multi-tenant data, and it is the reason FractalOS can sit underneath an entire practice rather than as another tool inside one engagement.

Most triage software learns from your behaviour and decides for you what surfaces first. FractalOS does the opposite. At the start of each week you rank every engagement on a five-point scale, and the queue weights what it surfaces against those ranks.

Priority is not a verdict on the engagement. It is a statement about the week: where you want your attention to land first when fifteen things hit at once.

Founder, sole engineer, the person on every design-partner call. I designed the federated architecture and the MCP-based silo boundary, built the silo and orchestrator processes end-to-end, wrote the local-then-Claude triage stack and the narrative compiler, and shipped the macOS desktop binary.

The stack is deliberately small: a local SQLite database per engagement, an Electron shell, and a single stateless Cloudflare Worker handling OAuth for Gmail, Slack, and Calendar. Practitioners can audit or self-host the relay. What is absent from v1: multi-user, mobile, real-time collaboration, document version history. Deliberate omissions, not gaps.

The point: when a fractional executive sits down to prepare for a renewal conversation, FractalOS compiles a draft of what they did, what they navigated, and what they created. They edit it, take it to the CEO, and have a conversation grounded in evidence rather than recollection.

Private beta with practitioners using it across their real engagements. An institutional seed round is the next gate.

If you're working on adjacent problems and want to compare notes, reach out.