tdl

End-to-end traceability is created by linking analyses, requirements, ADRs, design, and tasks using standardized templates and distributed Base36 IDs. Each document includes a Links section to map relationships across the software lifecycle.

Unique document IDs for parallel development are generated using random 5-character Base36 IDs. This distributed ID generation method prevents collisions when multiple developers create analyses, requirements, or tasks concurrently.

Documenting ADRs and linking them to requirements involves using standardized ADR templates and a dedicated Links section. You create the ADR and then map its relationship to specific functional requirements using distributed IDs.

Yes, you can use Python scripts to initialize traceability templates for your project. Running the initialization script sets up the TDL structure, enabling you to subsequently create analyses, requirements, ADRs, and tasks.

Link-based traceability works by providing a Links section within each document to map relationships. This connects tasks directly to design plans and requirements, ensuring traceability analysis and code integration references remain synchronized.

Yes, the traceability template system supports functional requirements. You can create specific requirement types, such as functional requirements, using the standardized templates and link them to analyses, ADRs, and execution tasks.