Narrative Quality Auditor

Based on the TALE Benchmark. This is the auditor-class gate for brand narrative — the eighth gate, peer of content-quality-auditor (CORE-EEAT), domain-authority-auditor (CITE), content-reviewer (C³ ART), ad-account-auditor (ROAS), email-quality-auditor (SEND), launch-readiness-auditor (RAMP), and social-quality-auditor (ECHO). It fills the gap between authoring the canon and letting a surface repeat it: a pass/fix/block check no other narrative skill performs.

This skill scores a narrative and messaging system on the four TALE levers (Truth, Architecture, Landing, Evidence), enforces four red-line vetoes, and emits a gated audit artifact with a SHIP/FIX/BLOCK verdict — as a full four-dimension NQS audit or as the fast pre-publish consistency go/no-go on a single surface vs the canon. It feeds the TALE Evaluate phase's scoring role and is the gate the T1/A1/L1/E1 vetoes are judged at (see tale-benchmark.md).

Scope guard: this skill is the sole computer of NQS = floor(weighted({T,A,L,E}, goal-weights)) and the sole enforcer of vetoes T1/A1/L1/E1. Every other narrative skill works ONE lever and hands off — narrative-baseline-mapper/category-narrative-mapper/audience-belief-mapper/positioning-truth-tracer build T, strategic-narrative-designer/message-system-architect/brand-language-codifier/story-bank-builder build A, narrative-cascade-planner/pitch-narrative-builder/narrative-enablement-kit/proof-point-packager land L, message-test-designer/narrative-resonance-monitor/narrative-drift-monitor work E. None of them compute the NQS or run the vetoes; that is this gate's job. The canon stays with narrative-registry and claims stay with offer-claims-registry — this gate judges against their records, it never writes them and never adjudicates a claim.

Provisional framework: TALE bands are new. Treat scores as provisional until calibrated against ~30 real narrative audits in memory/audits/narrative/.

When This Must Trigger

Run this before a flagship surface ships or when the narrative system itself needs a verdict, even if the user does not use audit terminology:

• User asks "audit our brand narrative", "is this message on-canon", or "does our differentiation actually hold"
• narrative-enablement-kit or proof-point-packager finishes and the assembled canon needs a verdict before it enables anyone
• A flagship surface (homepage, pricing, store listing, sales deck) is about to change and must be checked against the canon — the pre-publish consistency mode (below)
• narrative-drift-monitor flags a surface drifting from canon, or a canon re-version just landed in narrative-registry and dependent surfaces must be re-judged
• User suspects a differentiation-truth, canon-integrity, message-match, or evidence/resonance problem