Requirements Management

To generate a requirements traceability matrix, you create functional requirements, technical requirements, and test requirements, then link their IDs to form a complete FR×TR×TEST mapping for export. This ensures all requirements remain connected and validated.

Yes, you can ingest existing markdown or wiki documents directly into the workspace database. This process converts your current requirements documentation into structured FR, TR, and TEST records to establish a single source of truth.

The best way to link functional requirements to technical specifications is by applying traceability mappings within a workspace-scoped database. By enforcing strict ID conventions, you can reliably connect one FR to multiple TRs and TEST IDs.

Yes, requirements management applies strict workspace isolation by operating within the workflow.requirements.* namespace. This ensures your project's traceability matrix and requirement records remain completely separate from other workspaces.

You can export a requirements traceability matrix by generating markdown or wiki views from the workspace database. The system creates functional, technical, or testing views, as well as a full FR×TR×TEST matrix document for review and CI checks.

The strict ID conventions ensure deterministic operations and validation but require precise formatting when creating or updating FR, TR, and TEST records. You must adhere to these naming constraints to maintain traceability mappings within the workspace database.