@djjones, a question for you about the factory’s override rule, which came up while lining up the BrainDrive specs with PAA.
The problem: On the 10-20 call we agreed that the factory loads PAA’s acceptance criteria first, and a BrainDrive criterion with the same ID replaces the PAA one. But BrainDrive’s specs already number their own criteria AC-1.1, AC-5.1 and so on, the same way PAA does. So an unrelated BrainDrive AC-5.1 would silently replace PAA’s AC-5.1.
What I’d like to do: make overriding explicit instead of matching on the number.
- BrainDrive’s own criteria keep their current numbers. Nothing gets renumbered, so the existing test plans and evidence stay valid.
- A BrainDrive criterion that repeats a PAA rule becomes a one-line pointer: “Inherits PAA AC-3.5”.
- A BrainDrive criterion that deliberately differs from PAA says so: “Overrides PAA AC-5.1”, and it also goes in the departures register.
- The factory acts only on those two labels, never on a bare matching number.
This changes one detail of what we agreed on 10-20 (“same ID” becomes “an explicit Overrides label”). Since you’re building that rule, what do you think? Does it work for the factory, or do you see a problem with it?