A design that doesn't hand regulatory review wholesale to one model

This describes a real deployment that, instead of feeding hundreds of pages of design documents and constantly amended laws into one model wholesale, has a lead role set the review plan and order and then divides searching the documents, searching the regulations, and cross-checking the two among separate roles. What stands out is that the division of labor is justified by concrete failures: omissions and mixed-up information. For search, since the provisions include both ones that are found only when the terms match exactly and ones that mean the same thing in different wording, keyword and vector search are used together, and the knowledge base is kept current through incremental updates that re-collect only what has changed. The result stressed most is not speed but evidence tracing: clicking a review result immediately shows where in the original text the basis for the judgment lies. However, since it is a case study produced by the vendor, not a single quantitative result, cost figure or failure case is presented.

This is a note: my own write-up after reading several sources. It has no source link; events checked against a source are kept as records.