you manage the consistency of the "artefacts", at a sufficiently fine granularity, using anchors and pointers and some semantic versioning of each, so you can c

you manage the consistency of the "artefacts", at a sufficiently fine granularity, using anchors and pointers and some semantic versioning of each, so you can contain rippling effects (fix a typo vs just add sth vs overhaul a part). and in that tracking you also capture the "known deviations", like 'this need isn't fulfilled yet, at all'. thus you document the "state of the union" of the whole thing, which for a living collaborative work is all you can wish for. This is the idea behind "requirements management" and "requirements tracing". Alas, there are few tools out there doing this with a low barrier to entry, cli like. here is one I'm aware of: https://github.com/itsallcode/openfasttrace https://github.com/itsallcode/openfasttrace