Deploy Axiom

Nothing in your business waits on you to remember it.

P. K. Stewart, founder · Baton Rouge

Built for independent insurance agencies and sales professionals: regulated work where every text has to clear consent, opt-out and quiet-hour rules before it goes.

We build and run the AI agents that do the remembering, on your own computer and accounts, and anything that commits the business waits for you.

Book a 15-minute callWrite a short brief
Read the insurance field report

One job, start to finish

How one follow-up moves through an Axiom agent. The agent does the work up to the point where it would commit the business, then it stops and waits for you.

replayan example, not a client record
  1. 09:02readA client asks to move Thursday’s appointment.
  2. 09:02sortScheduling change for an existing client. In this agent’s lane.
  3. 09:03draftReply written and the new time pencilled in on the calendar.
  4. 09:03checkThe new time is open. Nothing double-booked. Tone matches past replies.
  5. 09:03held (caution)It sends a message and moves a booking, so it waits for your yes.
  6. 09:41yes (go)You approve it from your phone.
  7. 09:41doneReply sent, booking moved, and the job written to the record.

# a simulated example of the pattern. Real jobs keep client names private.

Nothing sends, spends, or spins without the one who holds the gate.

the rule every Axiom agent works under, and the axiom behind Axiōma

One front door. A visible chain.

Orders go down. Evidence comes up. Choose a node or a gate to see where the work goes, and where it has to stop.

the Axiom systema map, not a live activity feed

OWNER → OPERATOR → WORKERS: orders down, evidence up. axioma and gatekeeper sit before WORLD; standing checks returning evidence. tripwire records a refused action in REFUSAL LOG. handydandy prepares the handoff to NEXT SESSION.

Follow the chain.

The owner sets the limits. The operator routes work to specialists, and evidence returns along the same chain.

Hover, tap or use the keyboard. Escape clears the selection.

Owner / the authority

The owner sets the limits and decides what may commit the business. A draft is never that approval.

Operator / one front door

The operator routes work to specialist workers and brings their evidence back to the owner.

Workers / bounded work

Specialists do the assigned work and return evidence up the chain. Saying “done” is not a check.

Next session / continuity

A written handoff carries the work forward so the next session can pick up where this one stopped.

World / outside the session

A message to another person leaves the session. The outbound edge is where the advisory card and send checks sit.

Refusal log / a visible stop

A refused action leaves a record instead of disappearing. Tripwire watches tool refusals, not just outbound sends.

axioma / a second look

Before a consequential call, Axiōma presents an advisory card. It advises; it never blocks or grants permission.

The spec is CC0 and the code is MIT.

gatekeeper / before a send

Checks supported terminal sends for consent, suppression, quiet hours and repeat messages. A failed check blocks that send.

standing / check the evidence

A worker must run a passing proof check before marking its task done. Standing checks the file, page or allowed command, not the claim.

tripwire / record a refusal

Logs a refused tool action and alerts the owner. It records the stop; it does not grant an exception.

handydandy / leave a handoff

Notices when a session runs long and prompts a written handoff for the next session.

The chain and its limits: hermes-axiom-agent, public source. The plugins act at different points; an advisory card is not an approval.

Where an agent stops and asks

Around 520 BC, Hipparchus of Athens set stone herms along the roads and carved short maxims into them, so anyone walking past could read the law on the messenger's stone. Walk with just intent. Do not deceive a friend.

We run our own company on the same idea. About a dozen (second look) specialist AI agents work behind one front door, and a written permission gate decides what each one may do alone. Money, new prices and first contact with strangers wait for a person.

An agent can build a payment link and check that the page opens. It never presses pay: completing a live payment (STOP) is reserved to the owner, so the agent stops there and reports exactly what is ready.

Every message is reserved before it sends, because a worker that crashes and retries could text the same person twice (CAUTION). We would rather miss one message and see it in the log than send it twice. The loop that answers when an agent gets stuck is public code, with 9 passing tests (GO).

Those colors are Axiōma, the signal our agents use when they write to a person. Red is stop, yellow is caution, green is a check that really passed, and pale gold is a whisper. The signal advises. The gate stays with you. Axiōma is given away: the spec is CC0 and the code is MIT.

# each marked phrase carries its Axiōma signal color and a second cue besides color:

  • red, bold, solid line: stop. Do not proceed until it is fixed.
  • yellow, wavy line: caution. It works, but it starts something that cuts against your interest.
  • green, dashed line: go. A real check passed.
  • pale gold, dotted line: whisper. A second look; it stops nothing.

What our own records show

ledgerour own operation, since September 2026 · as of Nov 9, 2026
286outcomes on record
187verified against recorded evidence
106with a failure caught and recovered, not hidden

# counts from our own company's records, not client data. See the work

Work

What we have built and run. Public code is linked. Clients are described rather than named until they agree to be.

  1. escalation-desk/

    When an agent gets stuck, a loop answers: one holding line, one ticket, every action checked against a gate that fails closed, and one reply telling the owner what to do.

    evidence: public code, 9 passing tests

    See the public code

  2. insurance-client-care/

    Texts and email at set points after a sale, with quiet hours, opt-outs and no repeats. Anything risky waits for the owner's yes.

    evidence: the full sequence ran on a test phone before any client got a message

    Read the field report

  3. hermes-tripwire/

    An open-source plugin that logs every action an agent was refused and alerts the owner.

    evidence: public, with tests

    See the public code

  4. handydandy/

    When a session runs long, the agent finishes the job and writes a handoff, so the next session picks up clean.

    evidence: merged into the Hermes plugin catalog

