Phoenix Collective

The more we automate, the more visible human intent must become.

Intelligence should increase sovereignty, not diminish it.

Phoenix Gate on GitHub

Local node extensions coming soon

Why this exists

Models and tools will act. Someone has to decide which actions may proceed, without stopping ordinary work.

This is model-agnostic fractal governance. Model-agnostic means the rules do not depend on which model or tool is doing the work. Fractal means the same pattern repeats, from one action to a whole organization. Phoenix Gate is the mechanism: it allows an action, denies it, or asks a person.

Models change. The governance holds.

Frontier models and tools keep changing. Treat them as workers. They are not the rules.

The governance is built to outlast any one model. It can adapt as the work changes, and it scales from a single task to many organizations.

For a custom use case, any model or tool can sit behind a purpose-built gate. The gate defines the allowed action. The worker does the work. Swap the worker and the gate stays.

Constitution with teeth

These are the rules the system is built to enforce.

  • Sovereignty over extraction

    Intelligence should increase sovereignty, not diminish it. Tools should make people more free, not more dependent.

  • People set intent. Workers execute.

    A model or tool does not, on its own, transfer ownership, expose core assets, or make a commitment that cannot be undone. A named lock is the rule that stops that action or asks a person. The person decides.

  • Doctrine is the stable focus

    Doctrine keeps the work efficient, purposeful, and aligned while models and tools change. Phoenix Gate applies that focus to a specific action.

  • Evidence over assumption

    If we cite a score, we cite the date and how many cases were in the set.

  • Every decision leaves a record

    A later reader should see why a decision was made, not only what happened.

  • No single person is the switchboard

    The system should not require one person to personally relay every step. Locks and records carry the continuity.

  • The paradox of automation

    The more we automate, the more visible human intent must become.

Trust here is restraint plus a record. An action that cannot be undone waits for a person, and the reason is kept.

How it works

Workers do not set the rules. They enter a gate that reads Governance, and allowed work lands with the business, organization, or individual the operator is supporting.

Businesses we serve
Businesses, organizations, or individuals. Collective members, or anyone a local AI operator supports.
Local AI operators
People and teams running agents under Phoenix Gate. An operator can also be a business we serve.

Workers

Agents and tools

Frontier models and tools are workers. They enter at Gate Kit. They can be replaced. They do not rewrite Governance.

Enter only through the gate

Permissionless surfaces

CLI · MCP · API · plugins

These are ways a worker can reach the gate. They do not set the rules.

  1. [0]

    Governance

    SIOS and Continuity

    SIOS (Sovereign Intelligence Operating System) holds the constitution and Continuity. Continuity is the record of locks and decisions, so the work continues when no single person is relaying every step. The gate reads these rules before a worker acts. Local work runs for a business, organization, or individual on this layer, which is how one pattern scales.

    The gate reads these rules

  2. [1]

    Gate Kit

    Allow, deny, or ask a person

    Gate Kit is model-agnostic fractal governance for one use case: the same rules at every scale, whichever model is the worker. Phoenix Gate allows the action, denies it, or asks a person. A named lock is the rule it checks — who may act, what state is allowed, and what the action is for — when that action would transfer ownership, expose core assets, or cannot be undone.

    Allowed work becomes a packet

  3. [2]

    Ops packets

    Intent, bounds, receipt

    A packet states the intent, the bounds, and whose approval was required. A receipt comes back with the decision. That receipt is the provenance.

    Allowed work lands with the business

  4. [3]

    Where the work lands

    The business the operator supports

    Allowed work lands with a business, organization, or individual — the people the operator is supporting. That can be a Collective member business, or any business an operator serves through open Phoenix Gate. SIG (Sovereign Intelligence Graph), the brand graph, stays with that business. Many businesses mean many graphs on the same governance. Operators and businesses can be the same person.

In the works

Roadmap

More operators, quieter links

In the works: more local operators supporting businesses on the ground, and quieter links between those operations. These are not finished products.

What a receipt records

  • The intent that was named.
  • The lock decision: allow, deny, or ask a person.
  • Who approved the bounds, and when.

Open templates

Phoenix Gate is the public home for templates you can copy. There is no checkout and no signup on this page.

The more we automate, the more visible human intent must become.