reconcile-sop

reconcile-sop — keep the SOP true as the code changes

A v3 SOP (.tessary/sops/<call_site_id>.yaml, authored by /evals:derive-sop) states what a call site's standing procedure means. Commits change prompts, tool descriptions, and routing — and a conformance file that has drifted from its own instruction surface measures the wrong thing while looking authoritative. This skill is the maintenance half of the contract: re-read, re-verify every sentence, propose changes, re-lint.

There are no stored anchors, by design. The SOP deliberately carries no file paths, line numbers, or quoted prompt text to check against — pointers rot the moment a prompt file is refactored, and instructions live duplicated and disjoint across real repos (this platform's own git-observer learned the same lesson and moved from static anchors to re-analysis). So reconciliation is never "check the anchors": it is re-derive the rule↔code correspondence by reading the whole instruction surface, every time. Evidence lives transiently in your change proposal, never in the file.

Resolve the plugin path once

PLUGIN="${CLAUDE_PLUGIN_ROOT:-$(find ~/.claude -name SKILL.md -path '*/evals/skills/reconcile-sop/*' 2>/dev/null \
  | xargs -I{} dirname {} | xargs -I{} dirname {} | xargs -I{} dirname {} \
  | sort -V | tail -1)}"
echo "PLUGIN=$PLUGIN"

Flow

1 — Locate the SOPs in scope

List .tessary/sops/**/*.yaml. If the user named a call site or a commit range, scope to the SOPs plausibly touched; with no hint, reconcile all of them. No SOPs → route to /evals:derive-sop. A recent diff (git log/git diff over prompt and tool files) tells you where to look first — never what to skip: an instruction can change meaning through an edit far from where it was first stated.

2 — Re-read the whole instruction surface

Exactly as /evals:derive-sop step 2: system prompts and their composed fragments, tool definitions and descriptions, routing rules, few-shot examples, guardrail config, checked-in policy documents — all copies, however duplicated or disjoint. This is a full re-read, not a delta-read; the absence of anchors is what makes that mandatory, and it is what makes the result trustworthy.