ai-readiness — score baseline + tracking

[jon-devlapaz]

Run the rubric in AI_READINESS.md against the current repo head (commit d456df8) and record the score. Track delta after each phase lands so we know whether the uplift is converting into real numbers, not just intention.

Builder's Trap? → measurement-of-measurement. Only worth doing if the score actually drives subsequent prioritization. If we find ourselves scoring without changing what we'd work on next, kill this. The rubric's protocols are designed for reproducible scoring, but the score is a signal, not a goal.

Checklist

• Run every measurement protocol listed in AI_READINESS.md criteria A1–E2 (12 criteria) against commit d456df8. Each protocol is a shell command embedded in the rubric.
• Record the baseline score in AI_READINESS_SCORE.md (sibling of AI_READINESS.md) or in a section of the existing file. Include per-criterion score, total, tier, and the date + commit SHA.
• Re-score after each phase lands (B1 close, Phase 2 close, Phase 3 close). Track delta over time, not absolute score.
• Decide retention criterion: if 2 consecutive re-scores happen without changing the next prioritization decision, deprecate this issue and remove the tracking file.

Acceptance

• Baseline score recorded with reproducible commands + outputs.
• Each delta entry references the commit that triggered it.
• After 2 phases land, an explicit decision is made about whether to continue scoring.

Refs

• Rubric: AI_READINESS.md.
• Baseline commit: `d456df8`.
• Anti-pattern guard: the rubric document itself warns against "vanity score chasing."