Integration, by design.
DRIFT is a sealed Docker engine. Integrate against ICD-DRIFT-001, the stable public interface contract. Your systems don't change. Our engine doesn't open.
Most AI products require deep integration. Yours has to change to fit theirs. DRIFT is built on the opposite principle.
The contract
DRIFT operates as a sealed Docker engine with a single stable interface defined by ICD-DRIFT-001, the Interface Control Document. Your systems integrate against the ICD, not against the engine itself.
This is a familiar pattern in aerospace and defense engineering. You don't reach into a black box; you commit to a stable contract on its boundary. The black box can evolve internally without breaking anything outside it. The systems on the boundary can evolve too, as long as both sides honor the contract.
SEALED
Inputs flow into the engine through the contract. The engine produces a structured output — the resistance landscape — back through the same contract. What you do with that output is up to you. Render it in your existing operator interface, route it to your existing decision support tools, log it to your existing audit systems. DRIFT has opinions about what the landscape contains, but no opinions about how you display or use it.
Why the engine is sealed
The engine is sealed for three reasons. Each reason matters for a different stakeholder.
Determinism through isolation
Identical inputs always produce identical outputs. No leaks, no state carryover from previous requests, no drift in behavior over time. When you replay a decision later for review, you get the same picture you had during the decision.
A clean attack surface
A sealed engine has exactly one boundary to defend, and that boundary is fully specified by the ICD. Schema-checked inputs, no outbound network calls, no telemetry beaming home. Air-gapped, on-prem, and edge deployment are all supported. The engine fits under 200MB of memory.
No vendor lock-in to the engine internals
Because the contract is on the boundary, your investment is in your own integration code, not in the engine's internal architecture. If DRIFT's engine evolves, your code does not need to change. If you ever need to swap the engine, the integration code is preserved.
What flows through the contract
Without disclosing the specifics of ICD-DRIFT-001, the contract carries four kinds of information across the boundary:
Decision context. What is the operator deciding? What alternatives are on the table? What stakeholders care about the outcome? What constraints apply?
Qualified data. What information is feeding the decision? Where does it come from? How fresh is it? How trustworthy is it? Every input carries its own provenance and quality grade.
Scoring profile. The lens through which the engine evaluates resistance. Different deployments calibrate the scoring profile to their domain. The engine itself does not change; the profile does.
Traceability. Every output carries the trail of inputs that produced it. Versioned, replayable, auditable. When a regulator or reviewer asks why a decision came out the way it did, the answer is in the record, not in the engine.
What does NOT flow through the contract
DRIFT's internal logic — how resistance is computed, how layers are ordered, how scoring is performed — is not exposed through the ICD. That logic is patent-pending and protected as intellectual property.
This is by design, and it serves the customer's interests as much as ours. If the internal logic were exposed, the engine would be subject to spoofing, reverse engineering, and replication. The contract gives you everything you need to integrate, audit, and rely on the engine. It does not give you the engine.
Deployment options
Because DRIFT runs as a sealed engine with no outbound network calls, the deployment surface is unusually flexible.
— Air-gapped. Full functionality without any external connectivity.
— On-prem. Inside your existing data center, behind your existing security perimeter.
— Edge. Running on resource-constrained devices in the field.
— Cloud. If your environment is cloud-based, DRIFT runs there too.
The engine itself does not care where it is deployed. The contract behaves identically in every environment.
Where to go from here
If your organization is evaluating DRIFT for integration, the next step is a private walkthrough where we can discuss your specific environment, data, and constraints. ICD-DRIFT-001 v1.1 is available for review under NDA.
Request a private walkthrough →
Your systems don't change. Our engine doesn't open.