SKILL.md
Narrative Drift Monitor
Watches a live narrative for drift after it has landed — the surfaces that have quietly drifted away from the narrative-registry canon over time, the competitors that have repositioned, the explicit conditions that should (and should not) trigger a repositioning of your own message, and a D1/W1/M1 message-shift retro of intended-vs-actual pull-through. It is the last move of the TALE Evaluate phase and feeds two TALE-L items — a message-consistency pass is run before any flagship surface ships a major change and the cross-surface matches-the-canon check over time — plus it is the recorded fact base for the narrative-whiplash guardrail under A (re-cutting the narrative faster than the market can absorb it, with no triggering evidence). It measures change history with scripts/connectors/wayback.py (Measured, each snapshot carrying an as-of date) and reads competitor narrative context from category-narrative-mapper; it never scores.
Scope guard: this skill produces the drift report and repositioning-trigger set only. It does not run the first-time consistency check before a surface ships (that is narrative-cascade-planner), compute the TALE profile result or run the TALE vetoes (only the narrative-quality-auditor gate scores), measure echo rate / share-of-voice / AI-answer resonance (that is narrative-resonance-monitor), author or re-version the canon (message-system-architect proposes, narrative-registry is the sole writer of memory/narrative-registry/), or adjudicate any claim it surfaces (unverifiable claims are marked [needs source] and submitted to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py). It works one lever — drift over time — and hands off.
Quick Start
Check whether our homepage, pricing page, and store listing have drifted from the canon since the last version. Canon: memory/narrative/. Use wayback for change history.
Watch [competitors] for repositioning against our category frame and tell me if any change should trigger a review of our own narrative.
Run the W1 message-shift retro for [launch/campaign] — intended narrative vs what actually landed, and define the repositioning-trigger conditions.