What needs to remain under your authority?
A case can include correspondence, working documents, declared records, decisions and evidence received from another organisation. Sovereignty involves more than the physical location of a server. The responsible institution needs clear control over access, operating arrangements, export and the record’s lifecycle.
For an initial assessment, ask who operates the environment, who can change access, how records and metadata can be exported, and what happens when a supplier or network connection is unavailable. These questions help define requirements; no single hosting choice answers all of them.
Civil records and defence cooperation share a records problem
A ministry closing an administrative case and a team completing a defence-cooperation handover both need to preserve the record of what happened. Their mandates and handling rules differ. The common foundation is registration, context, controlled access and an accountable lifecycle.
Here, dual use means developing that foundation for civil and defence contexts, with explicit policy and assurance requirements for each. The records platform preserves decisions and supporting evidence. Live command, tasking and operational control remain in the relevant operational systems.
How EMBI approaches the problem
EMBI provides the open-core case and records foundation. Working capabilities include registration, declared versions and lifecycle workflows. The institution chooses its hosting and operating arrangements; those arrangements still need to be assessed for its intended use.
EMBISEC adds the security-classification layer. Classification, clearance and case-level need-to-know controls form the present foundation. Binding source restrictions consistently to recipient policy, full profile conformance and accreditation remain development or assurance work.
EMBISEC-L explores prepared local records work during interrupted communications. Lab workflows demonstrate local work and queued synchronization. Secure disconnected deployment, complete receipt handling and operational acceptance require further work.
A concrete starting point: one handover
The product illustrations use fictional host-nation-support records: a situation report, a signed handover package, supporting records and an after-action review. The useful question is whether the receiving team can identify the records, understand their restrictions and record what it has accepted. The illustration is a discussion aid, not evidence of a customer deployment.
What a pilot should establish
Start with one receiving institution, a defined set of synthetic records and explicit responsibilities. Agree what registration, access, export and acceptance must demonstrate. Record gaps as well as successful outcomes before deciding on a wider deployment.
EMBI is an early product seeking pilot partners. Its civil foundation, security layer and local-work configuration have different readiness levels. No NATO accreditation or blanket compliance is claimed.
Need help defining your requirements first? Móholt offers independent case-management assessment and advisory.