Sovereignty isn't a layer. It's a stack.
The research runs in two connected lines: a sovereignty architecture framework that identifies where sovereignty is required — and a hardened computing element, the Application Specific Processor (ASP), that makes control, transparency and continuity hold at the layer everything else rests on.
Two lines, one stack.
The research spans two connected lines: a framework for understanding where digital sovereignty is required and where it fails — and a hardened computing element that closes the gap at the silicon layer.
The Sovereignty Architecture Framework
Sovereignty modelled as a relation between governor and system, assessed through four capability classes: Control, Continuity, Transparency, Independency.
The Application Specific Processor
A hardened, minimal computing element: cores are finite-state machines generated from C/C++ source. No code execution, no instruction cache, reduced attack surface by construction.
Take this further.
Interested in the research, a collaboration, or how the ASP and the sovereignty framework apply to your systems?