This portal maps the Proof-of-Control (PoC) Cryptographic Verification Standard across its constituent domains as a hypergraph: one Shared Domain Graph per PoC domain, all connected to the same Proof-of-Control construct, with the cross-domain intersections, conflicts, and convergence / divergence / emergence patterns made first-class.
The six Shared Domain Graphs
Each graph is a registry of domains (objects), morphisms (typed maps), hyperedges (multi-way relations), and emergent composites (pullbacks that crystallize in situ when a request is honored). Every graph terminates at the shared Proof-of-Control core through Stage-3 cryptographic verification.
Insurance is the adoption engine
Security and AI are now part of the underwriting of every industry, and insurers are bifurcating into those that exclude AI in the policy and those embracing it. The flagship of this bundle — a private, cryptographically-attributed incident-response fabric — is the acceleration path for the embracing side: honored response patterns and conformance tiers become an underwritable security posture priced on real evidence, not claim-based assurances.
What you can do here
- Hypergraph Map — navigate all six SDGs and their intersections.
- Standards Anchors — every named standard as a trackable, engageable entry point.
- Incident Fabric — run the private report → honor → emerge loop.
- Discovery — universal personalized notification, search & recommendation.
- PoC Standard (0.1.0) — read the PoC standard with the universal right to follow.
Modeling language
Collaboration runs on FINOS CALM (the Common Architecture Language Model), adopted as the shared modeling language and deeply integrated with Pathway encodings. A security vulnerability's identification and fix is encoded as a CALM flow over CALM nodes, relationships, and controls.
See the Finos Invitation tab — an open invitation to FINOS and Karl Moll, with a directory of CALM resources and how they relate to the PoC standard.
The hypergraph
Hover a node for its name. Click to open a detail card; use Expand for the full relational view.
Standards Anchor Registry
Each named standard, community, or protocol is a trademark-like unique proper name (tm:) — simultaneously a mark to track across every context and an authenticated entry point for engagement. The Gap Analysis finding for each (where it stops short of open verification) is shown; PoC cross-references rather than replaces them.
Private Incident-Response Fabric flagship
The flagship private security technique. A party seals a security incident privately, routes an in-network attributed report, and a member honors it — emerging a reusable, credited response pattern. No raw incident detail ever leaves the boundary. This is the fabric the AI-insurance industry needs.
Seal Incident
Cryptographically bounded private record, signed at the moment of action.
Private Report
In-network, attributed request. Only derived signal + the ask cross the boundary.
Honor Response
A trust member contributes a response pattern; containment is signed.
Emerge
An attributed response playbook + underwritable posture crystallize.
Personas: CISO / security team (files & honors), AI insurer / underwriter (prices posture), independent assessor (verifies Trust Keys offline). All demo incidents are synthetic.
Universal Discovery, Search & Notification
The user-portal anchor feature: personalized notification, search, recommendation, and discovery across every indexed context — SDG nodes, standards anchors, standard clauses, pathways, incidents, CALM artifacts. Pick a persona to personalize; the six Pathways discovery dimensions (symbolic, semantic, physical, contextual, temporal, lineage) drive relevance.
Results & recommendations
Notifications for this persona
Finos Invitation
An open invitation to FINOS and to Karl Moll, Technical Project Advocate, to co-develop CALM as the shared modeling language for a cross-industry Proof-of-Control hypergraph. This tab is a mini directory: what FINOS is building, how CALM works, and how it connects to the Proof-of-Control (PoC) Cryptographic Verification Standard.
Why FINOS & Karl Moll
Karl convenes the AIGF × CCC × CALM convergence — moving governance off whiteboards into machine-readable, validatable reference architectures with measurable controls. That is precisely the substrate this bundle needs from the evidence side: architectures that are auditable, and runtime proof that controls operated.
Governance, Controls & Architecture
Frames the problem we attack from the evidence side: reference architectures that make AI governance concrete, with controls you can measure — not just document.
CALM Hands-On Workshop (Architecture as Code)
OSFF London workshop on transitioning from static diagrams to live, machine-readable Architecture as Code — and how CALM integrates AIGF, CCC, and AI governance.
FINOS project directory
Four registered anchors in the Standards Anchor Registry — each an authenticated entry point and open door for engagement.
FINOS (Fintech Open Source Foundation)
Linux Foundation open-source foundation convening cross-industry collaboration for financial-services technology — including the AI Initiative where CALM, AIGF, and CCC converge.
CALM — Common Architecture Language Model
JSON meta-schema for Architecture as Code: nodes, relationships, controls, and flows. Adopted here as the shared modeling language, integrated with Pathway encodings and Trust Key deep links.
AIGF — AI Governance Framework
Catalog of AI risks and mitigations for financial services. Converges with CALM (reference architectures) and CCC (controls) into a governable-AI pipeline.
CCC — Common Cloud Controls
Technology-neutral control catalog for compliant cloud deployments. Maps to CALM controls and, in EXP-CALM-4, onto SDG hyperedges per PoC domain.
CALM learning path
Start here if CALM is new. These are the official Architecture as Code (AasC) community resources.
What is CALM?
Introduction to architecture-as-code: JSON-based, version-controlled, machine-readable models that bridge design intent and implementation.
Core Concepts
Nodes, relationships, interfaces, controls, standards, timelines, and metadata — the vocabulary this bundle uses in its incident-response fabric architecture.
Working with CALM
CLI, VS Code extension, CALM Hub, Studio, and validation server — tooling to generate, validate, and visualize architectures from code.
architecture-as-code (open source)
FINOS AasC repository: CALM specification, CLI, patterns, and community contributions. Where CALM evolves as a living standard.
How CALM relates to the PoC standard
The PoC standard defines Stage-3 cryptographic verification — evidence of what an agent actually did, checkable by any party. CALM does not replace that; it gives the architecture layer a machine-readable form that PoC evidence can attach to.
| CALM construct | What it declares | PoC / bundle counterpart |
|---|---|---|
| Node | An actor, system, or service in the architecture | SDG domain object (e.g. security:incident_seal) |
| Relationship | How nodes interact (interacts, connects, deployed-in, composed-of) | Morphisms and cross-domain intersections in the hypergraph |
| Control | What must hold; keyed to a requirement (tm: anchor) | Gap Analysis row + standard clause (std:) via right-to-follow crosswalk |
| Flow | Sequenced transitions over relationships | Pathway template + Trust Key deep link per transition |
| Pattern | Reusable, parameterized architecture fragment | Per-customer in-situ PoC instantiation (EXP-CALM-3) |
PoC Standard Reader
Read the Proof-of-Control Cryptographic Verification Standard with the universal right to follow — every clause links outward to implementation vectors (pathways, CALM flows, SDG nodes).
What good evidence is
Generated at action time, mathematically verifiable, exists before dispute, independent of vendor documentation — the properties CALM controls aim to operationalize.
FINOS anchors in the registry
Every FINOS project cited above is a tm: trademark-like anchor — trackable across every context and an authenticated entry point for engagement.
Private incident-response fabric
The flagship Security SDG technique, encoded as a CALM architecture + vulnerability lifecycle flow. Where insurers, enterprises, and assessors collaborate on attributed response.
CALM artifacts in this bundle
Concrete CALM v1.1 encodings shipped with the hypergraph — not slides, working models.
Incident Response Fabric
Actors (insured enterprise, CISO, insurer, assessor), systems (agent runtime, tool gateway, TEE), and the PoC evidence layer. Controls keyed to tm: anchors with SDG node refs.
Vulnerability Lifecycle
Identify → private report → remediate → evidence. Each transition cites a Hypergraph.* pathway, SDG nodes, standard clause, and Trust Key deep link.
CALM Experiments (full designs)
Pre-registered EXP-CALM-1..4 with methods, success criteria, and hypotheses H-HG-1..4. Designed for co-development with FINOS.
Open Invitation (full letter)
Formal invitation text: why FINOS, the CALM premise, proposed joint work, collaboration model, and insurance context.
Proposed joint work — CALM experiments
Four pre-registered experiments. Pick one to run first; we'll seal a reciprocal bundle to your channel.
Controls ↔ Gap-matrix crosswalk
Join every CALM control's requirement-url (tm: slug) to Gap Analysis rows and PoC standard clauses. Unmatched controls = machine-detectable gaps.
Flow ↔ PathwayRun binding
Execute the vulnerability-lifecycle flow as PathwayRuns; bind provenance into Trust Keys. CALM diagram and cryptographic evidence become two views of one artifact.
In-situ PoC as CALM pattern
"The process is the product": a customer's PoC standard instantiated from their threat vectors, emitted as a valid CALM pattern specialized to their profile.
AIGF / CCC ↔ SDG hyperedges
Map AIGF risks and CCC controls onto SDG hyperedges; emit a validating CALM reference-architecture fragment per PoC domain. Direct contribution to Karl's convergence.
Insurance & financial services
Security and AI are now part of underwriting in every industry. Insurers are bifurcating into AI-excluding and AI-embracing carriers. A CALM-expressed, PoC-evidenced incident-response fabric is the acceleration path for the embracing side — financial services AI is where FINOS's home turf meets PoC first.
AI-insurance acceleration path
How sealed incidents, honored response patterns, and conformance tiers become an underwritable posture priced on real evidence — not claim-based assurances.
Cross-domain intersection
Security × Provenance × Authorization: the hypergraph intersection where incident evidence meets underwriting. Explore on the Hypergraph Map.
Pathways & the Anchor Name Ledger
This bundle is authored by the open Pathways project. Pathway encodings are the runtime half of the CALM collaboration model; the Anchor Name Ledger makes every FINOS mention trackable.
Pathways project
Agentic orchestration encoded, provenanced, and exchanged as verifiable pathways — the evidence layer that proves CALM controls held at runtime.
Trackable mentions & engagement
Every tm: anchor citation (FINOS, CALM, Karl Moll's convergence) is recorded here so associations are deep-linkable and auditable.
Standards Anchor Registry (source)
Authoritative registry of tm: and std: anchors — FINOS entries include engagement URLs and PoC domain mappings.
Collaboration model
- Every FINOS mention is a registered
tm:anchor — trackable via the Anchor Name Ledger. - Karl Moll's engagement is recorded against
tm:finos-calm,tm:finos-aigf, andtm:finos-ccc. - Everything is offline-verifiable: verify a Trust Key on your own device; follow a deep link only if you want more.
- The powerful party does least — no platform login, no vendor archive required.
Channel: djat-poc-hypergraph-20260716 · Next step: open an experiment design above and tell us which to run first.