Is there a way to create a custom inline tag or label in a FrameMaker document?

Question

I am trying to draft a requirements document that has an inline tag offset by brackets for every requirement listed. I would then like to generate a table of contents to keep track of the locations of these tags within the document. (I know tag and bookmark are not the correct terms for this, but I can't think of a better one)
The format should be something like this:
The software package shall [SRD_XXXX] be verified by the operator.
Where the "SRD_" is the label and "XXXX" is an auto-incrementing numeric value assigned to this requirement.

Answer 1

> ... numbering to be 4 characters with leading zeroes, as it's
> a standardized format. What hack would I have to use to do that?
Search this forum on "leading zeros", for, example:
Has anyone worked with US MIL-STD doc, and successfully generated page numbers in TOC?
There are two approaches that I know of, both touched on in that old thread:
Zeroes as tab leaders (trickier to set up, easier to maintain)
Literal leading zeroes in a small suite of autonumbers (easier to set up, trickier to maintain)
You'd have separate formats for SRD-000x, SRD-00xx, SRD-0xxx and SRD-xxxx and would need to
mind break-points so you avoid things like SRD-00010 (extra digits).
... unless Adobe has added something to AN formatting since FM9 that I don't know about.
> one reason I wanted to make them auto-incrementing was so I could add
> some in between existing instances as necessary without having to renumber everything after.
As isolated paras either in the main narrative or on reference pages, you can get this. Using cross-references is just a variation on the now-documented EndNote hack. As with EndNotes, the main risk is if you move the main narrative Xref, as it will then be out of order.
But you can have in-narrative "isolated" paragraphs that look like words in the middle of a para, by using Run-In paragraph formats. In a para that looks like:
The software package shall [SRD_XXXX] be verified by the operator
would actually be three paragraphs run together.
"The software package shall" is format, say, Body.Lead, Pagination <*> Run-In Head -- Default Punc {space}{left-bracket}
"SRD_XXXX" is format, say, SRD, Pagination <*> Run-In Head -- Default Punc {right-bracket}{space}
"be verified by the operator." is just normal Body
Para format SRD would have whatever auto-number scheme you decide on.