Forwardable architecture brief

Legal Evidence Architecture Brief

Problem

Content, revision history, signatures, custody logs and production identity often live in separate systems. Recipients must reconstruct their relationship.

Proposed architecture

Received item → living UDR with revision lineage → explicit declared custody events → final UDS with exact-state verification → BrowserCarrier for zero-install, offline-readable exchange.

What this can prove

• Whether the bytes being checked match the sealed state
• Whether a recorded signature validates against the supplied key
• What revision relationships and custody assertions the document contains

What this does not prove

• That a named person actually controlled a key
• That an external transfer physically occurred
• That evidence is relevant, complete or admissible
• That any court, agency or organization accepts UD

Security and privacy

Core verification is local. BrowserCarrier is script-free and makes no automatic network request. External trust and custody services are optional and independently represented.

Interoperability

UD does not require abandoning PDF. PDF remains a compatibility copy where an incumbent workflow requires it.

Known limitations

Structured legal identity and external custody orchestration remain extension/commensal work. No real court integration or admissibility evidence is claimed.