Orchestrata Ultimate / Specs / codegen
codegen: codegen
At a glance
| Item | Value |
|---|---|
| Spec directory | specs/codegen/ |
| Status line in the spec | not stated |
| Requirement IDs defined | 0 |
With a @traces citation in src/ |
0 (n/a) |
With a @traces citation in tests/ |
0 (n/a) |
| Tracked files | 1 |
| RTM page | codegen |
Reading this spec
This directory is not a prose specification. It holds a single data file, specs/codegen/enums.json, which describes enumerations for code generation. Each entry gives the enum's name, its base class, the module and source path where it lives, a docstring, its members with their string values, and optionally a list of traces that link the enum to a spec, a user story and requirement IDs. The file lists three enumerations, all string enums in the orchestrata_ultimate.knowledge_graph.types_enums module: ChangeType (the types of changes tracked in history: created, modified, deleted, renamed and moved), SyncStatus (the status of a file sync operation: pending, in progress, completed, failed and skipped) and NodeType (the types of nodes in the knowledge graph, with 13 members). Only NodeType carries traces, citing REQ-008-006 and REQ-008-052 of the knowledge graph spec and REQ-015-194 of the plugin SDK spec.
Because the directory has no status line and no requirement text, there is nothing to read here beyond that data file. No requirement IDs could be parsed from it, so the traceability matrix has nothing to measure for it: it contributes no covered and no uncovered requirements. The page tracks 1 file, and the status line reads as not stated. Measured trace coverage is not applicable, since the spec defines 0 requirement IDs. The gap, if any, is in the spec itself: requirements are not written in the REQ- form that check-traces reads.
Other tracked files
specs/codegen/enums.json