The full aBOS map: the front door, the factory, the six core agent classes, the safety rules and the patent-pending mechanisms. Part 2, the build log, is below. You can also download this map as HTML or as a PDF.
Imagine a toy factory that builds a little team of helper robots for each company. The robots do the busy work, a grown-up always says yes before anything important happens, and the company can take its robots home whenever it wants.
aBOS gives each company its own private AI team. One factory builds every team from the same tested design, so each new company is cheaper and safer to set up. The AI drafts and prepares. People decide. The company can leave with everything at any time.
aBOS is a governed, multi-tenant agent operating system. A Cell Factory compiles one versioned core plus a signed pack lock into an isolated per-tenant cell, with enforcement metadata bound at instantiation. Six mandatory agent classes run under permission envelopes, sensitivity-tiered memory and named-human gates; Finance inference is local-only.
Tap any box to learn what it does. Use the buttons at the top to hide or show parts of the picture.
Tap any part to see what it does, which patent-pending mechanism protects it and how it fits ExO 3.0. Use the layer buttons to show only what you are explaining.
Select a component for its contract, protecting filings, ExO 3.0 mapping and moat class. Layer toggles filter zones.
Step through the story in order. Each stop selects the part on the map above and explains it at your chosen reading level.
These are eight clever ideas we wrote down and sent to the patent office first, so they count as ours while the office looks at them.
Eight provisional patent applications are filed with the USPTO. Each protects a mechanism that runs inside aBOS. Tap "Show on map" to light up the parts it covers.
Eight US provisional applications under 35 USC 111(b), filed March to October 2026, each standalone (no benefit claims). Scope is described by subject matter, never by claim number.
ExO 3.0 is a recipe, written by Salim Ismail, for how a company should work when AI helpers do lots of the jobs. aBOS is the kitchen that actually cooks that recipe every day.
ExO 3.0 is Salim Ismail's framework for the AI-native company (The Organizational Singularity). It describes the destination. aBOS is running software that gets a company there: every ExO 3.0 component maps to real parts of the system. The framework is credited to its authors; the software that implements it, and its eight filed mechanisms, belong to AICSAI LLC.
ExO 3.0 = MTP-as-protocol (Constraint, Decision, Identity layers) + DRIVE (5) + SHAPE (5) over the Intelligence Stack (Four Pillars: trusted evals, searchable logs, granular rollback, human review queue; GOVERN/ASSURE). aBOS implements each element in its data plane. Select a letter to highlight its implementation on the map.
Select any letter on the left to see how aBOS implements it, then look at the map to see the parts light up.
We count every part of the picture and colour it by who made it. Most of the important parts are our own ideas.
Every part on the map is counted below by what protects it. The counts are computed from the map itself, so they change if the map changes. Parts that third parties make, like open-source models, are credited and not claimed.
Classification per component: covered by at least one filed mechanism (P1 to P8); otherwise trade secret / know-how; otherwise credited third-party or open source. Counts are live over the component dataset.
Eight provisional applications cover the cell model and local Finance (P1), safe learning, memory tiers and earned autonomy (P2), governance built in at creation (P3), workflow redesign (P4), multi-person discovery (P5), personas (P6, P7) and the AI meeting participant (P8).
The factory implementation, the single cell definition, golden test sets, attempted-violation test suites, release and recovery machinery, and the operating discipline that runs it.
The shared library of proven patterns grows with every cell (only patterns cross, never data). Each client's persona relationship is licensed, not exported. Intelligence density rises as override rates fall.
ExO 3.0 (Salim Ismail and contributors), open-source parts (local models, vector store, web framework, agent runtime, Postiz as a separate process) and cloud model vendors for non-Finance work.
A rule always beats a priority. These are enforced underneath the buttons, in the data plane, and each one has a test that tries to break it.
Build log entries start here soon. We will post short, dated notes on what changed in aBOS and why, and a timeline of how Alien Cortex got here.