URMA. GitHub

FUNDING / PROGRESS

One programme.
From V0 to 1.0.

ROSINT.org funded the foundation to V0. Five further stages take URMA to a robust 1.0 and its own device, integrated end to end.

  1. Stage 0V0 KickstartFunded · ROSINT.org
  2. Stage 1V0 refinementIn progress
  3. Stage 2External auditPlanned
  4. Stage 3Product validationPlanned
  5. Stage 4DistributionPlanned
  6. Stage 5Own device · 1.0Target
USD 25,000invested by ROSINT.org to reach V0
5stages open for support
1.0target: robust protocol and own device, end to end

01 / STAGES

One programme. Current status.
Stage0
Funded · USD 25,000 · ROSINT.org

V0 Kickstart

The foundational build: protocol, shared services, profiles and the first applications, carried to V0 by ROSINT.org.

  • Public core workspace: 14 crates, CC0 specification, 0BSD source.
  • The urma CLI published on crates.io (v0.2.x).
  • Records published on the Litecoin testnet and recovered byte-for-byte.
Stage1
In progress

V0 refinement

Hardening the V0 foundation that is already running: protocol, shared services, profiles and every application on them.

  • Specification and code reconciled, revision by revision.
  • Shared services and profiles hardened: retry, state and resource handling.
  • Public documentation an outside reader can follow.
  • Independent reader recovers the same bytes.
  • Fresh reproducible demos: Capture, Git, Wire, Names + Web.
Stage2
Planned

External audit & remediation

A contracted, independent review of security and interoperability.

  • Written scope and the exact revision under review.
  • Threat model revisited: parsing, keys, publication, retry, recovery, trust boundaries.
  • External report and a findings register with severity and owner.
  • Fixes, regression tests and closure evidence.
Stage3
Planned

Product validation

External people use the software. Results are measured.

  • Pilots with consenting external participants per software stream.
  • Observed onboarding and use; UX fixes from real problems.
  • Measured recovery, cost and resource figures.
  • Pilot report with failures and limits.
Stage4
Planned

Distribution & sustainability

Releases others can reproduce, a way in for contributors, a maintainer for a stated period.

  • Reproducible releases with provenance.
  • Public onboarding and contribution guide.
  • Security contact and reporting process.
  • Named maintainer, maintenance period, bounded service operation.
Stage5
Target · 1.0

Own device, end to end

URMA’s own camera with the engine on board, integrated end to end with a robust 1.0 protocol. The last stage of the programme.

  • Compute and sensor selection; URMA engine integrated.
  • Modular WAN: satellite terminal, LTE and Wi-Fi.
  • Power and solar, secure boot and secure element, enclosure.
  • Prototypes; measured consumption, autonomy and thermal behaviour.
  • Field tests: capture → publish → recover from the device.
  • URMA 1.0: audited, validated with users, distributed, running on the device.

02 / HOW CONTRIBUTIONS WORK

03 / PRODUCT STREAMS

Develop in parallel across stages.

01

Protocol · Shared services · Profiles

The common foundation every application reuses.

02

Capture

Journalistic photo, video and documents: protect, publish, recover.

03

Git

Code snapshots with verified checkout beyond one host.

04

Wire

Microblogging and articles with local verification.

05

Archive

Private files and collections: catalogue, export, recover.

06

Names + Web

Registry, resolution and site packages without a central provider.

07

Camera

URMA’s own device: capture, publish, recover from the field.

SUPPORT A STAGE

Fund what remains.
See exactly what you get.

Funders see the complete programme and choose the stages or deliverables they support.

ROSINT.org