Enter the access password to open the hypergraph portal, standard reader, and bundle explorer.
Channel djat-poc-hypergraph-20260716 · client-side access gate for review sessions
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.
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.
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.
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.
Hover a node for its name. Click to open a detail card; use Expand for the full relational view.
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.
The flagship private security technique. A party seals a security incident privately, routes an in-network attributed report, and a trust-network member honors it — emerging a reusable, credited response pattern. No raw incident detail ever leaves the boundary. Select a report, explore what crosses the privacy floor, and walk through honoring step by step.
Honoring is not disclosure and not triage on someone else’s logs. A trust-network member receives a PrivateReport packet — a small, privacy-bounded ask — and decides whether their own deployment has seen the same class of problem. If yes, they submit a signed response pattern from their own boundary (what worked in their environment). The fabric links the two via hash reference only; neither party ever sees the other’s raw detail.
Hypergraph.Incident.HonorResponse@v1.All demo incidents are synthetic. Personas: CISO / security team (files reports), trust-network contributor (honors), AI insurer (prices posture), independent assessor (verifies Trust Keys offline).
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.
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.
Formal invitation to FINOS and Karl Moll: Pathways technical intro, CALM×Pathways integration, four proposed experiments, collaboration model, and insurance context.
AIGF × CCC × CALM convergence is the FINOS-led work that Karl Moll (Technical Project Advocate) convenes to align three governable-AI layers into one pipeline.
The goal of the convergence is to move governance off whiteboards into machine-readable, validatable reference architectures with measurable controls. Proof-of-Control (this collaboration) adds the missing fourth layer: cryptographic evidence that those controls actually operated at runtime.
That convergence is the substrate this collaboration needs from the architecture side; Proof-of-Control supplies the evidence side: runtime cryptographic proof that controls actually operated, checkable by any party. CALM declares what must hold; PoC proves that it held.
Frames the problem we attack from the evidence side: reference architectures that make AI governance concrete, with controls you can measure — not just document.
OSFF London workshop on transitioning from static diagrams to live, machine-readable Architecture as Code — and how CALM integrates AIGF, CCC, and AI governance.
Four registered anchors in the Standards Anchor Registry — each an authenticated entry point and open door for engagement.
Linux Foundation open-source foundation convening cross-industry collaboration for financial-services technology — including the AI Initiative where CALM, AIGF, and CCC converge.
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.
Catalog of AI risks and mitigations for financial services. Converges with CALM (reference architectures) and CCC (controls) into a governable-AI pipeline.
Technology-neutral control catalog for compliant cloud deployments. Maps to CALM controls and, in EXP-CALM-4, onto SDG hyperedges per PoC domain.
Start here if CALM is new. These are the official Architecture as Code (AasC) community resources.
Introduction to architecture-as-code: JSON-based, version-controlled, machine-readable models that bridge design intent and implementation.
Nodes, relationships, interfaces, controls, standards, timelines, and metadata — the vocabulary this bundle uses in its incident-response fabric architecture.
CLI, VS Code extension, CALM Hub, Studio, and validation server — tooling to generate, validate, and visualize architectures from code.
FINOS AasC repository: CALM specification, CLI, patterns, and community contributions. Where CALM evolves as a living 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) |
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).
Generated at action time, mathematically verifiable, exists before dispute, independent of vendor documentation — the properties CALM controls aim to operationalize.
Every FINOS project cited above is a tm: trademark-like anchor — trackable across every context and an authenticated entry point for engagement.
The flagship Security SDG technique, encoded as a CALM architecture + vulnerability lifecycle flow. Where insurers, enterprises, and assessors collaborate on attributed response.
Concrete CALM v1.1 encodings shipped with the hypergraph — not slides, working models. Markdown docs open in a popup reader; JSON/YAML expand inline.
Actors, systems, PoC evidence layer. Controls keyed to tm: anchors with SDG node refs.
Identify → private report → remediate → evidence. Pathway, SDG, clause, and Trust Key refs per transition.
Pre-registered EXP-CALM-1..4 with methods, success criteria, and hypotheses H-HG-1..4.
Four pre-registered experiments. Pick one to run first; we'll seal a reciprocal bundle to your channel.
Join every CALM control's requirement-url to Gap Analysis rows and PoC clauses.
Execute the vulnerability-lifecycle flow as PathwayRuns bound into Trust Keys.
Customer PoC standard instantiated from threat vectors as a valid CALM pattern.
Map AIGF risks and CCC controls onto SDG hyperedges; CALM fragment per PoC domain.
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.
Sealed incidents, honored response patterns, and conformance tiers as underwritable posture.
Security × Provenance × Authorization: the hypergraph intersection where incident evidence meets underwriting. Explore on the Hypergraph Map.
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.
Agentic orchestration encoded, provenanced, and exchanged as verifiable pathways — the evidence layer that proves CALM controls held at runtime.
Every tm: anchor citation is recorded and deep-linkable.
Authoritative tm: and std: anchors with engagement URLs.
tm: anchor — trackable via the Anchor Name Ledger.tm:finos-calm, tm:finos-aigf, and tm:finos-ccc.Channel: djat-poc-hypergraph-20260716 · Next step: open an experiment design above and tell us which to run first.