Skip to content

ROADMAP.md

Latest commit

 

History

History
64 lines (44 loc) · 3.44 KB

ROADMAP.md

File metadata and controls

64 lines (44 loc) · 3.44 KB
Raw

Roadmap

Latch 1.0.0 is the first stable release. The portable evidence pipeline is implemented and host-tested, and one configuration (ESP32) is physically HIL-qualified with 23 additional targets emulator-tested under Renode. Latch is not yet an LTS line; the remaining qualification and review gates are tracked in docs/known-limitations.md. The next phase is to turn more platform claims into reproducible physical hardware evidence.

This roadmap is directional rather than a promise of dates. Issues and release notes are the source of truth for committed work.

Public-preview priorities

1. Make the first result obvious

  • Keep the host capture-and-decode demo working on Linux, macOS, and Windows.
  • Keep the machine-readable decoder and copy-paste CMake consumers stable in CI.
  • Document the smallest useful retained-RAM and Flash integrations.
  • Keep Arduino, ESP-IDF Component Manager, PlatformIO, Zephyr and Rust package metadata version-locked and validate their source layouts before publication.

2. Publish hardware qualification evidence

  • Record board, revision, SDK, compiler, linker script, and test procedure for each result.
  • Exercise real HardFault/trap, watchdog, brownout, corrupt-stack, nested-fault, and interrupted-Flash scenarios.
  • Promote a platform from “integration boundary” to “qualified example” only when its evidence is reproducible.
  • Turn the new Nordic, NXP, Microchip, TI, Silicon Labs and RV64 integration boundaries into board-specific HIL reports instead of broad compatibility claims.

3. Harden protocol and storage tooling

  • Keep LEP, stream/ACK, compression and AEAD fuzzers seeded from public vectors.
  • Expand cross-language and negative compatibility vectors.
  • Make spool inspection and recovery behavior easier to test outside firmware.

4. Review the security boundaries

  • Obtain independent review of envelope cryptography, nonce/key provisioning, redaction, replay behavior, and secure-element adapters.
  • Document measured stack, code-size, and timing costs for representative profiles.
  • Keep security claims narrower than the evidence.

5. Establish a predictable release rhythm

  • v0.2.0 is the first public-preview baseline.
  • Publish small, reviewable releases with changelog entries and generated provenance.
  • Use the version-parity gate and release procedure before the next tag; registry publication remains separately approved and manual.
  • Keep good first issue work curated and close the loop with contributors quickly.

Community-owned opportunities

The highest-value outside contributions are:

  • real board and toolchain qualification reports;
  • FreeRTOS, Zephyr, ESP-IDF, and bare-metal examples;
  • decoder, fuzzing, and packaging improvements;
  • reviews from people who have debugged retained state, brownouts, Flash interruption, or nested faults in production devices.

See good first issue and help wanted.

Non-goals

Latch does not aim to own:

  • a hosted observability dashboard;
  • the product's scheduler, allocator, bootloader, network stack, or Flash driver;
  • automatic capture of arbitrary memory without an explicit policy;
  • certification for hardware that has not been tested;
  • source minification as a substitute for compiler and linker optimization.