Request & assign
Name the work, the responsible provider, permitted inputs, expected result and acceptance criteria.
WORK TOGETHER. FOLLOW THE WORK. SHARE THE VALUE.
Your work.
Connected edges.
A shared account.
Send a request. Track who is doing the work. Receive the result and record its acceptance. Each member keeps its own data; the shared account makes contributions, costs and future shares checkable.
Consortium proposal · Interactive examples · 17 October 2026
WORK BETWEEN MEMBERSBefore customers
01 / YOUR ORGANISATIONYour edgeRequests, records & originals
02 / OTHER MEMBERSTheir edgeExecution, results & originals
↔ Requests, permitted data, results & receipts
↓ 32-byte commitments through the existing edge ↓
↑ Check the evidence behind each accounting item
03 / TOGETHERWork → result → acceptance → period accountShared rules. Separate custody. Human oversight.
01 / THE SIMPLE IDEA
First the work.
Then the shared account.
A shared work reference connects the request, responsible member, result and acceptance. Triple entry then connects that work to the records each organisation already keeps.
Execute & return
The member’s application performs the job. Its edge records progress and shares the permitted result with the intended recipient.
Check & accept
The authorised party checks the result against the criteria. Delivery, acceptance and final rail confirmation remain separately visible.
Close & allocate
Include accepted contributions in the agreed period. Carry pending items forward, calculate shares and net eligible obligations; payment is a separate step.
FOLLOW THE WORK / BEFORE THE ACCOUNT
Who is doing what?
What happens next?
Use the existing business host to connect the work, owner, source observations and review. Applications execute the work; edges retain records and exchange permitted data. This public view shows progress without issuing commands.
Business data between edges
Requests, agreed inputs, results and receipts use the separate authorised sharing path. Each organisation keeps its originals and controls access.
Commitments to the rail
The existing sender submits 32-byte commitments. Confirmations return to the same work records. The rail does not transport application inputs or execute the job.
Loading the dated LAB work observation…
NEXT WITH RESULT & VILLANOVA AI
One request. One result.
Two connected organisations.
A proposed first rehearsal: Result supplies a small synthetic input; Villanova AI runs one agreed service and returns its output; Result checks it against the agreed criteria. The same work reference follows both sides.
PARTNER CONNECTIONS PENDING
- Result → Villanova: request, permitted input reference and expected result.
- Villanova → Result: receipt, progress and result reference.
- Result → shared work: acceptance or a request for correction.
- Both → period account: their accepted contributions and costs.
Proposed roles, not a partner run. First agree one callable service and its input/output; install and verify each organisation’s edge. This page does not launch an AI service or grant permissions.
First shared job: what each member connects ↗Execution reference above comes from the existing Katalis/OpenNebula FED8RA LAB. It demonstrates reusable process tracking; it is not a Result or Villanova deployment. The separate Chamber qualification remains under Verified process.
02 / TRY THE BUSINESS MODEL
One period.
Every share explained.
Three illustrative contributors make the arithmetic easy to follow. Change a contribution or hold an item for acceptance and see the account change.
SYNTHETIC EXAMPLE Names indicate candidate participants, not agreed roles, prices, approval or installed edges.
Period selection changes the synthetic workload, not a real accounting schedule. Members will agree the actual cadence.
| Contributor / example work | Accepted effort points | Example cost | Acceptance | Cost recovery | Revenue remainder share | Trace |
|---|
The example rule, in plain language
Recover accepted costs first from the hypothetical revenue available. If revenue is insufficient, recover costs proportionally. Divide any remainder by accepted effort points. Pending items earn no allocation yet; they stay visible for a later period. With no accepted points, the remainder stays unallocated.
This formula is an editable business proposal for discussion, not an adopted Ambiti8n SLA or a claim that costs are payable. Points are illustrative, not currency.A SEPARATE EXAMPLE / MUTUAL OBLIGATIONS
Three obligations.
One net transfer.
Netting reduces the amount to move while preserving each member’s net position. These assumed obligations are separate from the contribution example above.
Requires agreed netting scope, eligible obligations and authority. It does not execute a payment.
03 / WHY TRIPLE ENTRY MATTERS
“Where did that number come from?”
Follow it all the way back.
An amount should lead to its accepted contribution, the owner’s small book, its returned rail proof and the original held by the owner.
Period amount→Accepted contribution→Owner book→Returned proof→Original & hash check
Originals stay with the organisation
The shared rail carries the existing 32-byte commitments, with protocol and proof overhead. Business documents and private keys stay off the rail. Relevant originals can be supplied through the authorised evidence process.
Proof and acceptance answer different questions
A proof establishes inclusion and integrity. An authorised acceptance and the agreed SLA determine how the item is treated in the account. A hash match alone does not establish service quality or a right to payment.
THE EXISTING PROCESS, CONNECTED
Your books.
A checkable shared record.
Normal work stays in the members’ books. When an item needs review, the existing Chamber procedure connects the originals, the shared evidence and the returned decision.
Keep the originals
Each party keeps its records and sends commitments through its existing edge.
Confirm the record
Final confirmation returns after the normal sealing period. Book time and finality time remain separate.
Check both sides
Request the relevant originals. Check the owner’s evidence against the Chamber’s independently maintained small book.
Book the decision
The authorised decision follows the same edge and rail path. Each party can verify it independently.
DATED LABORATORY EVIDENCE
One process. Two pilot contexts.
Three operator-owned LAB edges: two parties and the Chamber. The existing test compares a delivery of 100 units with a receipt of 80. Ambiti8n 5 runs first; the FED8RA example follows only after it passes.
Loading the last published observation. An unavailable result is not a successful test.
The LAB reviewer is scripted and signs only a test decision. This is not a partner’s human approval, a payable award or a live allocation. Partner installations remain pending. Published results are dated observations, not a continuous health monitor.
What was checked, and what remains to connect ↗04 / A PLACE FOR EVERY MEMBER
One framework.
Many contributions.
Software, infrastructure, integration, models, messaging and evidence can use the same accounting framework. Each member retains its own systems.
Proposed roster based on the supplied meeting and planning material. Connection and agreed contribution are pending for every named partner on this portal. ENEA, arsys and Lab8ra also appear in the planning material; their roles remain to be agreed.
05 / START WITH THE RULES WE HAVE
NEO Chamber today.
Ambiti8n rules, together.
Use the published NEO Chamber rules as the starting reference. Members can develop their shared Ambiti8n rules and SLA as the work becomes concrete.
Read NEO Chamber rules v0.1 ↗AVAILABLE
NEO Chamber rules
Existing governance and evidence procedure. Reading this page is not membership or acceptance of the rules.
TO AGREE
Ambiti8n Chamber & shared SLA
A proposed branch of the existing Chamber: members agree contribution measures, cost treatment, revenue allocation and period cadence. Record the version each party accepts.
What if members disagree?
Keep the disputed item identifiable and use the existing Chamber process: request relevant originals, verify their hashes, apply the existing service and deadline rules, and obtain the authorised human decision. The rest of the account follows the agreed treatment of open items.
06 / YOUR FIRST USEFUL STEP
Connect one organisation.
Prove one record.
Start with the current Studio installer and your own assigned connection. Then choose one contribution from your real work.
YOUR EDGE WORKSPACE / TRU STUDIO 0.3.6
Download your edge workspace.
Choose your computer. TRU Studio is the desktop workspace for your organisation’s records and its assigned NEO edge.
Windows
Windows 10/11, 64-bit; native startup checked on the Windows CI runner
Mac · Apple Silicon
Apple Silicon (M1 or later), macOS 11+ build target; tested on macOS 15
Mac · Intel
Intel x64, macOS 11+ build target; tested on macOS 15
Linux
Ubuntu 22.04 x64 tested; DEB or AppImage
Pilot preview · unsigned installers; macOS uses an ad-hoc signature. Release details & SHA-256 checksums · Installation guide. Your organisation’s identity and connection settings are supplied separately. No AI key is needed for the first evidence test.
You bring: a technical contact, your computer type and one process.We coordinate: identity mapping, private connection settings and the first proof check.
What is available — and what comes next
Available now
This process view, a dated real LAB execution, the account exercise, current Studio downloads and published NEO Chamber rules.
Next with members
Individual onboarding, a request and returned result between partner edges, authorised acceptance and a joint period rehearsal.
Still to agree
Shared SLA, adopted allocation formula, Ambiti8n branch rules and any commercial or payment arrangements.
The account calculator remains illustrative. The separate process panel reports dated evidence from the live-rail LAB qualification. Earlier Ambiti8n 4 and Pilot 3 remain separate. Realistic application scenarios follow verified partner connections.