It seems that this does not cover artifacts alredy existing where there isn't yet a requirement: a rapid prototype or demo gets created on a weekend, where requirements will be created later.

not clear what is referred to "create the artifact"? Create the link between requirements and taxa? between any artifact and taxa? between taxa and future artifacts, provided that requirements are already linked to taxa?

not clear if TL supports this scenario

it is common that software engineers are not in charge on writing use case scenarios/acceptance criterias. This is core for Agile methodologies.

this scenario is similar as the problem faced when EHR's were first introduced: sometimes it was required to phisicians to match the prescription to ICD-10 classification of diseases of World Health Organization. The implementation failed.

anyhow indirect trace links do not guarantee that whenever a new downstream artifact gets added to the system the link between the requirement and the new artifact gets created antomatically. It will also require human review. So now we have to stages of review instead of one: First stage of review is when we match requirements with taxa and second whenever an artifact is available into the system.

indeed, this is something we should verify with LLMs and see its limits

this is the expertise that we provide

in our cae, time is whenever a new/changed test case gets detected in a code repository

but now we have moved the problem of automatic tracing SWE requirements to downstream artifacts to semi-automatically trace SWE requirements to taxonomies.

Yet if this guarantees a good confidence rating, it would be also helpful for TL, e.g. we can use LLMs to match requirements with taxa.