Intelligence Exchange not connected
On this page you choose what your node shares with the Intelligence Exchange. A node is one participant in the Exchange. Nodes share what they learned, never the data they saw. Graded findings cross the boundary, and no row of data does. A meta-analysis works in the same way: it combines published results and never patient records.
What you share
| Record | What it says | Shared |
|---|---|---|
| claim | A graded finding: one thing causes another, how strongly, and how sure we are. | OffOn |
| graph | How the findings connect. | |
| method | How well a method performed, so that others can judge it. | |
| Environment | The environment class that your records report. |
PUT /v1/exchange.Publishing starts inside your network. Nothing connects into your network.What you would get back
The finding holds at your site, so it stays at grade C. Still missing: passed challenge tests, and replication in 2 independent environments.
Fewer than 3 accredited nodes report this setup class, so the release contains 0 records. The rule protects the identity of the organisation that sent a record.
suppressed sha256:46479acd47b6… from node-22429ae5d532: its setup class has fewer than 3 nodessuppressed sha256:1f6c2d4e401f… from node-8d291a2a07e6: its setup class has fewer than 3 nodesrelease 2026-11: 0 record(s) from 2 node(s), k = 3The signed release contains 4 records. Your node verifies the signature and every record, imports 3, and refuses 1, which is its own record. The 3 others count as half an environment each, so the finding reaches grade B.
release 2026-11: 4 record(s) from 4 node(s), k = 3import: 3 imported, 1 refused (own record)grade: C + refutations + replicated here and by 3 accredited node(s), unknown–unknownWhat would leave
auga exchange publish --dry-run --config exchange.yamlNothing leaves. The test publish sends no record, and it says why:
clm-a095e98354ac3a9f: claim records are not shared (exchange.yaml)
Current progress
| Part | Now | |
|---|---|---|
| Records, redaction and the leak check | Built and tested, 15 tests pass | built |
| Publish, registry build, import, replication | Built as commands: auga exchange, auga registry | built |
| What a tenant may share | The route exists. This page is the first screen for it. | route only |
| Attribute names of the customer organisation in a record | The names are shared exactly as written. This breaks the rule that the ontology is the only source of words in a record. | gap |
| A running registry and a first release | We did not find it in the repository's deployment. The demo describes a release as built by hand. | missing |
| Three accredited nodes | None yet, as far as the repository shows | missing |
The rules
| What is shared | Only exchange evidence records are shared. No rows, no runs, no prompts and no organisation names are shared. |
| Who takes part | A node runs a signed Auga release or passes the conformance suite, has a submission accepted, and has its key registered. |
| Releases | There is one release a month, with a fixed time window and a signed file. Nodes with no network connection import it by hand. |
| Revocation | A node or record that proves wrong is listed publicly, and every importing node refuses it. |
| Reciprocity | A node that contributes gets the release when it comes out. Others may get it later or at a cost. |
| What a release never does | A release never sets a grade. Records that contradict a finding flag it, and they never lower its grade by themselves. |
| Handover | With enough independent nodes, the registry and the charter move to a neutral organisation. |
This page is a prototype. Records and results on this page are real output of the engine's exchange code, run on test fixtures. The On and Off controls save nothing. No registry is running.