Assurance

“Show me that your AI cannot write to the schedule.”

So we ship a test that tries. Operations buys the outcome; IT approves the pathway — and the pathway is designed to be reviewed, not explained away.

The proof

A deterministic core, a probabilistic layer above it.

Completion is computed per edge rather than stored as a flag. The AI can propose; it cannot write. We will show you the schema.

  • Every question routes to a closed, fixed catalogue of engine-backed answers.
  • Every number is computed by a deterministic tool — the model never does arithmetic.
  • Anything outside the catalogue is refused with fixed text, not model narration.
  • The AI runs on its own database role, with INSERT revoked on every authoritative table.
  • A post-answer check re-verifies every figure against the source; a mismatch fails the response.
vantomic_agent=> INSERT INTO fact
                 (activity_id, fact_type_code)
                 VALUES (…);

ERROR:  permission denied for table fact
SQLSTATE: 42501 (insufficient_privilege)

Postgres

Enforces it. Not the application. Not a prompt.

Read-only

The AI can write to a scratchpad. Nothing else.

Drift-guarded

A new table stays locked until a migration unlocks it.

The agents run in a separate process that holds no privileged database credential at all — so there is nothing to misuse.

Integration

We read your systems. We never write back.

Read-only, one-way file exports — no agent, no inbound connection to the plant. The architecture is one connector interface, so a new source is a config, not a rewrite.

Primavera P6

.xer import, dry-run preview before commit

IBM Maximo

Work orders, closures, attestation timestamps

Hitachi Asset Suite

The dominant nuclear EAM — AP-913 / AP-928

eSOMS / clearances

Guaranteed shutdown state, tagout, clearances

OSIsoft / AVEVA PI

30-year historian trend for frequency justification

VSDS · GEDDS · RMS

Survey and telemetry history, gated migration toolkit

Sentinel · HIS-20 · REMS

RWPs and dose of record from your system of record

Syntempo / STO

Read execution status; we don't compete for it

Deployment

Your data sits where you decide it sits.

Hosting location is not what determines a Critical Digital Asset — function and pathway are. What matters is that the flow is one-way and the outputs are advisory.

Recommended

Your own cloud tenant

You own the subscription, the region, the keys and the bill. We never hold your data. Fastest route to a first deployment.

US-persons-only operations

AWS GovCloud (US)

FedRAMP High, DoD IL4/IL5. Frontier models run here, inside the boundary you already trust.

US-citizen-validated staff

Azure Government

FedRAMP High and IL5, and the only cloud with a published 10 CFR 810 position.

Nothing leaves the building

Fully on-premise

Your hardware, your perimeter — a distinct product with a distinct support model, because it is one.

The commitments

Advisory by construction, not by policy.

Non-safety-related

Advisory only. Performs no safety function, credited for none. Outside 10 CFR 50 Appendix B.

One-way by design

We ingest exports. No inbound connection, no agent, no pathway into any Critical System.

Your tenant, your keys

Deployed where you choose. We never hold your data and never see your dose records.

Not cited in any procedure

Deliberately built so the tool is never a credited input to a shutdown-risk decision.