One protocol.
Distinct applications.

The story doesn’t end
with the camera.

Our primary journalism application consumes the Capture Evidence Profile: captured originals, capture metadata and context, original–derivative relationships and capture sessions. It uses the shared archive engine to protect, publish and recover the original bytes.

A seized camera, a wiped memory card or a newsroom forced offline makes the purpose concrete. Recovery still needs published records, accessible history and the separately preserved compartment root. Authenticated bytes do not prove that the scene or its contextual claims were genuine.

Android has scoped implementation and recovery evidence. The complete Capture Evidence schema and product acceptance remain work; emergency capture is design-only.

Files and collections.
Original bytes.

Archive consumes the Private Files Profile for generic documents, filenames, paths, MIME/type metadata, directories and collections. An image is an ordinary file here; journalistic capture semantics belong to Capture Evidence.

Capture and Archive share one engine for encryption, canonical fragmentation, publication, recovery and optional repair. Separate products do not require separate installables immediately. Existing byte recovery does not establish complete catalog/profile interoperability.

Publish words.
Verify locally.

Wire consumes URMA’s fixed public post, reply, identity-profile and constrained avatar records. Its local index verifies records, tracks confirmed history and rolls back orphaned state. Rendering and external-image handling belong to the application.

Linked media stays external and mutable. Wire has no private-text mode and no separate protocol or Index product. Each chain/network has its own feed and identity history.

Current committed state.
Independent recovery.

URMA Git has an approved public HEAD-only design: the current commit and its complete final tree, without repository history. Recovery starts from a chain-scoped root transaction and creates a normal editable repository. The profile and CLI remain implementation work.

Generic multipart transport belongs to URMA. Git supplies the native PACK, descriptor, content review and safe checkout rules. It is a separate funding scope; a raw uploader, gallery or public index is not part of this delivery.

Fund the foundation.
Fund an application.

Protocol work covers the specification, implementation, vectors, independent recovery and review. Shared services and interoperable profiles have reusable deliverables funded once. Capture, Archive, Wire and Git each have their own application scope and acceptance criteria.

URMA Camera is optional hardware running Capture, funded separately. The current working budget covers protocol, Capture and hardware; it does not fund every application. No award or release is implied.