Your originals stay yours.
Documents, source records, private keys and the material needed for later disclosure remain under the owner's control. Retention and access follow agreed rules.
AMBITI8N 4 · PILOT PROPOSAL
Your records.
Your contribution.
A shared ledger
for trust.
NEO governance: clear rules, verifiable contributions and human oversight.
Interactive proposal · Synthetic examples · 16 October 2026
Partner connections, signatures and payments are not executed on this page.
THE COLLABORATIONPROPOSED
Your bookOriginals stay here
Their booksSeparate custody
↓32-byte commitments↓
≋
One shared evidence railCommitments in. Verifiable confirmations back.
↑ Confirmations return to each owner
A case, when needed.
The Chamber requests selected originals from their owners and checks their proofs against the recorded commitments.
IDENTITY · SLA · GOVERNANCE · VALUE
01 Keep your data02 Prove your contribution03 Resolve a disagreement04 Account for your share
01 / THE NETWORK
Every organisation.
Its own edge. Its own book.
Start with an identified organisation and one useful process. A working connection to the whole Ambiti8n application is not a prerequisite for this proposal.
The 11 organisations in the supplied meeting minutes, plus Tiscali from the health architecture. Names identify proposed participants, not installed nodes or endorsements. All books below are illustrative.
Other organisations and roles shown on the planning board
ENEA, arsys and Lab8ra also appear in the supplied planning views. Their connection and contribution to this case are unspecified. They each have a proposed book below, without an invented allocation. Hospital 1/2/3 are deployment roles, not identified legal organisations. Other small logos cannot be assigned a reliable case role from the screenshots alone.
32 bytes per object.
The existing edge path submits commitments and retrieves proofs. Signatures, envelopes and receipts are separate overhead; whole business documents are not placed on the binary rail.
Disclose only what is requested.
Authorised references connect the parties' records to a case. The Chamber requests relevant originals; a hash by itself neither identifies the business subject nor reconstructs a lost document.
02 / ONE SHARED CASE
Same collaboration.
Three possible outcomes.
An illustrative service package for a hospital application. Result receives the package; the named contributors provide agreed services. The disputed item is Villanova AI's report service.
PROPOSAL CASEAMB4 / SERVICE-001
AGREED DELIVERABLEService package + report using model v2
ACCEPTANCE BASISRequired version, delivery record, recipient review
ILLUSTRATIVE GROSS POOL€1,000 · no payment
THE EXISTING CHAMBER PROCEDURE
- Identify & agreeMember, passport, wallet, subject and accepted rule version.
- Record & confirmEach party books its claim and obtains its rail proof.
- Accept or disputeThe counterparty responds in its own book.
- Request originalsProve service of the summons, then run the agreed deadline.
- Review & decideApply the accepted rule and authorised review tier.
- Record the outcomeA signed decision is a new record. Enforcement is separate.
This walkthrough changes explanatory examples only. It does not issue a summons, run a deadline, verify a signature, make a Chamber decision or submit a rail object. It defines no new Chamber deadline or tariff.
03 / CONTRIBUTION → VALUE
A visible contribution.
An accountable share.
Dynamic revenue sharing follows agreed terms and accepted contributions. Being in the network does not, by itself, earn a share.
CURRENT EXAMPLE
Example schedule only: fixed percentages of a hypothetical €1,000 gross pool. These are not partner-agreed prices or the live FED8RA allocation engine.
| Organisation | Proposed contribution | Agreed share* | Example amount | Current treatment |
|---|
*Assumed agreement for this example. A disputed or missing contribution keeps its amount separate; it is not silently redistributed. Acceptance, eligibility, clearing and payment are separate steps. No bank connection or payment is claimed.
Identity & wallet
Know which organisation acts, under which passport and mandate. The wallet connects the member to its business records; a displayed balance is not proof of bank settlement.
SLA & acceptance
Agree the deliverable, measurement authority and acceptance criteria before work starts. A provider's statement and a customer's acceptance remain distinct records.
Governance & disputes
Apply a known rule version. Request evidence, observe the existing deadline and record a reasoned outcome through the Chamber. AI assistance does not impersonate an authorised reviewer.
04 / WHEN AN AUDITOR ASKS
From a question
to checkable records.
Prepare selected evidence for an authorised auditor or regulator, while keeping custody with the organisation.
Supports evidence for AI Act and GDPR obligations where applicable. Compliance also depends on the organisation's role, lawful processing, appropriate retention, access controls and the completeness of its source records.
SELECTED CASE DOSSIEREXAMPLE
“Which model produced this report?”
- Identified organisation and authorised actor
- Original request, model/version reference and result
- Record-to-commitment proof and rail confirmation
- Acceptance, objection and any Chamber decision
- Explicit list of missing or unestablished facts
The original + its proof.
The owner supplies the requested material through an authorised route. Matching a hash checks integrity; it does not establish clinical accuracy, lawful processing or that every action was captured.
05 / BUILT ON EXISTING WORK
One continuing story.
Clear evidence boundaries.
Each edition has a different purpose. A new proposal does not change the participant count or the results of an earlier experiment.
Local books. Shared evidence.
9 synthetic domains, 77 local records, 11 rail-closed snapshots and one linked handover. Pilot 2 explains the same September run.
Pilot 1 evidence ↗Pilot 2 walkthrough ↗Reconstruct a shared case.
10 synthetic contributors across 3 first-seal packages. 8/8 saved scenario controls. Local proof checking and restore; no clinical deployment.
Original results ↗Technical scope ↗Make the collaboration clear.
Named organisations, separate books, a shared case, evidence requests and illustrative revenue allocation. Browser examples, not new measured rail results.
Explore the proposal ↑Exercise the actual workflow.
After the Villanova AI connection is verified, select scenarios from the consortium's health architecture and design realistic simulations with traceable execution evidence.
No model execution, partner connection or clinical validation is claimed here.
Existing components to reuse for implementation
Organisation identity, passports, wallets, CompanyActions/evidence, acceptance and dispute authorities, existing owner edge/outbox/native client, Chamber workflow and clearing. This proposal adds no ingestion service, central document archive or alternative rail sender. Actual partner activation and the complete case must be qualified separately.
06 / YOUR FIRST STEP
Bring one process.
Keep your originals.
Confirm the responsible operator, membership, passport, wallet and accepted rules.
Keep keys and originals under your control. Agree storage, retention and an authorised evidence route.
Choose a real process and map its records to a shared subject. Check the first commitment and returned proof.
Record a counterparty response, retrieve selected originals and qualify the existing Chamber process and contribution accounting.
Next milestone: connect Villanova AI, verify the integration, then define Ambiti8n 5 simulations together.
Discuss the pilot ↗