rl-docs-hub

Documentation Gaps and Drift Register

Use this lightweight register to track known documentation issues that still need follow-up.

Status key

• Open — known gap or drift still unresolved
• Planned — follow-up is agreed but not done yet
• Blocked — waiting on a decision or source input
• Closed — resolved

Register

ID	Area	Status	Gap / Drift	Needed decision or action
DOC-001	Navigation	Closed	rl-bank-mvp docs existed in the repo but were not included in mkdocs.yml navigation.	Closed by adding the bank section and feature-status page into mkdocs.yml navigation.
DOC-002	App completeness	Open	Existing app sections are inconsistent in depth; some apps only have architecture while the governance standard now expects product/design/business rules/API/DB/data flow/permissions coverage before coding/PRs.	Backfill app pages/templates to meet the new governance standard.
DOC-003	Status usage	Open	Existing app pages do not consistently declare a documentation status.	Decide whether to retrofit status banners/front matter across all current app pages.
DOC-004	Decision records shape	Open	Important decisions are now required, but a dedicated ADR-style pattern is not yet standardized per app/shared area.	Decide whether to introduce a formal ADR folder structure or keep decisions embedded in governance/app pages.