Arc Categories

Every system Arc builds is, beneath its interface and its business model, one of a small number of kinds. The Arc Categories name those kinds. They are a taxonomy of technical essence — what a system fundamentally does in the stack of artificial intelligence — and they are deliberately indifferent to how it is sold, hosted, or delivered.

That indifference is the point. SaaS, API, licence, hosted service — these are delivery; one category can ship as any of them. The category asks the deeper question.

A category is what a system is, not how it is sold.

It is also what separates a category from an Arc Role: a role asks what function a project serves inside Arc; the category asks what kind of thing it is in the world. A project may show traits of several forms — those are its characteristics; the category names its primary form, not its only one.

The depth axis — six technical forms

Six of the eight form a vertical structure, from the surface where a person meets a decision down to the primitive that makes everything above it possible. The execution layer holds two: an agent given a workspace, and an agent given your world.

1. Decision     Intelligence System          data + context → judgement
2. Execution    Agentic Platform             a workspace that equips an agent — you bring work to it
                Agentware                    an agent in your own environment — it operates your world
3. Trust        Local-first / Trust-bound    control, privacy, governance at the edge
4. Reuse        Substrate                    foundations many systems build upon
5. Primitive    Foundational / Enabling      the core mechanisms the rest depend on

Near the surface, value is legible to a user and the engineering is heaviest. Near the floor, value is leverage rather than revenue, and the work sits closest to Arc's technical sovereignty.

• Intelligence System turns data, context, and operations into decision intelligence — resolve, simulate, what-if, so-what. (Lancet.)
• Agentic Platform is a workspace that equips an agent with tools, retrieval, memory, skills, and data — you bring your work to the environment it provides.
• Agentware fuses an agent into installable software that operates your own environment — your device, files, apps, hardware. The agent comes to your world rather than providing one; you supervise what it drafts.
• Local-first / Trust-bound System holds control, privacy, IP, and execution authority at the edge, where a system cannot simply be handed to the cloud. (Cawsal.)
• Substrate is a reusable technical foundation many systems build upon — judged by reuse and leverage, not sales. (Hunter-RAG; see Arc Substrate.)
• Foundational / Enabling Technology is the core mechanism, method, or standard that makes the substrates and systems above it possible. (HMI / StructPose.)

The two network forms

Two more forms are not points on the depth axis at all. Their essence is coordination among many parties rather than a layer of the stack:

• Marketplace / Exchange coordinates supply and demand — tasks, judgement, content, expertise — through matching, quality control, reputation, and settlement.
• Social Connect enhances connection between people, places, and activities — discovery, coordination, participation.

The line between them is exact: a marketplace organises an exchange of value; Social Connect organises a connection of people. Intelligence may sharpen either, but neither has AI reasoning as its essence — which is why they sit beside the technical forms rather than inside them.

What is not a category

The discipline is in what the taxonomy refuses. A category names a distinct technical essence, so the things that merely look like categories are kept out:

• Delivery is not a category. SaaS, API, hosted infrastructure — these are how a form reaches the world, not what it is. A Substrate exposed as an API is still a Substrate.
• A bolted-on console is not a category. A studio or operator console attached to another system — Cawsal's, Lancet's — is a feature of that system, a layer of interface. (A workspace that is the agent's primary environment is a different thing — that is an Agentic Platform.)
• Some apparent forms dissolve into others. A protocol or standard is Foundational / Enabling Technology; a control plane is an Agentic Platform or a Trust-bound System, depending on whether it equips agents or governs them. Each was considered and folded in, because a category must be an essence, not a sub-type or a wrapper.

Eight is not a target; it is what remains once delivery modes, interface layers, and sub-types are taken out — and it became eight only when a form arrived that the others genuinely could not hold.

How Arc reads its universe

The categories are not a filing scheme applied after the fact. They are how Arc reads its own work — and the structure a visitor meets first: they render as a live console on the home page and filter the portfolio. Where other lenses ask how mature a project is or what function it serves, the category asks what kind of thing it is — so each names a different position taken at the frontier, a different shape of deep technical option. Read together, the eight turn a list of projects into a universe with a structure.