I have a minor role working on a complex system that has many requirements. Some are monumental. Some are microscopic. They all need to be tracked and, at some point, traced to the implementation. Unfortunately, the specification has no unique, immutable identifiers for the requirements. Without these there is little chance every requirement will be tracked and less of a chance they can be traced.
The specification is a Word document. These are easy to create, to distribute, and to read (either online or in print). Word has useful features for conveying specifications -- section numbering, line number, version tracking, etc -- but not for tracking.
This got me thinking about tools like Starkits and Marimo (w/ uv) and using these to convey the specification's requirements and to track them. Ideally these specification "documents" can be as easily created, distributed, and read as Word documents are. They can be run locally by an individual or run on a server and used by the whole team. No need for a third party SaaS. No need for company IT involvement.
I don't have much more to say about this right now. This note is here to remind me of this idea during some future.
