Synthetic source profiles
A text export, SMS JSON and platform-neutral collaboration JSON.
2dA BronVast Messages Lab
Three source packages. One possible relationship. Every step traceable.
This demonstration uses only people, messages, numbers, events and source profiles invented by 2dA. It demonstrates a processing method, not compatibility with an existing application, supplier or customer environment.
Messages
Messages and events
Every timeline entry retains a reproducible source locator.
Open human reviews
No derived proposal is silently presented as a decision.
From source package to accountable destination
Source
unchanged synthetic files
Manifest
six files with SHA-512
Model
three conversations and twelve messages
Reconstruction
timeline across three source packages
Review
context, privacy, hold and exception
Block
zero automatic legal decisions
Explore the evidence chain yourself
Every item below is synthetic. Filter the reconstruction and inspect how source observations, reproducible derivations, proposals, reviews and holds remain separate.
Source message
Maya Vermeer
Can the revised decision note be added to Meridian today?
sms-json · message 0041Reply and attachment
Jonas Smit
Yes. I have added decision-note-v3.pdf to the shared review.
collaboration-json · event 018Derived relationship
BronVast
The reply reference and file name link this event to message 0041.
rule relation-v2 · confidence 0.98Context proposal
BronVast
Possible relationship with the fictional Project Meridian decision process.
model context-lab-1 · confidence 0.76Human review
Records specialist
Conversation relationship confirmed; process relationship remains open.
review BV-R-009 · reviewer role recordedDestruction blocked
Authorised reviewer
A synthetic investigation hold blocks destruction pending release.
hold BV-H-003 · activeEvidence Manifest sample
| Object | Status | Source locator | Integrity or method |
|---|---|---|---|
| MSG-0041 | observed | sms-json#message-0041 | SHA-512 manifest |
| EVT-0018 | observed | collaboration-json#event-018 | SHA-512 manifest |
| REL-0007 | derived | MSG-0041 ↔ EVT-0018 | relation-v2 |
| CTX-0003 | proposed | REL-0007 | context-lab-1 / 0.76 |
| REV-0009 | confirmed | CTX-0003 | human review |
| HLD-0003 | hold | conversation synthetic-02 | authorised block |
Fictional demonstration. No customer data, supplier export or third-party dataset is used.
Project Meridian
A shared reference and temporal proximity create a reproducible context proposal. They do not independently prove that all conversations belong to the same case.
- status remains proposal
- source locators remain available in the private proof
- an authorised reviewer must confirm the relationship
- rejection remains part of the log
An exception is not hidden
The proof deliberately includes one missing attachment. BronVast neither invents it nor counts it as present, but opens a review task.
- availability status per attachment
- hash only when the file exists
- exception in technical and human output
- next action without overwriting the source
Destruction remains blocked
The fictional proof lacks a valid selection basis and release of an active review hold. The route therefore cannot proceed to execution.
- no automatic grounds
- hold status visible
- human approval required
- zero automatic legal decisions
What your organisation receives
Source and derivation separated
Machine-readable objects with source locator, parser profile and status.
Relationships without false certainty
A timeline with messages, events, proposals, evidence and open questions.
Repeatably green
Sources byte-identical, counts correct, warnings present and the human gate enforced.
Reference points
These references show the professional basis for our choices. The requirements that apply in practice are determined with you from your situation, responsibilities and receiving environment.
Questions about this route
Are the displayed messages real?
No. All content is entirely fictional and was created by 2dA for this demonstration.
Does the Lab prove support for every chat application?
No. The Lab proves the processing and evidence architecture on synthetic profiles. Real source variants are tested separately.
Can a customer inspect the private source files?
2dA can explain the evidence route in an agreed demonstration. The public website does not publish internal source paths or private development files.
Next step
Start with evidence, not assumptions
A first engagement can be limited to one lawful source package, one process and one receiving profile.