Credit Qa Verifier

Path Resolution

See dev/engine/agent-protocol.md §1 — engine/ and templates/ paths resolve to the package root in both plugin-install and open-as-project modes.

Purpose

Engine version: v0.3.2

Non-Negotiables (see AGENTS.md): no delivery of analysis conclusions without a passing QA Verdict from this skill (pure knowledge questions exempt) · no numbers without a doc §section citation (engine_undefined otherwise) · no report outside dev/templates/.

QA layer — final stage of the four-stage chain. Responsibility: perform pre-delivery review of the Delivery Note and its upstream Analysis Artifact and Path Sheet, producing a QA Verdict. This skill uses engine documents as the rule source and never relaxes a gate: if any quality gate or mandatory check fails, the verdict is fail and must be sent back for remediation; do not lower standards for delivery. This skill does not replicate any thresholds/rating mappings; rule content uses the referenced engine documents as the single source of truth.

Inputs

• Delivery Note: produced by credit-report-builder (field shape at dev/engine/pipeline-contract.md §2.3).
• Analysis Artifact: produced by fixed-income-credit-analysis, for reviewing density/veto/completeness (§2.2).
• Path Sheet quality_gates: produced by credit-analysis-router, serving as the checklist source for gate-by-gate review; path_id is the join key throughout — all three artifacts must be consistent.

Output

• QA Verdict — final stage artifact, field shape at dev/engine/pipeline-contract.md §2.4. verdict takes one of pass | pass-with-findings | fail.

Verification Protocol

1. Join key consistency: The path_id in all three artifacts must be identical and resolvable in the registry. Inconsistency → fail.
2. Gate-by-gate review: Review each quality gate in the Path Sheet's quality_gates list, producing gate_results (each with status + evidence, evidence citing engine document sections).
3. Four mandatory checks: See below. Any failure → fail.
4. Produce verdict: All pass → pass; pass but with findings that should be noted → pass-with-findings; any failure → fail with remediation.

Mandatory Checks (rule source is engine documents)

• Signal density rule density_rule: Dimensions below the density floor must not output numeric scores and must be annotated as insufficient information to evaluate; when weighted-average density is insufficient, must not output a final letter rating. Rule source: dev/engine/mosaic-engine.md §4.3.
• One-vote veto ceiling veto_ceiling: Issuers triggering a one-vote veto have their rating ceiling locked at CCC, may not be raised. Rule source: dev/engine/industry-framework.md §5.
• Mode B anti-hallucination mode_b: Unless the user explicitly provides data sources (CSV/API/MCP), no Mode B external data values may appear; all Mode B fields must be treated as data gaps. Rule source: dev/engine/mosaic-engine.md §6.
• Single source of truth single_source: Reports/analyses must not fabricate thresholds, weights, or rating mappings; quantities not defined in the engine must be annotated as engine_undefined. Rule source: all referenced engine documents.

Process-Compliance Checks (anti-drift; rule sources as noted)

• Template compliance: Every rendered report file maps to a template in the path's registry templates field (or declared marker) — no ad-hoc layouts. Rule source: dev/engine/work-path-registry.md + dev/templates/index.yaml.