Skip to content

Latest commit

 

History

History
27 lines (25 loc) · 2.07 KB

ROADMAP.md

File metadata and controls

27 lines (25 loc) · 2.07 KB

Roadmap

  • Foundation: repository structure, license, governance and initial threat model.
  • MVP definition and nexusq-core integration spike.
  • Public repository and contribution templates.
  • Security-reviewed vault/file/backup adapter and automated integration tests.
  • Recovery design and user-tested recovery flow.
    • Draft backup-based recovery proposal and automated restore of file and folder vaults with a new vault password (user testing still pending).
  • Encrypted folder manifest and format migration policy.
    • Version-1 encrypted manifest, opaque object names, safe relative paths, atomic create-only publication and folder roundtrip tests.
    • Format migration, empty-directory preservation, large-file streaming and cross-platform filesystem review.
      • Drafted the NQX2 chunked-streaming proposal; no cryptographic code is implemented pending core review.
      • Review and implement the format in nexus-q with NQX1 backward compatibility and fuzz/fault-injection tests.
  • Desktop UI and accessible onboarding.
    • Initial Tauri 2 desktop shell and Rust command boundary (prototype only; not yet user-tested).
    • UI commands for individual files, folder encryption/restoration and encrypted key backups.
    • Native file/folder pickers through Tauri's cross-platform dialog plugin.
    • Initial accessibility pass: semantic status/errors, labelled picker controls, busy states, keyboard focus and reduced-motion support.
    • Password visibility controls; visibility resets when forms clear secrets or the vault is locked.
    • User testing, onboarding polish and full accessibility review.
  • CI for library and desktop checks/builds; cross-platform alpha installer release workflow.
  • Dependency review, fuzzing, signed releases and reproducible-build investigation.
  • External security review and community beta.
  • 1.0 release after recovery, format and update-security criteria are met.

A roadmap item is not complete merely because a prototype exists. Security milestones require published evidence and review.