lofn-qa

SKILL: Lofn QA — Router

This file is intentionally lean to prevent context collapse. The full tuned QA procedure is preserved byte-for-byte in references/qa_full_legacy.md and must be loaded just-in-time when an audit is actually performed.

Workflow

1. Identify the output directory and modality.
2. Read ../orchestration/references/adversarial_qa_stance.md to adopt the competitive-auditor stance.
3. Read references/qa_full_legacy.md before performing any substantive QA audit.
4. For music/audio outputs, additionally read references/eligibility_7_properties.md and references/suno_15_point_qa.md; classify ACCESSIBLE vs AMBITIOUS and run the full Suno 15-point gate.
5. If using a structured report, copy the mold from assets/eligibility_report.template.md and add the Suno 15-Point QA Gate table.
6. When deterministic eligibility scoring is available from explicit numeric scores, use scripts/score_eligibility.py.
7. Apply the full QA procedure exactly as specified in references/qa_full_legacy.md; do not summarize or weaken its tuned requirements.
8. For music/audio outputs, explicitly verify standalone Suno/Udio music prompts before any PASS verdict. This gate is non-waivable even if the parent task supplies a shorter custom checklist.
9. For full Lofn pipeline outputs, explicitly verify original-Lofn artifact granularity: Steps 00–05 must exist as separate coordinator files (step00_aesthetics_and_genres.md ... step05_refine_medium.md), and Steps 06–10 must exist as separate per-pair files (pair_{NN}_step06_facets.md ... pair_{NN}_step10_revision_synthesis.md). Summary files or collapsed pair_{NN}_steps_06_10.md rollups alone are blocking pipeline-compliance failures.
10. Save QA_REPORT.md in the audited output directory.
11. If failures require rerun, follow the rerun task format from references/qa_full_legacy.md.

Non-Negotiables

• The legacy QA text is authoritative until fully split into smaller verified references.
• Do not remove tuned QA checks; move only after byte-for-byte preservation and validation.
• QA stays strict. Do not loosen file, line-count, EMO-tag, header, standalone Suno prompt, contamination, child-safety, or artifact-provenance gates to preserve “creative freedom.” Missing required structure is still a blocking failure.
• QA is not the creative brief. These checks are applied after creation to verify package readiness and diagnose failures. Creative agents should be led by Golden Seed / lineage / personality first, with QA requirements last as a hard output contract. If a file is structurally complete but generic, QA may mark REPAIR — SOUL LOSS; if a file is soulful but missing required prompt pieces, QA must still fail it structurally.
• AMBITIOUS classification is not failure unless the route target was ACCESSIBLE.
• Music/audio PASS requires a standalone copy-paste Suno/Udio music prompt per song. QA must fail any final music file that only contains scattered metadata such as [GENRE/TEMPO/KEY], [SONIC WORLD], [PRODUCTION NOTES], or lyrics without a dedicated ## 1. MUSIC PROMPT / [SUNO STYLE PROMPT:] section.
• Music/audio PASS requires full Suno performance-script headers. QA must fail bare [EMO:...], prose EMO HEADER:, plain SONG FORM:, or missing [Section - EMO:... - Voice - Cue] headers, even if the agent self-check says PASS.
• Custom parent QA instructions cannot waive the music prompt gate. If a custom checklist omits music prompts, QA must add the legacy prompt check back in and note that it did so.
• QA reports for music must include a row or bullet named Standalone Suno/Udio music prompt present for every song/pair.
• QA reports for full pipeline music must include a row or bullet named Original Lofn step granularity present for every pair. Use scripts/audit_lofn_pipeline_artifacts.py <run_dir> when available.
• QA reports must check for inline validation evidence. If *.repair_attempt_*.md, *_VALIDATION_BLOCKED.md, or failed validator logs exist, QA must verify the underlying artifact was repaired and passed later validation; otherwise mark REPAIR REQUIRED.
• Music/audio QA must run the Suno 15-Point QA Gate from references/suno_15_point_qa.md. The 7 eligibility properties alone are not enough for PASS; points 8–15 verify Suno readiness, hook survivability, Lofn specificity, anti-slop, and package readiness.