System Architecture
Diagram-led documentation of the InvarOS platform: from the native invarosd daemon running on real hardware, through the enterprise orchestration and policy layer, to the air-gapped evidence and federation model.
Where InvarOS sits
InvarOS operates as infrastructure beneath AI agent systems, not as a proxy in front of them. It captures, verifies, and attests — without routing every agent call through a cloud gateway.
Server and edge deployments
invarosd has been deployed on two hardware targets with different system configurations. Both produce authentic TBoM 3.0.0 artifacts and cryptographic receipts.
Dell x86_64 Linux Server
GL-MT3000 OpenWrt Edge Router
From physical node to verifiable receipt
Every topology observation flows through a deterministic pipeline, producing cryptographically linked artifacts at each stage.
Topology Discovery
invarosd topology plugin scans host interfaces. Nodes classified as bridge, physical, logical, tunnel, or neighbor. Edges inferred from bridge membership.
tbom_v3.0.0 · topology_fingerprint Receipt Generation
Receipts plugin emits HMAC-SHA256 signed evidence per execution event. Each receipt references the host fingerprint and observation epoch.
receipt · host_fingerprint Attestation Pipeline
Enterprise platform Continuous Attestation Pipeline generates CycloneDX 1.6 CBOM, in-toto DSSE envelope, and ZK compliance claim from orchestrator results.
CBOM · in-toto · ZK claim Federation Recognition
Recognition packets aggregate receipts and topology fingerprints asynchronously. Local/offline — no peer discovery, no consensus protocol. Transport is the operator's responsibility.
recognition_packet · chain_fingerprint TBoM 3.0.0 artifacts from live deployments
The following JSON structure represents the schema of topology artifacts produced by invarosd. Node IDs, fingerprints, and epochs are authentic. MACs and final IP octets are masked for publication.
Dell x86_64 TBoM fragment
"topology_fingerprint": "93c9dec0c9dea70b
0fd8392d0a9322d8
8281e875627e080f…",
"subsystem_identity": {
"host_fingerprint": "044eb029…",
"observed_at_epoch": 1782690885
},
"graph": {
"nodes": [
{ "name": "docker0", "type": "node_bridge",
"status": "UP", "ip": "172.17.x.x" },
{ "name": "veth43d2eca", "type": "node_logical" },
{ "name": "wlp3s0", "type": "node_physical" },
{ "name": "tailscale0", "type": "node_tunnel" }
],
"edges": [
{ "source": "veth43d2eca", "target": "docker0",
"relation": "bridge_member" }
]
}
GL-MT3000 TBoM fragment
"topology_fingerprint": "a92137f8a9d4161c
d8e4f604cc140ee3
cdbda4dd0f24d9fc…",
"subsystem_identity": {
"host_fingerprint": "ca1d805c…",
"observed_at_epoch": 1782691017
},
"graph": {
"nodes": [
{ "name": "br-lan", "type": "node_bridge",
"status": "UP", "ip": "192.168.x.1" },
{ "name": "ra0", "type": "node_physical" },
{ "name": "rax0", "type": "node_physical" },
{ "name": "apcli0", "status": "UP" }
],
"edges": [
{ "source": "ra0", "target": "br-lan",
"relation": "bridge_member" }
]
}
These fragments are derived from authentic deployment artifacts. Complete TBoM JSON files (with MAC addresses and internal IPs masked) are available on request during pilot and consulting engagements.
Air-gapped, asynchronous federation
InvarOS federation does not require a persistent cloud connection. It uses a three-pillar trust model based on cryptographic fingerprints alone.
Governance (Rule)
Canonical policies define boundary conditions. Policy-to-ZK compiler generates deterministic, fingerprinted schemas. Rules are the authority that other pillars reference — they do not change per-tenant.
Commitment (Proof)
Tenants generate commitment arcs progressing Intent → Consent → Settlement. Each transition is cryptographically witnessed. Commitment C ABI and Temporal Micro-Chain provide native-layer proof generation.
Federation (Recognition)
Structural acceptance of commitments across boundaries. No consensus protocol. No WAN broadcast. The FederationRecognitionAdapter processes recognition asynchronously via thread pool, returning futures immediately.
Air-gap operation: Because invarosd generates topology evidence and receipts locally and autonomously, the runtime does not require a persistent connection to any control plane. Evidence batches can be physically transported across air-gaps. The federation model was designed specifically for classified, sovereign, and highly regulated environments where always-on cloud connections are architecturally prohibited.
Ready to plan a deployment?
Architecture assessments, topology extraction engagements, and pilot design are available now. Contact us to discuss your environment.