req-link

To validate target IDs before inserting artefact links, the system reads the registry to confirm every target ID exists, preventing broken references and maintaining traceability across artefacts and source code.

Adding satisfies links between requirements and design artefacts involves locating the source artefact, inserting the appropriate satisfies link at the correct insertion point, re-validating link integrity, and committing the change separately.

Yes, you can link code annotations to requirement IDs across source code. The process validates the target ID exists in the registry before writing the link to maintain traceability and prevent broken references.

Yes, you need read access to the library/_ids.md registry to prevent broken artefact references. This read access allows the system to confirm target IDs exist before attempting to insert any satisfies links.

Your satisfies link insertion requires a separate commit to record the changes in a reversible step. After locating the artefact, inserting the link, and re-validating integrity, a separate commit isolates the traceability update.