Deploy Axiom™
The Axiom mark: three cut circles, and a triangle nobody drew™

Nothing in your business waits on you to remember it.

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

Built for owner-led firms where everything waits on you: insurance agencies, law offices, financial advisors and CPAs, real estate teams, medical and dental practices, coaches and founders’ offices. In regulated work, every text clears 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.

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.

Who it’s for

The job changes by field. The rule doesn’t: anything that sends, spends or commits the business waits for your yes.

Insurance agencies

Client care after a policy issues: a birthday note where there is a date, then regular check-ins by text and email through the first year, each one checked before it goes for opt-out, the client’s own local hours and the approved wording. See the field report

Law offices

The attorney’s calendar and deadlines kept straight, and routine letters and record requests drafted for review before they go.

Financial advisors and CPAs

Client review meetings scheduled on their cycle, open paperwork tracked, and the follow-up after each meeting drafted.

Real estate teams

Past-client care after closing: anniversary notes, check-ins and review requests at set points, with the client records kept current.

Medical and dental practices

Appointment changes, reminders and patient callbacks drafted from your own systems for your staff to approve.

Coaches and fitness studios

Member follow-up: check-ins, renewals and the members who have gone quiet, each message written in your words.

Founders’ offices

Calendar, inbox triage, meeting prep and the follow-ups that come out of each meeting.

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.

Regulated work

We work in fields where HIPAA applies. Your compliance stays with you and your systems; if you need help there, we'll point you to people who specialize in it.

Work

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

  1. Insurance agency 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

Public code, for technical reviewers

Our agents run on Hermes Agent, an open-source agent platform made by Nous Research. These are pieces we built for it and publish; a plugin is an add-on any Hermes install can load.

  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

  2. Tripwire

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

    evidence: public, with tests

  3. 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

Read all field reports. Six of the plugins we run on our own agents are accepted into the Hermes Agent plugin catalog: see the six plugins. How the whole system works for a founder: The operator layer.

Built on an axiom

An axiom is a first truth. It is not proved; everything else is built on it.

Euclid, Book I, Proposition 1: on the line AB, a circle with center A through B and a circle with center B through A cut at C; joining CA and CB gives an equilateral triangle.ABC
Euclid, Elements, Book I, Proposition 1

Euclid’s Elements opens with axioms: five postulates and five common notions. Its first proposition builds an equilateral triangle from two circles.

Given a straight line AB:

  1. 1With center A, draw the circle through B.
  2. 2With center B, draw the circle through A.
  3. 3Where the circles cut, mark C.
  4. 4Join CA and CB. Each is a radius equal to AB, so all three sides are equal.

Our mark is that triangle, left undrawn: three cut circles, and the eye completes a shape nobody drew. Gaetano Kanizsa described the effect in 1955.

Axiom is built the same way. One rule comes first, and every agent we deploy works from it.

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.Each part of the chain, and where it has to stop, is described below.

Skip the system map
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 two companies on the same idea. Sixteen specialist AI agents (as of Nov 9) (second look) 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

An outcome without a recorded readback counts as an outcome, never as verified. Counts from our own company's records, not client data. See the work.

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.
Read the transcript

Operations brief. One client, starting from zero. Every mechanism we run, in the order the work actually happens. A box is a step the system runs. A diamond is a check that runs every time. A square is a person saying yes.

It starts with research. The business, its market, its audience, and the facts. The owner gets a short yes-or-no list. Nothing is posted yet.

Then content. The owner films on their own phone. We edit, keep their exact words, and write the captions. It’s checked for facts and fit, and the owner approves it before it goes public. Engagement turns into new prospects, and what worked feeds the next round of research.

New messages are checked every five minutes, and the owner gets a private alert. A reply is drafted in their words. It only goes out when the owner says yes. Money, contracts and complaints always go to a person.

Every call is answered. The caller is told it’s an AI. Spam is screened, the details are taken, and a person will take over the call. We run this on our own business first.

After the sale, no one is forgotten. The day a policy is issued, the client’s first year is planned. Check-ins all year, with consent, opt-outs and quiet hours respected. A referral ask only goes out with the owner’s yes.

The owner has one thread with us, and every message is read and logged. Simple questions get answered. New work or money goes to a person. Anything personal is left alone.

Every mechanism passes the same gates. Facts checked against sources. Fit with the client. A fresh set of eyes. Then a person says yes, and it’s logged.

Put together, that’s one client’s full system. Research feeds content. Content brings prospects. Prospects become clients. Clients are cared for, and what’s learned goes back to the start. Now zoom out. Same system, many clients. Nothing in your business waits on you to remember it. Axiom.

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.

What we found running our own operation

  1. Field reportClient Care for an Independent Insurance AgencyClient care is now set up to run without the owner remembering it. Referral asks still wait for her yes.
  2. EssayWeightsA 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. NoteOne Front DoorWhen 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

Book a call, or send a brief.

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.

Book a 15-minute call
Write a short brief

Six short answers. Our AI agent reads every brief first and replies the way you ask. If the work fits, P. K. Stewart takes the call.

If you give a mobile number, we reply about your brief by text to that number only. Reply STOP and we stop.

Team size

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