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.
You share
claim
Your choice, shown on this page only
Would leave at the next publish
1
record, with 63 field paths
The network
No registry yet
A release needs at least 3 accredited nodes
Releases imported
0
Nothing here has changed a grade
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. |
Only an admin can change this. It is saved with
PUT /v1/exchange.Publishing starts inside your network. Nothing connects into your network.What you would get back
COne environment of your own
The finding holds at your site, so it stays at grade C. Still missing: passed challenge tests, and replication in 2 independent environments.
CToo few to publish
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 = 3BA release, imported and checked
The 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–unknownOther nodes add replication, which means the same result in another environment. They never add truth. Grade B always needs an environment of your own, and the grade is set on your own data.
What would leave
auga exchange publish --dry-run --config exchange.yaml| Field | You hold | Leaves as | What happens |
|---|---|---|---|
| The dataset | acme_checkout | not sent | Removed. (subject) |
| The setup's hash | null | not sent | Removed. Only the class of the setup leaves. (subject) |
| The component behind a cause | acme_checkout | ec21f96a | Pseudonym made with your key. (names) |
| The finding's id | clm-a095e98354ac3a9f | fclm-011e32bd93272bab | A new id, and no link to earlier versions. (lineage) |
| Who issued it | local | node-6209a15ad65f | Derived from your node's key. (issuer) |
| A run | r1 | b1eec10d0b11 | Pseudonym. (ids) |
| An environment | acme_checkout:0 | a5bf8731750d | Pseudonym. (ids) |
| How many runs | 800 | 1e2 | A size range. With under 100 runs, the record is not published. (n) |
| The effect, low end | 0.328 | 0.32 | Rounded outward, so the range never looks more certain. (rounding) |
| The effect, high end | 0.492 | 0.5 | Rounded outward, so the range never looks more certain. (rounding) |
| The environment's class | unknown | prod | What you set under What you share. |
| The grade | C | C | The grade is computed again on the redacted record. Rounding can only lower it. |
| A method | pcmci+ | pcmci+ | Kept, because the grade rules use it. |
| A name of your own | acme.customer_vip_tier | 3f681946.customer_vip_tier | gap The attribute name leaves as written. Only the component is hidden, and the leak check lets it pass. |
From the record
clm-a095e98354ac3a9f in the test fixture.hashkindnodepackage_versionrecords[].assumptions[].evidencerecords[].assumptions[].kindrecords[].assumptions[].statusrecords[].claim_idrecords[].edge.fromrecords[].edge.kindrecords[].edge.torecords[].estimand.effect.hirecords[].estimand.effect.lorecords[].estimand.effect.pointrecords[].estimand.identification.basisrecords[].estimand.identification.statusrecords[].estimand.outcomerecords[].estimand.quantityrecords[].estimand.treatmentrecords[].evidence[].detail.bootstrap_freqrecords[].evidence[].detail.ci[]records[].evidence[].detail.effect_sizerecords[].evidence[].detail.environmentrecords[].evidence[].detail.independentrecords[].evidence[].detail.methodrecords[].evidence[].detail.n_bucketrecords[].evidence[].kindrecords[].evidence[].resultrecords[].evidence[].runrecords[].generator.grade_rulesrecords[].generator.namerecords[].generator.ontologyrecords[].generator.versionrecords[].grade.derived_byrecords[].grade.missing_for_next[]records[].grade.valuerecords[].hashrecords[].hypotheses[].kindrecords[].hypotheses[].statusrecords[].issuer.noderecords[].kindrecords[].privacy.dprecords[].privacy.krecords[].privacy.n_bucketrecords[].privacy.profilerecords[].privacy.redactions[]records[].record_versionrecords[].subject.env_classrecords[].subject.setup_class.frameworkrecords[].subject.setup_class.modelrecords[].temporal.lags[]records[].temporal.tzrecords[].temporal.windowrecords[].unit.grainrecords[].unit.kindrecords[].variables[].conceptrecords[].variables[].manipulablerecords[].variables[].namerecords[].variables[].sourcerecords[].variables[].typesetup_class.frameworksetup_class.modelweekCurrent 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.