criteria-retrieve

Criteria Retrieve (Connect)

Purpose

Load the quality framework and criteria the deterministic engines apply: evidence substantiation, required disclaimer/reliance language, scope alignment, confidentiality, brand, licensed-content attribution, embedded-instruction handling and prior-findings closure.

When to use

After deliverable-ingest in every run, and whenever a reviewer asks which checklist, required language or prior QRM finding applies.

Inputs

• Structured intake payload from deliverable-ingest.
• Quality/risk framework excerpts, gate criteria and required language.
• Brand/formatting standards and prior review finding tracker.

Steps

1. Retrieve the criteria set that applies to deliverable type, audience and intended recipients.
2. Preserve criteria.criteria_sections as an explicit list and compare any engagement extract against the shipped floor: quality-gate-criteria.md #1-#8 plus severity-rules.md #1-#4. If the extract omits a shipped section such as #8, keep the shipped floor and escalate the mismatch.
3. Identify whether third-party reliance language is required, including named lenders, regulators, acquirers, vendors or other allowed users. Report the required disclaimer type only: QRM supplies the approved reliance-restriction clause, and this plugin never drafts, paraphrases or supplies disclaimer wording. When the clause is needed, the output says "reliance-restriction clause required; obtain the approved wording from QRM".
4. Normalize prior findings, closure status and required fixes without accepting tracker closure as proof.
5. Verify intake-owned required_disclaimer_type, scope_aligned and client_data_handling against the criteria and source extracts; correct only with cited evidence, otherwise leave the field and escalate uncertainty.
6. Pass the complete criteria payload to assertion-map and gate-check.

Output

Contract payload with criteria, prior_findings, required language and citations to quality-gate-criteria.md and severity-rules.md.