Reference & Historical Records¶

This page provides access to detailed technical references, historical planning records and operational material that remain useful for traceability but do not need to occupy the primary documentation path.

The pages listed here have not been removed from the documentation set. They remain available as supporting references and historical evidence.

Architecture and data reference¶

API contracts and mapping reference¶

Security reference¶

Testing procedures and acceptance reference¶

Design and UX reference¶

The current, final design lives in the primary path as Final Design & Wireframes. The superseded Sprint 1 wireframes are historical evidence only, kept in the legacy wireframe archive.

Deployment and operations reference¶

Final API gap-analysis records¶

These focused records preserve the analysis used to close or bound selected final API work. They are retained for implementation traceability rather than presented as primary product documentation.

Historical planning and Sprint records¶

These pages preserve the state of the project at the time they were written. They should not be read as if later implementation decisions were already known during earlier Sprints.

The current final-state assessment is maintained separately in Final Requirements and Rubric Traceability.

Development reference¶

Retained evidence¶

The repository-level evidence collection remains authoritative for retained Sprint, validation, stakeholder, user-testing, decision and AI records.

Use Project Records & Evidence as the normal evidence entry point rather than duplicating those records into this appendix.

AI Declaration¶

The reference and historical-record index was planned and drafted with the assistance of ChatGPT-Web[GPT-5.6 Sol]. The final-design and legacy-wireframe separation was added with the assistance of Claude-Web[Claude Opus 5.5] under issue #894.