Alcove

Appearance

Alcove roadmap ​

This document lists planned work, grouped by the release in which it is targeted. Major functionality that has already shipped is summarized in CHANGELOG.md, not here. Project overview and architecture are in DESIGN.md.

Targeting is aspirational; the maintainers do not commit to a release date for any item below.

Pre-1.0 ​

Work required before the 1.0 release.

  • Annotated end-to-end exchange specification example in EXCHANGE_REFERENCE.md, generated by exporting from the web application's configuration GUI
  • Accessibility assessment against WCAG 2.1 Level AA and Section 508 for the web application; publication of a VPAT
  • One-time EAR ENC notification to BIS and NSA before public 1.0 distribution
  • Public website with documentation
  • Linkage rule sets for different operating contexts: bundles of matching rules tuned to the fields a context shares and to its precision and recall needs (for example, a set that relies on no Social Security number and uses addresses); the built-in rule-set registry and picker are the first steps

Version 1.0 ​

  • SSH channel as a lower-latency alternative to SFTP polling
  • Parallelizing the commutative-encryption step

Version 1.1 ​

  • PSI-Sum
  • Synchronous protocol execution for the CLI (the web WebRTC path is already synchronous; this eliminates file-based polling latency where the channel allows)
  • Provisioning of supporting services (peer coordination, STUN/TURN, SFTP, WebSocket-to-TCP proxy)
  • Reference configurations and deployment guides for each supporting service; the section pointers in DEPLOYMENT.md will be replaced with concrete guidance
  • Metadata classification

Possible later work ​

Captured in DESIGN.md#possible-extensions. These are research directions rather than committed work:

  • Threshold and weighted scoring via secure multi-party computation
  • Brute-force protection through input-size controls
  • WebSocket relay as a WebRTC fallback
  • Electron desktop distribution of the web application. The progressive-web-app half is built: the hosted application is installable and its shell renders offline (see MANAGED_EXCHANGE.md)

See also ​