Role Versioning

Role definitions are living documents. When ANCHOR deployed as Agent 20, three existing role contracts required updates — PATCH's escalation protocol, CLOSER's handoff timing, and BEACON's customer intelligence routing. Without versioning, those changes would be invisible.

Version every role contract like you version code. Semantic versioning works: major version for role splits or merges, minor version for scope adjustments, patch version for threshold tuning. HUNTER is currently at v3.2.1 — major 3 (the January role split from CLOSER), minor 2 (added ICP scoring criteria), patch 1 (adjusted lead qualification threshold from 65 to 72). The version history tells you exactly how the role evolved and why.

1. Adopt Semantic Versioning Major: role splits, merges, or fundamental scope changes. Minor: new task additions, handoff modifications, SLA adjustments. Patch: threshold tuning, formatting changes, minor quality gate updates. Every version increment includes a changelog entry explaining the reason.
2. Maintain the Changelog Each version entry records: what changed, why it changed, what triggered the change (audit finding, performance data, team growth), and the expected impact. The changelog is the institutional memory of role evolution.
3. Link Versions to Performance Track key metrics before and after each version change. HUNTER v3.0 increased lead qualification accuracy from 71.24% to 84.67%. QUILL v2.3 reduced revision rounds from 2.4 to 1.1 per post. If a version change does not measurably improve performance, understand why before the next iteration.