Shared rules.
Independent applications.

Write. Verify.
Recover.

Private objects preserve arbitrary original bytes through authenticated encrypted chunks. Wire text records stay atomic. Generic public objects use a bounded root, leaves and data parts, with one Taproot reveal per record. The protocol owns canonical serialization, fragmentation, cryptography, proof validation and exact reconstruction.

Applications depend on the URMA implementation. The protocol does not depend on a product, camera, wallet, local index or implementation database.

One archive engine.
Separate meanings.

Shared services handle publication plans, funding interfaces, sources, recovery, exports and optional repair. Capture Evidence describes originals, context, derivatives and sessions. Private Files describes files, names, paths, directories and collections.

Profiles are interoperable contracts above URMA, non-normative for protocol conformance. Exact schemas and independent profile vectors remain release work. A collection or session manifest is different from a repair manifest and from the publisher’s operational journal.

A complete original can remain recoverable while its contextual metadata is missing. Missing canonical chunks mean an incomplete object. Optional repair can supply reconstructed candidates only if they pass ordinary protocol validation.

Choose the workflow.
Keep the protocol.

Capture brings the first journalism workflow; Archive handles generic private collections. Wire publishes and reads public text, identities and replies with local indexing. Git has an approved public HEAD-only design; its application remains to be implemented. Each application has a separate contract and funding scope.

Optional Camera hardware runs Capture. Independent recovery does not require that hardware or the original application. Record availability, source trust and surviving secrets remain explicit dependencies.