Functional Requirements — Retired
:::caution This page is retired As of 2026-08-14, functional requirements no longer live on this page. They have moved to the versioned requirements catalog:
- Requirements Catalog — index — start here: the four version buckets, the ID scheme, and the mandatory per-requirement template.
- V1.0 MVP — most
REQ-FUN-*ids from this page's old "Version 1 (Baseline / MVP)" tag. - V2.0 shipped — items delivered in the
v2.0.0release, includingREQ-FUN-50's current (sidebar.toml) form. - V3.0 next and V4.0+ backlog —
everything this page used to tag "Future Phase (v2.0+)". That tag is retired along with this page: it
read as "already delivered" once
v2.0.0actually shipped, which misrepresented several still-unbuilt requirements (translation, RAG export, LLM enrichment, XLIFF). Every requirement in the new catalog now carries exactly one explicit target —v1.0,v2.0,v3.0, orv4.0+.
If you have an old link pointing at a #req-fun-NN anchor on this page, search for that id's exact
heading (`REQ-FUN-NN` — Title) in the four files above. Each requirement is its own heading there,
so it has a stable Docusaurus-generated anchor derived from that heading — unlike this page's old
bullet-list structure, which never generated per-requirement anchors at all. Explicit {#custom-id}
anchors are deliberately not used: that syntax fails to build in this repo's MDX toolchain (see the
catalog index for the details).
:::