DOCUMENTATION / AUTHORITY
Read the contract.
Inspect the evidence.
One normative protocol, separate interoperable profiles and application contracts, and evidence tied to actual implementations.
These paths are in the project checkout. A canonical public documentation URL has not been configured for this site.
journalism-protocol-notes/PROTOCOL.md— sole normative URMA V0 specification.journalism-protocol-notes/DECISIONS.md— current owner decisions.journalism-protocol-notes/ARCHITECTURE.mdandSHARED_SERVICES.md— layer ownership and reusable services.journalism-protocol-notes/profiles/— Capture Evidence, Private Files, optional Redundancy and the approved public Git profile.journalism-protocol-notes/applications/— separate Capture, Archive, Wire and Git contracts/workboard.journalism-protocol-notes/05_funding_strategy.mdandresearch/urma-modular-funding-roadmap.md— independent funding scopes and the working budget.TEST_RESULTS.md,android/VERIFICATION.mdanddesktop/INTEROP.md— scoped implementation evidence.
The website summarizes these sources without parallel format snapshots. Profile schema completion and independent interoperability remain explicit work.
URMA V0 is a normative draft. The root implementation and deterministic corpus have scoped evidence. Android records its separate integration and live private recovery exercise. No full V0 conformance, complete profile interoperability, stable product release, external audit or shipped camera is claimed. Git has an approved public HEAD-only design; its application remains to be implemented.
Protocol materials/data use CC0-1.0; project-authored source uses 0BSD. Dependencies retain their licenses. Complete distribution notices and the non-normative scientific PDF remain work.