domain

Featured

Load the AgentOps language and bounded-context contracts when a term needs precise meaning. Triggers: "define this domain term", "check the bounded context".

AI & Automation 414 stars 40 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
87
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
68
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Domain — ubiquitous language Use this read-only library when an AgentOps term or bounded-context boundary needs precise meaning. Returning the exact contract definition works because two contexts that read the same source line cannot drift apart on a term; a paraphrase reintroduces the ambiguity the lookup exists to remove. Named failure mode — **synonym smuggling**: answering with a near-synonym ("close" for "verdict") that quietly imports lifecycle authority the term does not carry. Anti-pattern: defining a term from memory because the contract file is one read away. Corrective: always cite the definition and its source path from the live contract, even for terms you are sure about. ## Procedure 1. Read `docs/contracts/ubiquitous-language.md` for the term. 2. Read `docs/contracts/bounded-contexts.yaml` only when ownership or a port boundary matters. 3. Return the exact definition and source path. 4. Stop. Do not invent synonyms that imply lifecycle authority. In particular, Plan, Candidate, manifest, verdict, revision, strategy, and adapter are semantic terms; queue, claim, lease, close, land, release, and delivery belong to caller systems rather than AgentOps core state. Vocabulary changes are normal source edits to the two contracts above. This skill does not promote terms, mutate a knowledge index, or create continuation.

Details

Author
boshu2
Repository
boshu2/agentops
Created
8 months ago
Last Updated
today
Language
Go
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category