Pax Equitas
Skip the opening
  1. 01 · FragmentsEvidence, documents, communications, claims, approvals — arriving out of order, from everywhere.
  2. 02 · SignalEach fragment is read, typed, and scoped to the organization it belongs to — nothing ambient.
  3. 03 · StructureStructured and connected under one identity, one permission set, one organization boundary.
  4. 04 · DecisionAn AI role drafts. Nothing proceeds on its own.
  5. 05 · Human controlA person approves. The action is written to an append-only audit — actor, organization, target, timestamp.

Pax Equitas

The Control Plane for AI-Operated Organizations

Pax Equitas does not compete with frontier AI. It makes frontier AI governable inside a real organization — with the authority, boundaries, institutional context, verification, and accountability it takes to entrust it with real work.

Proven in production, October 2026: an AI agent's bounded change reached production under company-owned authorization, an external system enforced it, and a separate identity verified it.

Where the lines are

Five parts. Hard lines between them.

Intelligence, authority, execution, and verification are different things, held by different parties. Pax Equitas supplies none of the intelligence and all of the organizational layer around it.

  1. 01

    Frontier AI

    Intelligence

    Reasoning, generation, and the capability to execute. It improves on the vendors' schedule, not ours. Pax Equitas builds none of it and competes with none of it.

    Supplied by the model vendors

  2. 02

    Pax Equitas

    The control plane

    Identity and authority, bounded authorization, policy and operational boundaries, institutional memory, execution evidence, and the durable record of the company — the organizational layer a model does not carry with it.

    Owned and operated by Pax Equitas

  3. 03

    Peterson

    Governance and institutional memory

    The layer that knows the organization: its missions, its decisions, who is authorized to do what, what was executed, and what was verified. Peterson runs no model. It governs how a model's work enters the company.

    Owned and operated by Pax Equitas

  4. 04

    Agents

    Bounded execution

    AI executors with a registered identity, acting under an authorization scoped to one mission, one action, one exact target, and one expiry. An agent can ask for authority. It cannot grant it, and it cannot mark its own work verified.

    Vendor runtimes, under identities registered with Pax Equitas

  5. 05

    Verifiers

    Independent confirmation

    A different identity checks the outcome against evidence from the systems where the work landed — never against the agent's own report — and records every check, pass or fail. An agent can never mark its own work verified; only a verifier or an authorized person can.

    Operated by Pax Equitas, separate from every agent

Use the most capable AI models in the world. Pax Equitas gives them the authority, boundaries, institutional context, verification, and accountability required to operate inside a real organization.

How Peterson governs work

Ask. Authorize. Execute. Verify. Record.

Work that Peterson governs moves through the same five steps. One of them can only be taken by a person, and every one of them leaves a record.

  1. 01 · Ask

    Work enters as a mission.

    A person or an agent proposes a mission with an objective. An agent can propose and report under its own signed identity. It cannot approve anything, including itself.

    Mission ledger · registered agent identities

  2. 02 · Authorize · Human

    A person grants one bounded authorization.

    The decision — yes, no, or discuss — is recorded with what was asked and why. A yes authorizes one registered agent to take one action, for one mission, on one exact target, until one expiry. It can be revoked.

    Founder decision record · action authorization · revocation

  3. 03 · Execute

    The external system refuses what is not authorized.

    When a change is proposed or updated, the system where it will land asks Peterson whether this agent holds a live authorization for exactly this version. Wrong mission, wrong agent, wrong version, revoked, expired: refused. A merge that slips past a later revocation is caught by the verifier, not prevented.

    Required merge check (GitHub today) · gate decision ledger

  4. 04 · Verify

    A separate identity confirms the outcome.

    The verifier gathers evidence from the systems where the work landed — what merged, what deployed, what the live system reports — and checks it against the authorization. Pass or fail, every check is written down.

    Independent verifier identity · verification records

  5. 05 · Record

    The company keeps the record.

    Every step above was written as it happened: decisions, grants, gate answers, attestations, verifications. The governance ledgers refuse updates, deletes, and truncation at the database, so the history is append-only.

    Append-only ledgers, enforced by database trigger

Peterson is the organizational intelligence and governance layer within Pax Equitas. It holds the company's missions, decisions, authorizations, and evidence; governs what AI agents are authorized to do; records what was executed; and verifies the outcome. It runs no model of its own.

How Peterson works →Trust & governance →

Proof Mission #1

Proven on our own production system.

In October 2026 the loop ran end to end on the Pax Equitas platform itself. An AI agent made one bounded change to production under a company-owned authorization, an external system enforced that authorization, and an independent verifier recorded the result.

