You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Replaced 3 broken links to non-existent README-arch-sovereign-ingress.md
- Updated all references to point to existing README-arch-sovereign-unified-identity.md
- Clarified that unified identity document covers both ingress and egress architecture
- All architecture links now functional
Copy file name to clipboardExpand all lines: hybrid-cloud-poc/README.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ For full use case descriptions, value propositions, and regulatory context, see
61
61
62
62
### PoC Implementation Coverage
63
63
64
-
This PoC provides end-to-end implementation for **Stage 2: Trusted Egress & Data Center Infrastructure Attestation**. Stage 1 (Verified Ingress) is defined architecturally in [README-arch-sovereign-ingress.md](README-arch-sovereign-ingress.md).
64
+
This PoC provides end-to-end implementation for **Stage 2: Trusted Egress & Data Center Infrastructure Attestation**. Stage 1 (Verified Ingress) is defined architecturally in the [Unified Identity & Trust Framework](README-arch-sovereign-unified-identity.md).
65
65
66
66
| Use Case | Stage 1: Verified Ingress | Stage 2: Trusted Egress | PoC Status |
- 🔲 Privacy-preserving geofencing (ZKP-based Reg-K compliance without storing GPS) - See [Unified Identity & Trust Framework](README-arch-sovereign-unified-identity.md)
82
82
- 🔲 Privacy-preserving data center audit trail (batch & purge proofs) - See main [README](../README.md#layer-3-ai-governance-verifiable-logic--privacy)
83
83
84
84
---
@@ -97,7 +97,9 @@ The AegisSovereignAI framework implements this loop through:
97
97
## Stage 1: Verified Ingress (Roadmap)
98
98
The AegisSovereignAI framework treats the trust chain as a closed loop. For a detailed technical breakdown of the Ingress hardware-rooted provenance, see:
0 commit comments