The block remains visible
An active FOI, investigation, dispute or other recorded hold prevents execution until authorised release.
BronVast Messages | Destruction & transfer
Retain when required. Destroy when authorised. Prove what happened.
Removing a link, account or search result does not automatically destroy digital information. BronVast exposes scope, copies, indexes, derivatives, holds, authorisation, execution and evidence and prepares an appropriate transfer.
Messages
More than the user layer
The route includes agreed copies, indexes, derivatives and relevant backup mechanisms.
The receiving profile leads
Metadata, representations, manifest and validation align with the concrete DMS, RMA or e-depot environment.
From source package to accountable destination
Grounds
approved framework and authority
Scope
objects, relationships, copies and derivatives
Blocks
holds, exceptions and open reviews
Authorisation
separation of duties and dual control
Execution
destroy or assemble package
Evidence
record outcome, failures and acceptance
Destruction as an accountable process
Digital information is destroyed only when made permanently inaccessible within the approved scope. Failures and remaining copies must remain visible.
- formal decision and authorised approval
- technical execution per system or storage layer
- exceptions and non-executable objects
- second-person verification
- agreed evidence metadata after execution
MDTO-directed is not automatically MDTO-conformant
BronVast can direct metadata and a transfer package towards MDTO and a SIP structure. Conformance follows only after validation against the agreed specification and acceptance by the receiving environment.
- machine-readable representation
- human-readable access view
- manifest, provenance and validation report
- open exceptions
- acceptance result and receiving-profile version
Sustainable accessibility after transfer
A package must remain findable, available, readable, interpretable, reliable and future-proof within its selected management route.
- relationship between source and access representation
- format and integrity information
- rights and access restrictions
- preservation events and future migrations
What your organisation receives
Decision and execution together
Scope, authority, blocks, actions, failures, verification and evidence metadata.
Validate before production
Representations, metadata, manifest and report against the agreed receiving profile.
No silent loss
Results, open exceptions, recovery route and formal acceptance by the destination.
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
Does BronVast delete messages automatically?
No. No destruction occurs without recorded grounds, scope, authorised approval and control.
Is a removed search result the same as destruction?
No. Underlying information, copies, indexes or derivatives may still exist. The approved scope must be executed demonstrably.
Does BronVast automatically deliver an MDTO-conformant SIP?
No. An MDTO-directed mapping and test package can be designed. Conformance requires validation against the agreed profile and receiving environment.
Next step
Start with evidence, not assumptions
A first engagement can be limited to one lawful source package, one process and one receiving profile.