docs: add ubiquitous language glossary#1326
Open
TimothyJones wants to merge 1 commit into
Open
Conversation
Add UBIQUITOUS_LANGUAGE.md capturing the ContractCase domain vocabulary (contract lifecycle, consumer/provider roles, mocks, matchers, states, triggers, broker), with a relationships map, an example dialogue, and flagged ambiguities. Emphasises that consumer/provider are roles rather than client/server, so mocks and state handlers land on whichever side runs the real service (definition or verification). Link it from docs/README.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
UBIQUITOUS_LANGUAGE.md— a DDD-style glossary of the ContractCase domain vocabulary — and links it fromdocs/README.md.The glossary groups terms by contract lifecycle, services & roles, mocks, matchers, states, triggers, and distribution, plus a relationships map, an example dev↔domain-expert dialogue, and a "flagged ambiguities" section.
Key emphasis
Consumer/provider are roles, not network direction — a consumer can be an HTTP server consuming requests. Consequently mocks and state handlers are not pinned to a phase: they land on whichever side runs the real service, so a contract authored from the server side puts state handlers at contract definition, not verification.
Notes
🤖 Generated with Claude Code