# VaultMesh Funding Roadmap — Visual Architecture Diagrams **Purpose:** Technical architecture diagrams for major EU funding proposals (Mermaid format) **Location:** `~/vaultmesh-core/funding-roadmap/diagrams/` --- ## Available Diagrams ### 0. Treasury Nebula Map — Complete Funding Roadmap Meta-Visualization ⭐ **File:** `treasury-nebula-map.mmd` **Scope:** All 8 proposals, €15.8M+ orchestration, 2025-2027 timeline **Purpose:** Single-page synthesis of entire funding axis **What it shows:** - **8 proposals** organized by tier (Tier 1: €12.8M, Tier 2: €5.5M, Tier 3: €2.5M) - **Temporal rhythm** (Q4 2025, Q1 2026, Q2 2026 submission cadence) - **VaultMesh core organs** as gravitational centers (LAWCHAIN, Ψ-Field, Federation, Receipts, Treasury) - **Partner constellations** (20+ organizations across 10+ countries) - **Three technical pillars** (Cryptography, Infrastructure, Intelligence) - **Expected outcomes** (budget, partners, standards, publications, pilots, TRL) - **EU policy alignment** (AI Act, DORA, NIS2, Gaia-X, EHDS) - **Cross-proposal synergies** (quantum-safe federation, shared AI governance, etc.) **Key innovation:** This is the **meta-diagram of meta-diagrams** — the funding roadmap visualized as a living organism with: - Budget mass (size indicates funding amount) - Temporal flow (timeline determines orbital position) - Gravitational pull (VaultMesh core organs bind all proposals) - Constellation connections (partners and policy compliance links) **View:** ```bash cat ~/vaultmesh-core/funding-roadmap/diagrams/treasury-nebula-map.mmd ``` **Use cases:** - Steering committee presentations (single-slide funding overview) - Investor/board briefings (civilization-scale vision) - Consortium kickoff workshops (show partners the bigger picture) - EU portal supplementary material (demonstrate orchestrated thinking) - Internal ledger record (Rubedo seal for funding axis completion) --- ### 1. PQC Integration — Hybrid Cryptographic Architecture **File:** `pqc-integration-architecture.mmd` **Proposal:** €2.8M HORIZON-CL3-2025-CS-ECCC-06 **Partners:** VaultMesh (IE), Univ Brno (CZ), Cyber Trust (GR), France Public Services (FR) **What it shows:** - Classical cryptography layer (current: Ed25519, ECDSA, SHA3, AES) - Hybrid transition layer (TRL 4→6: dual signatures, hybrid KEMs) - Post-quantum target state (CRYSTALS-Kyber, Dilithium, SPHINCS+) - VaultMesh organ integration (Receipts, LAWCHAIN, Treasury, Federation, Ψ-Field) - Work package flow (WP1-5) - Validation pilots (France, Czech, Greece) - Standards contributions (ETSI/IETF/ISO) **Key migration path:** ``` Ed25519 → Dual Signature → CRYSTALS-Dilithium ECDSA → Hybrid KEM → CRYSTALS-Kyber SHA3 → (already quantum-safe) → SPHINCS+ ``` **View:** ```bash cat ~/vaultmesh-core/funding-roadmap/diagrams/pqc-integration-architecture.mmd ``` **Render online:** - Copy content and paste into [Mermaid Live Editor](https://mermaid.live/) - Or use Mermaid plugin in VS Code/Obsidian --- ### 2. Digital Twins — Three-Pillar Sovereign Architecture **File:** `digital-twins-three-pillar.mmd` **Proposal:** €10M HORIZON-CL4-2025-DIGITAL-03 **Partners:** VaultMesh (IE), Fraunhofer AISEC (DE), Siemens (DE), TU Munich (DE), Charité Berlin (DE), Barcelona (ES) **What it shows:** - **Pillar 1: Urban Digital Twins** (Barcelona pilot — smart mobility + energy) - **Pillar 2: Biomedical Digital Twins** (Charité pilot — diabetes optimization) - **Pillar 3: Industrial Digital Twins** (Siemens pilot — smart factory) - VaultMesh core infrastructure (LAWCHAIN, Ψ-Field, Federation, Receipts, Treasury) - Cross-pillar coordination layer (interoperability, governance, standards) - EU policy alignment (AI Act, DORA, NIS2, Gaia-X) **Key innovation:** - Ψ-Field provides **collective intelligence** across all three pillars - Single LAWCHAIN for multi-domain audit trail - Sovereign federation allows city-to-city, hospital-to-hospital, factory-to-factory exchange **Pilots:** - 🏙️ Barcelona: 30% energy reduction target - 🏥 Charité: 20% patient outcome improvement - 🏭 Siemens: 15% throughput increase **View:** ```bash cat ~/vaultmesh-core/funding-roadmap/diagrams/digital-twins-three-pillar.mmd ``` --- ### 3. GenAI Health — Federated Learning + Governance Flow **File:** `genai-health-federated-governance.mmd` **Proposal:** €3M HORIZON-HLTH-2025-CARE-01 **Partners:** VaultMesh (IE), DFKI (DE), UMC Utrecht (NL), Philips Healthcare (NL) **What it shows:** - Federated data sources (hospitals A/B/C + clinics across EU) - Privacy & anonymization layer (differential privacy, homomorphic encryption, GDPR consent) - Federated ML (local training, secure aggregation, global model) - AI Act governance (Ψ-Field oversight, ethics board, human-in-the-loop, explainability) - VaultMesh proof infrastructure (receipts, LAWCHAIN, federation, treasury) - Clinical deployment pipeline (validation, regulatory, EHR integration) - EU policy compliance (AI Act Art. 10/14, GDPR Art. 9, MDR, EHDS) **Key innovation:** - **No raw health data leaves hospitals** (federated learning) - **Every training round = cryptographic receipt** (LAWCHAIN audit trail) - **Ψ-Field detects model drift & bias** (collective sensing across sites) - **Human-in-the-loop for high-risk decisions** (AI Act Art. 14 compliance) **KPIs:** - 20% diagnostic accuracy improvement - 30% reduction in data collection time - 5+ hospital network (cross-border) - 0 privacy breaches (differential privacy guarantees) - 10+ publications (top-tier medical AI venues) **View:** ```bash cat ~/vaultmesh-core/funding-roadmap/diagrams/genai-health-federated-governance.mmd ``` --- ## Rendering Options ### Option 1: Online (Mermaid Live Editor) 1. Copy diagram content: ```bash cat pqc-integration-architecture.mmd | pbcopy # macOS # or cat pqc-integration-architecture.mmd | xclip -selection clipboard # Linux ``` 2. Open https://mermaid.live/ 3. Paste content into left pane 4. View rendered diagram in right pane 5. Export as PNG/SVG if needed ### Option 2: VS Code Extension 1. Install extension: `bierner.markdown-mermaid` 2. Open `.mmd` file in VS Code 3. Click preview icon or `Cmd+K V` (macOS) / `Ctrl+K V` (Linux) ### Option 3: Obsidian 1. Copy `.mmd` content into Obsidian note: ````markdown ```mermaid [paste diagram here] ``` ```` 2. Diagram renders automatically in preview mode ### Option 4: Command Line (mermaid-cli) ```bash # Install mermaid-cli npm install -g @mermaid-js/mermaid-cli # Render to PNG mmdc -i pqc-integration-architecture.mmd -o pqc-integration.png -w 3000 # Render to SVG mmdc -i digital-twins-three-pillar.mmd -o digital-twins.svg # Render to PDF mmdc -i genai-health-federated-governance.mmd -o genai-health.pdf ``` ### Option 5: GitHub/GitLab - Push `.mmd` files to GitHub/GitLab repository - Both platforms auto-render Mermaid diagrams in markdown preview - Example: Embed in proposal docs with: ````markdown ```mermaid graph TB ... ``` ```` --- ## Diagram Styling Legend ### Color Coding **PQC Integration Diagram:** - 🔵 **Blue** — Classical cryptography layer - 🟡 **Yellow** — Hybrid transition layer (TRL 4→6) - 🟢 **Green** — Post-quantum target state - 🟣 **Purple** — VaultMesh core organs - 🟠 **Orange** — Work packages - 🔴 **Red** — Validation pilots **Digital Twins Diagram:** - 🟣 **Purple** — VaultMesh core infrastructure - 🔵 **Blue** — Urban pillar - 🟢 **Green** — Biomedical pillar - 🟠 **Orange** — Industrial pillar - 🟡 **Yellow** — Cross-pillar coordination - 🟣 **Lavender** — EU policy alignment - 🔴 **Red** — Pilot deployments **GenAI Health Diagram:** - 🔵 **Blue** — Federated data sources - 🟣 **Purple** — Privacy layer - 🟢 **Green** — Federated ML - 🟡 **Yellow** — AI Act governance - 🟠 **Orange** — VaultMesh infrastructure - 🟢 **Teal** — Clinical deployment - 🟣 **Lavender** — EU policy - 🟠 **Peach** — Expected outcomes ### Line Types - **Solid arrows (→)** — Primary data/control flow - **Dashed arrows (-.->)** — Feedback loops, secondary relationships - **Bold arrows (==>)** — Critical migration paths or high-priority flows --- ## Use Cases ### For Partner Onboarding - Include diagram in Partner Onboarding Kit (1-pager supplement) - Shows partner where their organization fits in architecture - Visualizes WP dependencies and deliverable flow ### For Proposal Part B - Embed in Section 1 (Excellence) to illustrate technical approach - Reference in Section 3 (Implementation) for WP structure - Useful for reviewers to grasp complex multi-partner architecture quickly ### For Steering Committee Reviews - Present diagrams in consortium kickoff workshops - Use to align partners on technical vision - Update diagrams as architecture evolves during proposal development ### For Standards Contributions - Submit to ETSI/IETF/ISO working groups as architectural reference - Shows how VaultMesh aligns with emerging standards (PQC, digital twins, AI governance) ### For Pilot Planning - Share with pilot sites to explain integration points - Identifies data flows, security boundaries, compliance checkpoints --- ## Maintenance ### Version Control ```bash cd ~/vaultmesh-core git add funding-roadmap/diagrams/ git commit -m "diagrams: update [PQC|Digital Twins|GenAI] architecture v1.X" git tag -a diagrams-v1.X -m "Architecture diagrams v1.X" ``` ### Update Workflow 1. **When consortium changes:** Update partner boxes and WP assignments 2. **When budget finalizes:** Update budget figures in annotations 3. **When pilots confirm:** Add specific pilot details (sites, metrics) 4. **When policy updates:** Add new compliance references (e.g., AI Act amendments) ### Receipt Generation ```bash python3 << 'EOF' import json, hashlib, datetime from pathlib import Path diagrams_dir = Path.home() / 'vaultmesh-core/funding-roadmap/diagrams' for diagram_file in diagrams_dir.glob('*.mmd'): content = diagram_file.read_text() hash_val = hashlib.sha256(content.encode()).hexdigest() receipt = { "kind": "funding.diagram.update", "ts": datetime.datetime.now(datetime.timezone.utc).isoformat(), "file": str(diagram_file), "hash": hash_val, "description": f"Architecture diagram: {diagram_file.stem}" } receipt_path = Path.home() / '.vaultmesh/receipts' / f'diagram-{diagram_file.stem}-{datetime.datetime.now().strftime("%Y%m%d%H%M%S")}.json' receipt_path.write_text(json.dumps(receipt, indent=2)) print(f"Receipt: {receipt_path.name}") EOF ``` --- ## Exporting for EU Submission ### High-Resolution PNGs ```bash # Export all diagrams at 3000px width (suitable for A4 print) for file in *.mmd; do mmdc -i "$file" -o "${file%.mmd}.png" -w 3000 -b transparent done ``` ### SVGs for Vector Quality ```bash # Export as SVG (infinitely scalable) for file in *.mmd; do mmdc -i "$file" -o "${file%.mmd}.svg" done ``` ### Embed in LaTeX Proposal ```latex \begin{figure}[h] \centering \includegraphics[width=\textwidth]{diagrams/pqc-integration.pdf} \caption{VaultMesh PQC Integration — Hybrid Cryptographic Architecture} \label{fig:pqc-arch} \end{figure} ``` --- ## Statistics **Total Diagrams:** 4 **Total Nodes (approx):** 220+ across all diagrams **Total Relationships:** 300+ edges showing data flows, dependencies, compliance links **Coverage:** - **8 EU funding proposals** (4 visualized: 3 detailed + 1 meta-synthesis, 4 referenced in nebula map) - **20+ consortium partners** mapped across all tiers - **25+ work packages** illustrated - **12+ validation pilots** detailed - **15+ EU policies/standards** linked (AI Act, DORA, NIS2, Gaia-X, EHDS, etc.) - **€15.8M+ total budget** orchestrated and visualized **Diagram Hierarchy:** - **Level 0 (Meta):** Treasury Nebula Map — orchestration overview - **Level 1 (Detail):** PQC Integration, Digital Twins, GenAI Health — technical deep dives - **Level 2 (Referenced):** Quantum Comms, Incident Response, Cloud, Maritime, Grid — in nebula map --- ## Future Diagrams (Planned) **Quantum Communications (€1M)** — QKD protocol stack + VaultMesh integration **Incident Response (€1.5M)** — CSIRT workflow + LAWCHAIN audit trail **Cloud Sovereignty (€2M)** — Gaia-X federation + VaultMesh proof layer **Maritime Security (€1.2M)** — AIS tracking + cryptographic receipts **Smart Grid (€800K)** — Energy mesh + treasury subsystem --- **Document Control:** - Version: 1.0 - Created: 2025-11-06 - Last Updated: 2025-11-06 - Owner: VaultMesh Technologies B.V. - Contact: guardian@vaultmesh.org - Classification: Consortium Internal (Non-Public)