Read what was proven, and what was not →

  • No authorizationREFUSED
  • Wrong missionREFUSED
  • Wrong agentREFUSED
  • Wrong version of the changeREFUSED
  • Revoked authorizationREFUSED
  • Authorized agent, exact authorized versionACCEPTED

The system

One system, in one view.

Every governed role, the engine it runs on, and the platform that permissions, audits, caps, and can stop it — drawn from the registry, not from a slide.

Engines · 00 public products

    The decision path

    How a decision moves through it.

    Inside a product, the path one AI-drafted decision takes — and the gate where the draft waits for a person.

    1. 01

      Fragments arrive

      Photos, policies, estimates, agreements, inquiries — from public intake, signed agreements, storm and roof feeds, and field staff, in no particular order.

      Public intake · agreement execution · storm and roof intelligence

    2. 02

      Read and typed

      Each fragment is scoped to your organization before anything reads it. Access is default-deny, checked server-side on every request.

      Organizations & Teams — row-level tenancy, server-side checks

    3. 03

      One boundary

      Evidence, documents, and inquiries sit inside one organization's boundary — one identity, one permission set — before any role can touch them.

      One directory · one data boundary

    4. 04

      An AI role drafts

      A recovery position, a scope audit, a qualified intake — drafted, never final on its own. The recovery report cites its sources.

      AI Claims Assistant · AI Intake — scoped capabilities only

    5. 05 · Human gate

      A person approves

      The draft waits at the gate. Regulated determinations are made by licensed professionals, and an unreviewed analysis cannot reach a customer.

      Review gate on the report · approval step before any deployment

    6. 06

      Written to the audit

      Actor, organization, target, timestamp — appended, never edited. Any role can be paused or revoked in one action.

      Governance & Compliance — append-only audit, kill switches

    AI Workforce roles are software — permissioned, audited, and stoppable systems, not employees, contractors, or legal persons.

    Platform governance →Trust & governance →

    The roles

    Roles a frontier model can hold here.

    Each role is a job description, a permission set, and a manager: you. The intelligence comes from the model. The authority, the boundaries, and the record come from Pax Equitas — inside your systems, under your brand if you want, and never beyond the authority you grant.

    Hire it. Audit it. Cap it. Fire it.

    Enterprises don’t fail with AI because models are weak — they fail because nobody can answer “what did it do, on whose authority, and how do we stop it?” Pax Equitas answers all three, in code.

    Permissioned like an employee.

    Default-deny, role-based access; an AI employee can only use capabilities you granted, scoped to your organization.

    Audited like a transaction.

    Every action writes an append-only audit record — who, what, when, and through which channel.

    Capped like a budget.

    Spend limits and daily caps are governed and displayed; automation ships default-off and fails closed.

    Stoppable like a machine.

    Kill switches and approval gates are first-class platform objects, not support tickets.

    Nothing on this platform becomes purchasable, deployable, or reachable by payment alone. Licensing is gated by verified product maturity, and approvals re-check preconditions at decision time.

    Peter Guzzi — Founder, Pax Equitas

    Founder, Pax Equitas

    Leadership

    Meet the founder.

    Peter Guzzi is a serial entrepreneur, business strategist, and sales executive whose career spans more than four decades of building, scaling, and leading organizations in insurance, financial services, education, franchising, and technology. He rose to national recognition at NASE and UICI, founded Educate America and USDigital, and today serves as the driving force behind Pax Equitas.

    Peter Guzzi · Founder, Pax Equitas

    Built where the work is hardest.

    The AI Workforce was forged in insurance claims — one of the most regulated, adversarial, deadline-driven industries there is — and it carries that discipline everywhere else.

    The engines are already running.

    The roles aren't demos over an empty backend. They're powered by a product family that runs live operations today.

    Put your brand on the workforce.

    Agencies, resellers, and operating companies license the platform and offer AI employees under their own name — their domain, their logo, their client relationships. Pax Equitas stays in the engine room.

    Private-label ready today

    A platform you can build on.

    Documented APIs, signed webhooks, versioned SDK surface, and sandbox tenants. The same APIs power our own consoles — there is no private fast lane.

    Pax Search Intelligence lets the AI clients you authorize read your organization's Google Search Console data, read-only. It is in early access: you can create an account and try it.

    Someday you'll walk the office your AI employees work in.

    We're building toward a spatial workspace — a command center you step into, where your workforce, portfolio, and operations surround you. Same platform, same permissions, same audit trail. It ships when it's real, not before.

    Read about the spatial roadmap →

    Put the best AI to work — on your authority.

    Start with one governed role, or bring the whole control plane into your organization.

    Request a Demo