HullSmith Horizon
The wall. The firewall at the gates.
Every contained agent reaches your data only through five numbered gates. Horizon fuses exfiltration physics and hallucination checks in one call. A blocked write is a signed certificate, not a hope.
02 · The invariant
Gate 01 · In
Context in
PASS · sanitized, field-masked context
BLOCK · prompt-injection or unmasked field
Gate 02 · Out
Results out
PASS · grounded result, no data loss
BLOCK · hallucination or DLP hit · incident
Gate 03 · Out ↑
Egress to the surface
PASS · DLP-clean payload to the screen
BLOCK · residual leak toward L3
Gate 04 · ⇄
Tool call, resolved
PASS · engine call, typed I/O
BLOCK · raw system or unscoped tool
Gate 05 · In
Task dispatch
PASS · scoped, short-lived task token
BLOCK · standing session or broad token
Walk the wall with the engineer who runs it.
A G1 call is free. Bring your security questionnaire ; we answer it gate by gate, show a blocked write, and put a signed certificate in front of you.
01 · Five gates
Context in, results out, egress, tool I/O, task dispatch. No sixth path.
02 · Horizon fused
Physics and hallucination, one verdict, a signed certificate.
03 · Honest status
Production. Standalone, or inside MaxorConnect.
04 · No training loop
No customer data in any training loop. Agents propose ; a human approves.
The deployment schematic
Five gates. If a change draws a path around the wall, the change is wrong.
Every line entering or leaving the containment cell transits one of these. There is no sixth path — not for our agents, not for a vendor's, not for yours.
Gate 01 · In
Context in
Governed context enters the cell sanitized — prompt-injection screened, fields masked to policy.
PASS · sanitized, field-masked context
BLOCK · prompt-injection or unmasked field
Gate 02 · Out
Results out
Every result is screened for hallucination and data loss before it leaves. Blocked = withheld, and recorded as an incident.
PASS · grounded result, no data loss
BLOCK · hallucination or DLP hit · incident
Gate 03 · Out ↑
Egress to the surface
DLP on the way up to the product surface — what reaches a screen has crossed two gates.
PASS · DLP-clean payload to the screen
BLOCK · residual leak toward L3
Gate 04 · ⇄
Tool call, resolved
Substrate I/O both ways screened — an agent asks the deterministic engines, never the raw system.
PASS · engine call, typed I/O
BLOCK · raw system or unscoped tool
Gate 05 · In
Task dispatch
Work enters the cell as a scoped, short-lived task with a scoped token — not a standing session.
PASS · scoped, short-lived task token
BLOCK · standing session or broad token
Invariant
No contained agent reaches a product, the control plane, the substrate or a client system without crossing HullSmith.
✕ BLOCKED — hallucination or DLP hit — withheld, recorded as an incident
5
numbered gates — no sixth path
1
signed certificate per blocked write
0
ML, GPU, or training data — nothing to drift
Cloud → Air-gap
runs where your agents live
The wall, the firewall, the proof.
Signature scanners catch what they have already seen. Language models invent fluent lies. HullSmith is neither. It is the numbered wall around contained agents. Horizon is the firewall fused at that wall — physics of exfiltration and hallucination-verify in one call. The moat is the receipt you can replay, not a claim that the wall is inviolable.
Five gates. No sixth path.
Every contained agent reaches a product, the control plane, the substrate or a client system only by crossing HullSmith. A change that draws a path around the wall is the wrong change.
Horizon: physics and hallucination, one call.
Horizon is the public name of the firewall fused at this wall — deny-default syscalls, scoped tools, exfiltration physics, and a deterministic hallucination-verify fabric. HullSmith consumes it and vends the signed certificate. The embeddable SDK for third-party AI output lives on /products/maxor-ground — a different placement, not a second HullSmith.
Gate. Fuse. Sign.
An agent hits a numbered gate. Horizon scans. You get a verdict you can replay.
01 — Hit a gate
Context in, results out, egress, tool I/O, or task dispatch. Five numbered crossings. There is no sixth path — not for our agents, not for a vendor's, not for yours.
02 — Horizon fuses the scan
One call measures exfiltration physics and hallucination at the same gate. Deterministic: same input, same verdict. No model to train, nothing to poison, nothing to retrain.
03 — Sign the certificate
PASS ships. BLOCK withholds the write and signs a certificate you can replay. The billable unit is that receipt — proof, not a hope the wall held.
The wall you can prove.
Built to sit inline on the agent boundary — and to be checked, not trusted on faith.
Five numbered gates
Context in, results out, egress to the surface, tool I/O, task dispatch. A path around any of them is the wrong architecture.
Hallucination-verify fabric
Every result leaving the cell is screened for ungrounded claims before it ships. A fluent lie is withheld and recorded — not delivered as a fact.
Exfiltration physics at the same gate
Information flow, channel entropy, access pressure — measured, not matched to a signature list. A novel leak trips the same alarm.
Signed certificate
The billable unit. PASS or BLOCK with the gate, the check, and a receipt your auditor replays without calling us.
Deny-default. Scoped tools.
Syscalls denied unless allowed. Lateral movement blocked. Tools scoped. Egress only through a gate. The agent cannot talk its way past.
No ML, no GPU, no training data
Nothing to drift, nothing to poison, nothing to retrain. Small enough for cloud, self-hosted, or air-gap.
The writes that should never leave the cell.
Each is a gate failure you can name. A novel variant trips the same check — no signature update required.
Ungrounded results
A fluent answer that is not in the source — the classic hallucination — caught at Gate 02 before anyone downstream sees it.
Exfiltration & residual leak
Abnormal information flow toward the surface or a client system — flagged before the data crosses the point of no return.
Prompt injection & unmasked fields
Context that tries to walk into the cell carrying an instruction or a raw field the policy said to mask — blocked at Gate 01.
Unscoped tools & raw system
An agent asking the operating system instead of a typed engine, or a tool outside its scope — refused at Gate 04.
Standing sessions & broad tokens
Work that wants a permanent session instead of a short-lived, scoped task token — refused at Gate 05.
The sixth path
Any architecture that draws a line around the wall. HullSmith's invariant: if the change creates a sixth path, the change is wrong.
Hosted, or entirely inside your perimeter.
Start in the cloud ; bring the wall in-house when your security review — or your data-residency rule — demands it. The math does not need the internet.
Cloud
Fully managed on Canadian-resident infrastructure. The fastest way to put HullSmith in front of an agent — nothing to provision.
Self-hosted
Run the wall inside your own environment — your keys, your infrastructure, your control plane. Signals never leave your network.
Air-gapped
Fully disconnected for the most sensitive deployments. No telemetry, no phone-home. Deterministic and small enough to run offline.
Anyone putting an agent near data.
If software — or an AI agent — can act, you need a verdict you can defend on what that action was allowed to do.
One deterministic philosophy, across the suite.
HullSmith is the Maxor stack's own agent-containment boundary. Horizon is the firewall brand fused at that boundary. The document-grounding SDK on /products/maxor-ground is a different placement — embeddable in any third-party AI output — not a second HullSmith.
Explore the Maxor suiteAvailability
—
Status
Production
Deployment
Cloud · Self-hosted · Air-gap
Owner
Maxor Digital · IP held by Maxor Global LLC
Walk the wall. See a blocked write.
A G1 call is free. Bring the questionnaire. We answer gate by gate, show a blocked write, and put a signed certificate in front of you — not a brochure. Production. Standalone, or inside MaxorConnect.
HullSmith, answered
HullSmith is the wall. Every contained agent — ours, a vendor's, yours — reaches your data only through five numbered gates. Horizon, the deterministic firewall, sits behind them. Production. Same stack as Architecture, zoomed on L2.5.
Context in, results out, egress to the surface, tool I/O, and task dispatch. There is no sixth path. A change that draws a path around the wall is the wrong change.
Horizon is the public brand of the firewall fused at HullSmith's gates — physics and hallucination-verify in one deterministic call. You buy HullSmith. Horizon is not a second product.
Yes. Cloud, self-hosted, or fully disconnected. The math does not need the internet, and because it is deterministic and small, the full scan runs offline.
A G1 call is free. Bring your security questionnaire; we answer it gate by gate and put the answers in writing. Request it on this page — nothing here trains a model.