A blockchain shows a transaction, but not the full off-chain disclosure and decision process.
Connect the off-chain identity, document and approval history that a blockchain transaction alone does not explain.
An illustrative working process
From first contact to continuing responsibility.
01
Invite and review participantsEntity and participant checks with source references
Recorded context
02
Manage source disclosures and versionsCurrent disclosures, terms and linked translations
Recorded context
03
Collect required acknowledgementsQuestions, review findings and responses
Recorded context
04
Record human approvalsVersion-specific acknowledgements and signatures
Recorded context
05
Retain subsequent updates and requestsUpdates, renewed reviews and ongoing communications
Recorded context
OFF-CHAIN PREPARATION
The disclosure changes. Keep the response tied to it.
An on-chain event does not explain which disclosure a participant received beforehand. Keep the source version, questions and acknowledgement in the same preparation record.
Less fragmented off-chain information. A clearer account of what was shared and acknowledged.
Illustrative workflow. Scope and availability are agreed for the engagement.
THE WORKING RECORD / EXAMPLE
Disclosure set · Revision 4
Source
The current disclosure set and linked translations
Required response
The participant acknowledges the relevant version
Next owner
The issuer’s reviewer handles unresolved questions
What can go wrong
The transaction is only part of the story.
Illustrative off-chain workflow. Human reviewers remain responsible for participant and compliance decisions.
The on-chain event lacks its off-chain context.
A transfer alone does not show which disclosure or terms a participant received.
Connect the documents to the process.
Keep the source terms, exact disclosure version and participant response in the project record.
Terms change after invitations go out.
People may respond to a superseded disclosure while the project moves forward.
Request a version-specific response.
Identify the changed file and ask affected participants to review that version.
A screening question remains open.
A participant check raises an exception, but the next team sees only a status label.
Keep the review human and visible.
Record the source, finding, reviewer and decision before the relevant next step.
