Provenance and integrity first
Source files remain unchanged. Manifests, hashes, source locators and exceptions keep every processing step traceable.
2dA BronVast Messages
From scattered messages to accountable public information
Business communication lives in chat applications, SMS, collaboration environments and exports. BronVast Messages starts with a lawfully obtained source package and builds the information chain around it: integrity, relationships, context, human review, appraisal, access, destruction and transfer.
Messages
No isolated lines without relationships
Participants, time, replies, events, attachments and possible process context are connected where the source responsibly supports it.
A proposal is not a decision
AI and rules can prepare work. Authorised people decide meaning, access, appraisal, holds, destruction and transfer.
From source package to accountable destination
Source package
lawful export or agreed capture output
Evidence layer
manifest, SHA-512, parser log and exceptions
Reconstruction
conversations, participants, time and attachments
Context
process, case and description proposals
Human review
appraisal, access, holds and exceptions
Destination
retain, destroy or transfer under control
Capture is the start, not the archive
An export or capture can secure messages. Meaning, context, retention, access and transferability are not resolved automatically. This is where 2dA adds archival intelligence.
- technical profiling for each agreed export variant
- strict separation of source and derived values
- missing elements and assumptions reported explicitly
- no generic claim to support every application or version
Do not keep everything. Never destroy without grounds.
Digital communication may touch several processes, retention periods and exceptions. BronVast makes the decision route visible without replacing the authorised archivist, lawyer, FOI specialist or records manager.
- selection framework and process context as inputs
- holds block destruction while their grounds remain
- separation of preparation, authorisation, execution and control
- agreed evidence metadata remains available
Local where the information requires it
Source files, indexes, embeddings and task models can remain within customer infrastructure or an agreed protected 2dA environment.
- role-based access and protected review
- logging and version control
- local search and proposal models
- architecture aligned with DPIA, security and the receiving environment
What your organisation receives
A facilitated baseline assessment
Source map, scope, authority, export profiles, risks, target architecture and a bounded pilot plan.
Demonstrate first on a limited scale
A lawfully obtained test set passes through manifest, reconstruction, context, review, exceptions and concept transfer.
Scale only after acceptance
Capacity, error handling, security, roles, monitoring and the receiving profile become measurable.
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
Can BronVast Messages read every chat application?
No. BronVast starts with a lawfully obtained export or agreed capture output. Each source variant is profiled and tested first.
Must all business messages be retained permanently?
No. Process context, applicable appraisal frameworks, retention periods, exceptions and holds determine the route. The authorised organisation decides.
Can processing remain fully local?
Yes, where the source, infrastructure and selected tools allow it. Security, privacy and operational controls are defined per engagement.
Next step
Start with evidence, not assumptions
A first engagement can be limited to one lawful source package, one process and one receiving profile.