Agent Lexicon scans repository code and documentation for candidate project language.
How Agent Lexicon and SkeinRank work together
Agent Lexicon and SkeinRank are separate products with separate deployment boundaries. They can be used independently. Together they describe one terminology governance lifecycle.
Humans accept canonical terms, aliases, deprecations, scopes, and tool rules.
A git-tracked lexicon snapshot becomes the repository vocabulary used by agents and CI.
Approved organization-level terminology is mapped into a SkeinRank profile through an explicit review or import workflow.
SkeinRank binds a reviewed snapshot to a search index, application context, or runtime workflow.
Evidence and drift findings feed the next vocabulary review instead of silently mutating production language.
Responsibility split
Section titled “Responsibility split”| Layer | Agent Lexicon | SkeinRank |
|---|---|---|
| Primary scope | Repository, branch, diff, tool call | Organization, profile, index, runtime binding |
| Main user | Developer or coding agent | Search/RAG/platform team |
| State | Git-tracked lexicon + local review workspace | Profiles, bindings, evidence, snapshots |
| Decision path | Resolve, guard, lint, check merge | Canonicalize, enrich, bind, publish, roll back |
| Typical integration | CLI, CI, local MCP | SDK, REST API, governance console, Elasticsearch |
Current integration boundary
Section titled “Current integration boundary”This page describes the operating model, not an automatic synchronization service. Today:
- each product can run without the other;
- vocabulary handoff should remain explicit and reviewable;
- teams decide which repository terms belong in an organization-level runtime profile;
- the source lexicon and the runtime snapshot retain their own version and provenance.
That boundary is intentional. It prevents a newly discovered identifier in one repository from silently becoming production vocabulary everywhere.
Recommended adoption path
Section titled “Recommended adoption path”- Start with Agent Lexicon in one repository.
- Review whether naming drift is a measurable cost in pull requests or agent sessions.
- Promote stable, cross-team concepts into a SkeinRank profile.
- Bind that profile to one search or RAG context.
- Expand only after the review and rollback workflow is understood.