Skip to content

BACKLOG.md

Latest commit

 

History

History
106 lines (89 loc) · 5.17 KB

BACKLOG.md

File metadata and controls

106 lines (89 loc) · 5.17 KB
Raw

Backlog

A candidate register of UX patterns, candidate modules, and cross-cutting concerns that may eventually inform ROADMAP.md. Sibling document to the roadmap.

Purpose

  • Candidate register only. Not a commitment, not a promise of delivery, not a feature list.
  • Items are intentionally unordered.
  • Items may move onto ROADMAP.md, be deferred indefinitely, or be dropped outright after review.
  • Inclusion here does not imply that any item has been scoped, designed, approved, or staffed.
  • Boundaries documented in ROADMAP.md and README.md (browser-only, static-host friendly, no backend, no telemetry, no persistence by default) apply to every entry below. Anything that would weaken those boundaries is out of scope unless explicitly re-decided.

Shared UX patterns

Candidate cross-module UX patterns under consideration. None are scheduled.

  • Command-center landing / workspace — an optional future shell that could group module launcher cards alongside local, in-memory, session-only status for sample-run triage. Strictly local; would not introduce any remote state, any live feed, or any persistence across reload.
  • Module workbench — a consistent per-module layout candidate: input on the left, results on the right, sample loader, clear-input action, a run action disabled until input is sufficient, explicit empty/success/warning/error/ caveat result states, and a privacy note adjacent to the input area.
  • Documentation / support hub — a first-class page or set of cards rather than a modal, so reference material is linkable and persistent within the navigation, not hidden behind transient UI.

Candidate modules

Modules being considered. None are scheduled. Each is governed by the boundaries above and the caveats below.

  • BIC tooling — possible expansion beyond the shipped BIC demo, made up of smaller surfaces such as:
    • Syntax Check — ISO 9362 shape feedback only.
    • Demo Snapshot Lookup — lookup against the bundled demo snapshot only.
    • Structure Explainer — explain BIC structure (institution, country, location, branch).
    • Provenance & Caveats — surface snapshot identity and demo-only limitation text using the shared provenance pattern.
    • Persistent caveats for any BIC tooling considered here: bundled demo snapshot only; no current BIC existence checks; no current reachability; no current operational status; no current bank enrichment; not for production routing, compliance, or payment decisions.
  • Documentation / support hub — a possible in-app reference area covering Getting Started, the Browser-only Privacy Model, IBAN reference content, BIC caveats, ISO 20022 module notes, the Provenance model, and an explicit "What this suite does not claim" page.
  • Vault — encrypted local export bundle — a future, security-reviewed local portability feature only. If built, it should let the user explicitly export selected local outputs as an encrypted downloadable bundle and later import that bundle in a fresh browser session. It must not become cloud storage, server storage, sync, accounts, remote key custody, telemetry, upload, or default browser persistence.

Cross-cutting concerns

  • Reusable provenance component — the shared provenance pattern referenced by the roadmap; would be consumed by IBAN Workbench, the BIC demo module, and any future module that ships generated/snapshot data.
  • Optional command-center shell — only worth introducing once at least one cross-module workflow makes the shell genuinely useful; otherwise the per-module pages stay sufficient.
  • Consistent result-state taxonomy — a shared empty/success/warning/error/ caveat vocabulary so every module communicates outcomes the same way.

Boundaries — what this suite does not claim and will not borrow

The following are non-goals for the suite as currently scoped. They are listed here so that nothing in this backlog is read as a commitment to them:

  • No backend, no API, no server-side processing.
  • No server-side persistence and no remote logging.
  • No telemetry, no analytics, no error reporting beacons.
  • No file upload off the user's device.
  • No MQ, directory, admin, or infrastructure settings UI.
  • No real send-to-agent action and no live system action of any kind.
  • No live monitoring, no live activity feed, and no live settlement view.
  • No Verification of Payee / VOP and no account-owner / name matching.
  • No live BIC lookup, no current BIC reachability, and no current bank enrichment.
  • No cloud/server Vault. Any future Vault is limited to an explicit encrypted local export/import bundle and remains unbuilt until separately reviewed.
  • No production routing, compliance, or payment decisions derived from the bundled BIC demo snapshot or any other snapshot data.

Explicitly out of scope

These are not under consideration for this suite, even as backlog items:

  • Login, authentication, and any user identity model.
  • Multi-user shared state.
  • Server-side persistence of any kind.
  • Cloud-synced or account-backed Vault storage.
  • Live reference-data feeds.
  • Operational monitoring of payment systems.
  • Production workflow orchestration.