Agent Lexicon
Dev-time terminology governance
One canonical vocabulary across agents, branches, and tool calls.
Agent Lexicon discovers project language, records review decisions, publishes an immutable vocabulary snapshot, and gives deterministic resolve, guard, diff, merge, and MCP interfaces to coding agents.
Use Agent Lexicon when
Section titled “Use Agent Lexicon when”- multiple agents or branches introduce competing names for the same project concept;
- terminology needs to be reviewed like code instead of living only in prompts;
- a tool call must be allowed, blocked, or clarified from deterministic language rules;
- pull requests need a terminology review alongside tests and linting;
- agents need a compact canonical vocabulary before starting a task.
Core workflow
Section titled “Core workflow”scan repository ↓review evidence-backed candidates ↓publish a lexicon snapshot ↓context / resolve / guard / lint-diff / check-merge / MCPThe local workflow is review-first. Discovery can suggest candidates, but accepted vocabulary is explicit and versioned.
Documentation map
Section titled “Documentation map”InstallationInstall with pipx or pip and verify the CLI.QuickstartGo from an empty project to a published lexicon.Review and publishUnderstand workspace evidence, decisions, and snapshots.Agent contextGive an agent the canonical terms and deprecated language to avoid.Merge and CI checksDetect drift in working diffs and pull requests.MCP serverExpose deterministic terminology tools over stdio.
Product boundary
Section titled “Product boundary”Agent Lexicon is repository-local and deterministic by default. Optional semantic extras may rank suggestions for a human reviewer, but they do not replace deterministic enforcement. Shared network storage and automatic synchronization with SkeinRank are not implied by this documentation.