G4: Specification Identification
"The login spec" is ambiguous when multiple versions exist. Path-based references break when specs are renamed or moved. AI agents also cannot reliably link related specifications.
Unique identifiers solve this problem. Regardless of how spec files are reorganized, IDs remain constant and cross-references don't break. Tools can automatically build dependency graphs, and changing a spec immediately identifies all affected specifications.
Principle
- All specifications SHOULD be distinguished by unique identifiers and MAY use domain-based namespacing for organization.
Regardless of how spec files are reorganized, IDs remain constant and cross-references don't break. Tools can automatically build dependency graphs, and changing a spec immediately identifies all affected specifications. Recommended format: [DOMAIN]-[TYPE]-[SEQUENCE], e.g., AUTH-SPEC-001, PAY-API-003. Identifiers should be stored in the frontmatter id field, and a central registry maps IDs to current file locations.