CogniScaleFormula AI Control Centre · architecture

How the Formula AI Control Centre works

Four pictures, top to bottom: what an organisation contains, where everything is stored, what happens when a co-CEO opens, and how a Connected Colleague is made. Then the words we use.

1 One organisation, by level

One organisation one row in the register; everything below belongs to exactly one People members and administrators rows in the register (Supabase) Skills shelf reusable how-to for the organisation a skills folder in the library (GitHub) Connected Colleagues specialist co-CEOs, one job each a sealed package each, in the library belong to the organisation, not to a library Workspace Brains · the libraries one private GitHub repository per brain Owner floor the founder Leadership floor the few Team floor everyone in the organisation rooms for clients and projects
An organisation is a building. Its people, its skills shelf and its Connected Colleagues belong to the building. Its libraries are the Workspace Brains; a person reads a floor only with that floor's card.

2 Three places hold everything; one front desk connects them

The front desk · Control Centre every read and write passes here app.cogniscale.com and its server functions (Netlify) checks who may see what hands over a signed bundle reads documents for you The register who exists, who belongs where, which colleagues are approved Supabase · row-level security Each person's Mac the helper checks the signature, then launches the co-CEO the CogniScale helper The library documents, skills and colleague packages GitHub · private repositories Nothing is stored twice. The front desk checks the register before anything leaves the library.
The register knows who and what exists. The library holds the documents. Each Mac fetches only what its person may see. The front desk is the only way in or out.

3 What happens when a co-CEO opens

1 · Open the helper on your Mac asks the front desk 2 · Check the register says which brains you hold a card for 3 · Bundle a signed bundle of those brains, checked on your Mac 4 · Work your co-CEO opens with Gmail, Drive and Calendar The co-CEO runs on Claude. Google connections are the person's own, granted once, with permission. A bundle that does not match the approved version is refused on the Mac.
The person's own connections stay theirs. The bundle is signed by the platform and checked on the Mac before anything runs.

4 Making a Connected Colleague

1 · Ask tell your co-CEO the job 2 · Interview four short questions 3 · Approve registers it with its skills 4 · Launch it opens like your co-CEO Behind step 3 the platform writes the colleague's sealed package into the organisation's private repository. Nobody edits files by hand. Private by default; shared with named people when you choose.
A colleague is a specialist co-CEO with one job, defined by a small package the platform writes for you.

5 The words

Organisation — the building; everything belongs to exactly one.
Workspace Brain — a library; floors for Owner, Leadership and Team, with rooms inside.
Room — a section of a floor, for a client or a project.
Skills shelf — reusable how-to; one shelf per organisation.
Connected Colleague — a specialist co-CEO with one job and its own sealed package.
The register — the card index: who exists, who holds which card, what is approved. Supabase.
The library — where documents, skills and packages live. Private GitHub repositories.
The front desk — the Control Centre and its server functions; every read passes it. Netlify.
The helper — the small program on each Mac that checks signatures and launches the co-CEO.
Personal brain — a person's own notes, on their own Mac, read by nobody else.