Propagation Pilot – Progress & Change Across Organisations
A working demonstration of the Inontime Protocol: governed progress and change events are created in Organisation A, hashed, wrapped in propagation envelopes, and verified and replayed in Organisation B.
Capture governed progress and change data (scope, % complete, baseline, timestamps, change descriptions, impacts).
The app generates canonical JSON + SHA-256 hash for each governed event.
Org B verifies the hash, replays the event in its own workspace, and can respond or accept based on its own baselines.
Post Pilot stage, the propagation will be opened to the multi organisational environment during the Inontime protocol development.
LIVE DEMO (SLICE ONE) – PROPAGATION
What this demo shows (Situation + Task)
This demo shows a thin vertical of the Inontime Protocol: one governed change event created in Organisation A, propagated and independently verified in Organisation B, with both sides ending up on the same story.
You start in Organisation A’s workspace.
A governed change or progress event is created with clear metadata: who raised it, what work package it affects, and the intended impact on scope, time and value.
The event is canonicalised and hashed.
The same JSON representation is created every time, and a cryptographic hash is generated. Any tampering or re-editing would change the hash.
A propagation envelope is sent to Organisation B.
Org B doesn’t see Org A’s system, it just receives the governed event + hash, in a protocol envelope it can trust but still verify.
Organisation B independently verifies and replays the event.
Org B checks that the hash matches the payload it received, then replays the governed event into its own workspace, updating its view of the work package and baseline.
What you get from this slice (Action + Result)
Slice One is not a full project control system; it’s a working proof that governed events can move between organisations as verifiable objects, without shared logins or exported spreadsheets. Both sides end up with matching, tamper-evident records of the same change, ready to drive baseline versions, valuations and funding signals in later slices of the protocol.
This is the core invention: truthful propagation of governed delivery events across organisational boundaries. Everything else in Inontime – baselines, funding assurance, and the delivery-identity graph – is built on top of this behaviour.
How to Use the Pilot
Follow these steps to explore how the protocol pilot works.
1. Go to the pilot demo
Open the pilot demo using the button.
2. Log in as Org A
Use demo credentials to log in as Organisation A.
3. Create a progress event
Create a governed progress event and review the canonical payload + hash.
4. Create a change event
Create a governed change event (e.g., early warning or change event) and review the canonical payload + hash.
5. Switch to Org B & verify
Switch to Organisation B and verify the hashes for incoming events.
6. Replay events in Org B
Replay the propagated events in Org B’s own workspace and baseline.
7. Same hash across orgs
Observe that the same governed event yields the same hash across organisations.
8. Independent baselines
Each organisation maintains its own baselines and records without sharing systems.
Open the live propagation pilot
Use this environment to explore how governed progress and change events propagate across organisations using the protocol. For real pilots on live projects, please contact us.
