Compute centrally,
support decisions independently at the field edge.
CREAIM Defense targets a deployment model that connects central Command/C2 Runtime with on-device and Edge Runtime rather than relying on a public-cloud service. Mission Data remains inside designated security boundaries, and when communications are constrained the field node is designed to perform limited re-computation using the last synchronized state and Local Conditions.
Operate Runtime Core and Evidence Store on internal institutional servers/accelerators.
Deploy C2, Data Adapter, and Runtime Node on an internal network without external internet.
Deploy a reduced Runtime on field hardware for selective State re-evaluation.
Connect central control and field Runtime through one Mission State.
Mission Objective · Common Operational State · Rule Set · Approval
Normalize · Multi-COA · State/Branch · Constraint · Failure Elimination · Evidence
Last Sync State · Local Sensor Conditions · Local Constraint Gate · Selective Re-evaluation
When communications fail, the system does not pretend to know.
If a field node cannot receive the latest central state, it first checks data freshness and available Constraints. When required information is missing, the target behavior is to move to HOLD or NEED_MORE_DATA instead of generating GO from arbitrary defaults.
Security is a boundary across the entire Runtime, not a single feature.
Define storage, processing, and export boundaries for Mission data inside the deployment environment.
Target architecture for linking user, role, permission, and approval boundaries with institutional identity systems.
Separate input, Candidate, Run, and result by execution unit and preserve independent Trace.
Record Run ID, Input Hash, Core Version, Seed, and Replay Result.
Exchange only authorized data between central and field nodes.
When links or data are insufficient, use HOLD / NEED_MORE_DATA instead of automatic assumptions.
The architecture does not assume all raw data must be sent outside.
Depending on institutional security policy, raw Sensor/C2 data can remain inside the Source System or On-premise Adapter boundary while only structured conditions required by Runtime are forwarded, or the entire Runtime can be deployed inside the same secure network.
LLMs do not make or authorize mission decisions.
LLM is an auxiliary layer for structuring natural language and documents into Fact/Context or explaining Runtime results. State, Branch, Constraint, Failure Elimination, Runtime Status, and Evidence Trace are handled by the Runtime Core.
Distributed Edge Runtime, Tactical Network state, adversarial input quarantine, Hardware Trust/Authorization, Mission Safety Kernel, and re-synchronization logic have been verified in synthetic environments.
Military security accreditation, real closed-network integration, crypto modules, military Edge hardware, EW/communications-loss conditions, and 1–2 second end-to-end latency remain targets until measured and certified.