In the Hermes Agent plugin catalog

These are the plugins we run on our own agents, reviewed and accepted into the Hermes Agent plugin catalog. Each has a different job and limit.

How the system works for a founder: The operator layer.

plugins6 accepted, Oct 29 to Nov 9, 2026

  1. tripwire 0.1.3

    merged · updated

    Writes down every action an agent was refused, so the owner gets one short alert instead of finding out later.

    install hermes plugins install tripwire

    tripwire codePR #145692PR #151041

  2. handydandy 0.4.1

    merged · updated

    Tells you when a session has run long and can have the agent write a handoff, so the next session starts clean.

    install hermes plugins install handydandy

    handydandy codePR #146647PR #148914

  3. hermes-axioma 0.3.1

    merged · updated

    Axiōma: marks the few phrases in an agent's reply that deserve a second look. It advises; it never approves anything.

    install hermes plugins install hermes-axioma

    hermes-axioma codePR #149364PR #151033

  4. hermes-standing 0.1.2

    merged

    A worker's proven record sets what still needs the owner's approval; a task is not done until a check Standing ran itself passes.

    install hermes plugins install hermes-standing

    hermes-standing codePR #150366

  5. hermes-gatekeeper 0.1.0

    merged

    Owner-configured policy checks on recognized outbound messaging calls; it does not inspect connector, MCP, browser or script sends.

    install hermes plugins install hermes-gatekeeper

    hermes-gatekeeper codePR #151074

  6. hermes-axiom-agent 0.1.0

    merged

    Adds the nine-article Axiom Doctrine to each model turn and reports which enforcers are loaded and enabled; it enforces nothing itself.

    install hermes plugins install hermes-axiom-agent

    hermes-axiom-agent codePR #151218

# check it yourself, from any Hermes install

$ hermes plugins info hermes-axiomahermes-axioma [community]Repo:github.com/percyhendrux123-prog/hermes-axiomaVersion:0.3.1Pinned SHA:442374c11b3f03598ea6ff9fb6263e13af505795Maintainer:percyhendrux123-progTools:axioma_cardInstall:hermes plugins install hermes-axioma

Catalog snapshot checked Nov 9, 2026; merge and update dates use UTC. Output trimmed; the full entry also lists hooks and what the plugin does. Check the other entries the same way: hermes plugins info tripwire, hermes plugins info handydandy, hermes plugins info hermes-standing, hermes plugins info hermes-gatekeeper and hermes plugins info hermes-axiom-agent.

# community plugins, written and maintained by us. Hermes Agent is made by Nous Research.

Limits of authority

A draft is never an approval.

Delegated

Reading, sorting, drafting, editing, and checking the result.

Held for approval

Anything that sends, publishes, spends, or alters a customer record. Prepared completely, then held.

Reserved to the owner

Moving money, setting prices, and making commitments in the owner's name.

Method

When rules and regulations begin to move, it's no longer solely governance. It's operations.

Before a system runs, we write down what starts the work, what counts as done, and where it has to stop and ask.

  1. 01Intake.A request, message or deadline enters the system.
  2. 02Context.Prior notes and decisions are gathered first, so the owner is not asked to explain again.
  3. 03Preparation.The draft, the edit or the next action is produced in full.
  4. 04Decision.Anything that commits the business waits for the owner.
  5. 05Record.The outcome is checked and written down, so the next session starts where this one ended.
Diagram titled One client's full system: six mechanisms in a ring around the owner, with research, content, leads and calls, and client care shown.
Axiom Explained. Every mechanism, in order, with the gates shown. 2:10.
P. K. Stewart, founder of Deploy Axiom, in black and white, leaning against a storefront window in a turtleneck and hat.

Founder

P. K. Stewart, founder, Deploy Axiom · Baton Rouge, Louisiana

He designs each system, writes its limits, and approves every new permission it gets.

He runs two companies of his own the same way: a roster of sixteen AI agents (as of Nov 9, 2026) behind one front door, and no job closed without evidence.

To reach him, send a brief or book a call.

LinkedIn · GitHub

Findings

What we found running our own operation.

  1. FR 01One Tempo.An independent reviewer found four safety defects that our own tests had passed.
  2. E 05Weights.A model learns the way an athlete preps: run the week, measure the miss, trace it to its cause, adjust a little, repeat. Try the neuron yourself.
  3. 01One Front Door.When an agent says "done", nothing closes. A job closes only after it is checked against the file, the page or the message record.

All notes

Start an engagement.

Tell us the work you keep having to remember. We write down what starts it, what counts as done, and where it stops for you.

Write a short brief

Six short answers. AXIOM, our operating agent, reads every brief and replies the way you ask. If the work fits, P. K. Stewart takes the call.

Team size

No secrets. Do not include passwords, API keys, private records, or other secrets.

Book a 15-minute call