LPA Drift-Tracking Prompts¶

Five prompts for LPA in a drift-tracking posture — long-horizon watch for slow decoder drift that accumulates across releases.

Context for Claude¶

As LPA in drift mode you maintain a rolling 90-day log of decoder edits, clone-location changes, and verifier findings. You partner with the forensic auditor (FOR) for cross-reference to git blame.

Prompt 1: 90-day drift log¶

LPA, compile the 90-day drift log:
- Git log for docs/ecosystem/codename-decoder.md
- Count of edits per release
- Net rows added / changed / removed
- Any row that flipped tiers

Expected outcome: drift log.

Prompt 2: Slow-drift detection¶

A row has not been edited in 6 months but its clone might have moved.
Design the slow-drift detection:
- Check git log of the sister repo for rename events
- Compare against our decoder entry
- Flag discrepancies

Expected outcome: slow-drift detector design.

Prompt 3: Sister-repo rename coordination¶

Sister repo `l2_distro_hub_ext` might rename to `datalock_ext` at some
point. LPA's coordination plan:
- Early-warning subscription (watch the sister repo's release notes)
- Decoder-row draft for the rename
- mkdocs nav retouch
- ADR if the rename is architecturally meaningful

Expected outcome: rename coordination plan.

Prompt 4: Drift severity scoring¶

Not all drift is equal. Propose a 0-3 severity scale:
- 0: cosmetic (URL trailing slash)
- 1: path nudge (no consumer impact)
- 2: rename requiring consumer migration
- 3: tier flip
Score the last 10 drift events.

Expected outcome: severity-scored log.

Prompt 5: Drift-budget policy¶

Propose an allowable drift budget per release: e.g. "no more than 2
severity-2 events per minor release". Justify with the v1.6.1 and
v1.6.2 actuals.

Expected outcome: drift-budget policy.

Persona YAML: src/fcc/data/personas/local_path_auditor.yaml
Related prompts: persona-lpa-prompts.md, local-path-audit-prompts.md, auditors-vocabulary-drift-sentinel.md