03 / Local records continuity
Connection lost.Work continues.
Local-first records continuity for interrupted communications. Prepare the workspace, save local work and reconcile queued changes when the link returns.
Capability, in practice
Continuity is part of the information model.
01 /
Work through disruption
Lab workflows support prepared local work and pending synchronization during a link interruption. Offline authority, revocation, conflicts and acceptance must be defined for the deployment; a local save is not a remote receipt.
02 /
Bound labels
Security metadata must travel with prepared records and queued work. Complete cryptographic protection of local content, verified relay identity and consistent policy enforcement remain delivery gates for secure offline use.
03 /
Offline evidence
Hash-linked audit data and release evidence support integrity review. Offline verification requires retained keys and trust information; completeness, independent anchoring and the scope of captured events must also be assessed.
Built on one foundation
Your racks. Your operational boundary.
Designed for customer-controlled infrastructure and prepared local workspaces. Fully disconnected deployment is an engineering and assurance target; the current lab workflows do not establish an accredited air-gapped system or fully protected local storage.
Lab-validated at TRL 4. NATO DIANA 2027 application submitted; application does not imply selection or endorsement.
Disconnected operation / schematic
↕ Link interrupted · reconcile on return
Node · field-01 (demo) · prepared workspace · 141830Z SEP 26
Capture at source
Bring correspondence into the case.
The capture alpha links correspondence to a case using declaration metadata and a SHA-256 digest. Original content remains in the mail system in this path, so this is not yet complete archival capture. The planned ingestion engine will add verified original-content custody and explicit acceptance for approved inputs.
Sanitised console · fictional HNS exercise data (NG26) · illustrative workflow · the capture component is an alpha; the demo tenant is not accredited for classified content
Scenario A / HNS operational handover
A completed rotation. An accountable handover.
A fictional allied rotation closes out at a host-nation site in Iceland. The RMS preserves the signed transfer of responsibility, facility inventory and resource accounts. This illustrative sequence matches the home-page animation; markings are synthetic and do not classify all HNS records alike.
Bundle NG26-HNS-0007 is open under HNS Cell. The HNS team prepares its workspace while connected, registers the rotation SITREP and receives the signed handover package before the interruption.
The already-received HNS package remains in the prepared workspace. Review notes and an AAR draft are saved locally; 2 updates wait to synchronize. The final LOGREP is supporting evidence, not a live logistics task.
The illustration shows two updates synchronized without conflict. Formal registration and any recipient receipt are recorded separately. The target workflow preserves the sequence of local work and subsequent acceptance for the handover review.
Sovereignty, made visible
Know what runs. Know who controls it.
Inspect the components, custodians and connections behind your deployment — and whether the running instance still matches the release you signed.
01 / Sovereignty manifest
Your deployment, in view.
Components, hosting jurisdiction, organisational custodians and outbound connections are documented for inspection. Declared policy, observed behaviour and verified enforcement are distinct evidence.
02 / Release & record evidence
Evidence for the people who assess it.
Release manifests, the bill of materials (SBOM), content digests and audit-chain checks support review. Assess actual release results separately from these illustrative console figures.
Illustrative results · secure offline deployment remains subject to further controls and assessment.
Sanitised console · fictional HNS exercise data (NG26) · illustrative workflow · deployment details and results are illustrative build output
Standards & scope
STANAG 4774 / 4778 are conformance targets. Current EMBI metadata bindings and lab synchronization tests do not establish complete secure disconnected operation. Deployment controls require separate assessment and approval.
Standards references distinguish design targets from implemented checks. They do not imply certification, accreditation or approval for classified operation.
A deliberate boundary
Records and case management.
For accountable public authority.
EMBI preserves official records of decisions and activity. It is not a live command-and-control system. Approved transmission cryptography and cross-domain guards belong to specialist infrastructure; their integration and authorisation are separate from the RMS.
Let’s start with your requirements.
Discuss your records, security and operational environment.
Request a briefing