I build systems that help businesses carry their responsibilities.
Dominus Foundry builds and operates Managed AI for businesses. Sabina is your company's own AI, with Forge included and work agreed around your information and authority. DominusOS supplies the authority architecture; Forge supplies a structured operating workspace. Specialist tools are confirmed in the written scope.
Your company’s own AI, the authority she works under, and the record the work lands in.
Dominus Foundry builds and operates Sabina. DominusOS supplies the authority architecture. Forge comes with every Sabina engagement as the structured workspace. Specialist tools are scoped separately; Forge is also available on its own.
Start with a question worth answering or a responsibility worth carrying: company understanding, preparation, communication or permitted follow-through. Foundry sets up and operates Sabina with Forge included. Your team selects the information and authority; reviewed context can carry forward into the next question, draft and responsibility.
Runs on a core model trained and operated by Foundry.
Shaped around your company by our own memory and teaching systems.
Her understanding can grow; her authority comes only from the permissions you grant.
Where the proof stands, and your company’s data
She answers Dominus Foundry's own lines today — the proof is on our account, not yet on a customer's, and a founding seat is how that changes. See current founding availability. Pricing comes in a written proposal. What she learns working for a company belongs to that company’s account, and what it takes with it if it leaves is set in its agreement.
Your company’s knowledge, memory, operating instructions, and permissions remain specific to your company, and access follows the sources and authority you approve. See the trust and company-data page.
Authority has to be written down before it means anything. DominusOS is where it gets written, granted and checked. Where a permit is required, the action is recorded before it is carried out and carries a signed, single-use permit bound to that company, that capability and those exact details.
Bounded authority
On supported governed paths, model observations do not grant authority. Accepted owner restrictions constrain execution; widening requires deliberate confirmation.
Attributable action
On supported governed paths, attempts and outcomes have a record, including refusals and approval waits, with the authorizing grant or approval.
Receipt before speech
On supported completion-check paths, a booking, send or change needs a committed record before it is described as complete. Coverage depends on the channel.
Example
Not a real permit, and not the format one travels in — what a single permit binds, in plain language.
Authorised by
the authority that allowed it — a person’s approval, or a standing restriction that did not apply
For
this one company, and no other
To do
one named thing — here, book one appointment
With
these exact details, not the action in general
Good for
a short window, and then no longer
Uses
one — minted once, consumed once
Signed
anyone holding it can check the signature; only the authority service can issue one
DVOID
Change the rules and the permits already issued stop being good.
What the permit does not cover yet
Precisely, because the difference matters: the permit does not cover everything she does yet. Some call actions run under documented exemptions, and some requests to the phone carrier are limited to approved destinations instead. Those are weaker checks than a permit.
And its scope today is exactly one: it is the governance layer Dominus Foundry built for Sabina, and it governs one managed private AI, for real work — hers.
Forge comes with Sabina as the structured operating workspace and is available independently. Move agreed work into Forge where practical; retained systems need assessed API reads and writes. Core, Hyperion, Sigil and Torch have defined scopes; Ariadne and Treasury are in development. Specialist tools are confirmed in writing, not assumed included.
Coreas the system of record
Hyperionfor spatial capture and pricing
Sigilfor signatures
Torchfor the dialer and call intelligence
AriadneOne record of the job, and tools that share it.
TreasuryOne record of the job, and tools that share it.
Forge is in paid use at All Weather Roofing, Albuquerque; Sabina is not onboarded there.
AV and security runs at CalLord — a separate, founder-affiliated integrator.
Fire and life safety, solar and property management are in development.
Forge’s paid roofing use is the current trade foothold. CalLord is founder-affiliated, and Foundry’s Sabina use is internal; neither is an independent Sabina customer case study.
Why there are three, and how they fit together.
SabinaDominusOS→ depends on
She cannot act on her own say-so. The actions she is governed for — a booking among them — need authority that was granted first, and a refusal is written down as carefully as a success.
DominusOSForge→ depends on
Forge holds the agreed business records — such as a client, scope or schedule. On supported governed paths, a permit binds the action to those details and the resulting record can be checked afterwards.
ForgeSabina→ depends on
Forge supplies structured business context for useful questions, drafts and follow-through. On supported completion-check paths, a claimed booking or update needs a saved result; not every channel is covered.
Forge can be used on its own and comes with every Sabina engagement. We prefer to move agreed work into Forge; keeping another system requires a supported API connection. Specialist tools are confirmed in scope.
The company
Dominus Foundry builds all three.
Fide et Familia — held by the Lord family, from Albuquerque.
Dominus Foundry is held by Bri and me — a family business in Albuquerque, and everything above comes out of it.
Sabina runs on a core model trained and operated by Foundry. Our proprietary memory and teaching systems shape that foundation around each company, while that company’s permissions define what she may do. One reusable core and one set of systems, with each company’s knowledge kept its own — that is how a two-person shop builds and operates it.
We have bootstrapped it to here. What is already in production, what we are raising for, and what it is meant to become are written out in full on the investor pitch — it lives at the Foundry, not here.
Patent pending. Non-provisional 19/791,511, filed 30 August 2026, held in Dominus Foundry LLC.
The maker
An operator long before I was a founder.
Storefronts
I started in storefronts, not server rooms — two Cold Stone Creamery shops in Albuquerque before I was old enough to know better.
The labs
Then eighteen months in the labs, on the team that helped bring LED lighting into the world we now take for granted.
A few hundred rooms
Most of the years since I spent in sales and business development — learning, in a few hundred rooms, exactly what the work needs and what the tools keep getting wrong.
MMXXV · Two companies
In 2025 I built two companies to answer it: CalLord, a commercial security & AV integration firm I own half of, and Dominus Foundry, which Bri and I own outright. They are two companies, not one with two names: CalLord does the security and AV work and uses Forge in it; the Foundry builds and operates Managed AI for businesses — Sabina, your company's own AI, and the systems beneath her.
Fide et Familia
Built alongside my wife Bri Lord, Dominus Foundry’s CEO and my co-founder on Sabina and Forge — Fide et Familia. By faith and family.
iPad LiDAR captures the geometry in about sixty seconds. Hyperion prices from the scan and puts the proposal in front of the customer in one visit. It is the instrument I wanted in the field and could not buy, so we built it.
~60sGeometry capture
iPadOSNative · LiDAR
LiveAll Weather Roofing
Live today at All Weather Roofing in Albuquerque. No measured cycle-time reduction is claimed.
Hyperion · iPad LiDAR capturePoint cloud, filling in over six seconds
iPadOS
Six seconds of an iPad LiDAR capture: a point cloud of a space, scattered at first, thickening pass by pass until the walls, the floor and the fixtures in it are continuous surfaces.
The index
Where the work lives.
Dominus Foundry and the products it builds — and, listed apart because it is apart, the integration company I co-own. Each of these is a real, running surface, not a page about something that is coming.
