Command and service contracts
Updated: 2026-04-30
Status: beta
Owner: Regents CLI
Short answer
Section titled “Short answer”Regents uses published command and service rules before product behavior changes. These rules keep product pages, agents, operators, and the regents command aligned.
Canonical definition
Section titled “Canonical definition”A Regent command or service contract is the current published rule for what a product command or service may accept, return, and require.
Why it matters
Section titled “Why it matters”Agents and operators need one current rule for each public action. Without that rule, a command can say one thing while a product page does another.
How it works in Regents
Section titled “How it works in Regents”Each product owns its own public service rules. Regents CLI owns the shipped command surface. When a product action changes, the owning rule changes first, then product pages, agent paths, command behavior, examples, and tests are updated to match that one rule.
Regents keeps only the current shape. Old shapes are removed instead of being carried beside the current one.
Example
Section titled “Example”If a Techtree publishing command gains a new required field, the Techtree rule and the Regents CLI command rule change first. The page, command, examples, and checks then use that current field everywhere.
What this does not claim
Section titled “What this does not claim”This page does not list every command or service action. It explains the rule that keeps them aligned.
Related concepts
Section titled “Related concepts”What wins if a page and command disagree?
Section titled “What wins if a page and command disagree?”The owning product contract wins for product behavior. The command surface must be updated to match it.
Why remove old shapes?
Section titled “Why remove old shapes?”One current shape is easier for people and agents to trust.