docs(ddd): publish context map, ubiquitous language, and tactical model - #273
docs(ddd): publish context map, ubiquitous language, and tactical model#273seonghobae wants to merge 18 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…to codex/pr273-restack Signed-off-by: Seongho Bae <me@seonghobae.me> # Conflicts: # docs/traceability/mcp-authority-route.md
|
Restacked on parent PR #272 exact head fe124e4 without force-pushing. The updated traceability document preserves the parent request-envelope and executable RED/repair evidence, then adds the DDD ownership boundary for core, MCP adapter, and protocol-independent policy. Exact child head e5c8fcb evidence: 159 Python repository contracts passed; cargo fmt, workspace tests, strict Clippy, and rustdoc passed; fresh-worktree production function/line/region/branch coverage is 100%. Relative to the parent, the PR remains five DDD documentation/contract files. This PR remains draft. |
Scope
DDD documentation child of PR #272. It records the strategic Context Map, ubiquitous language and truthful tactical DDD classification without turning MCP, WebDriver BiDi, or persistence adapters into core authority.
The executable fitness contract parses the actual
originweave-core,originweave-policy, andoriginweave-mcpCargo manifests. Core/policy may not depend outward on MCP; policy depends inward on core; the MCP adapter depends inward on core and policy. Current identifiers such asBrowserSessionId,BrowsingContextId,Origin, andDocumentEpochremain Value Objects unless lifecycle/identity semantics in code justify Entity/Aggregate classification. No Aggregate Root, persistence Repository, or OriginWeave Domain Event is invented merely to fill a diagram.browsingContext.navigationCommittedremains an adapter integration event until adopted through the owning browser-domain boundary, and command ACK is not post-condition proof.Parent-first state
A concurrent non-force update advanced this child to exact
e5c8fcb66bf644dfa750bb1b40ba3d600cb7805a; it remains open, Draft, and mergeable. Its GitHub base branch isfix/ddd-mcp-adapter-boundary, but the stored base generation is predecessor parentfe124e447cad3f679e22337fb6fbdfd135ab3652.Live parent #272 has since been non-destructively reconciled onto protected
main@87c4daa1830bac5a5228b6036752ad5633232085and is exactb1cae8ad1cbd8eb6992037c830aea30b9aa436b3, Ready and behind 0. Fresh parent→child comparison is therefore intentionally diverged: child ahead 18 / behind 5, merge basefe124e447cad3f679e22337fb6fbdfd135ab3652. The effective child-owned delta remains exactly five paths:docs/context-map.md,docs/tactical-ddd-map.md,docs/ubiquitous-language.md,docs/traceability/mcp-authority-route.md, andtests/test_ddd_documentation_contract.py.The parent reconciliation preserves #286's protected CI/MV3 lifecycle controls, keeps
.github/**out of the effective #272 delta, and separates MCP-specific repository assertions into a focused contract. Predecessor parentfe124e...had GREEN native CI/MV3, but those results do not transfer. The firstready_for_reviewevent on reconciled predecessor975492b1...reproduced #279's #286 defect by completing native CI/MV3 asskipped; current parentb1cae8ad...was then synchronized while Ready and has fresh exact-head CI/MV3/Security/Semgrep/CodeQL runs materialized. They are non-terminal at the current observation point.Do not reconstruct this child until unchanged #272
b1cae8ad...has terminal required evidence. Once the parent is verified, rebuild this child non-destructively on that exact parent and retain only the five validated documentation/fitness paths above; then rerun the Cargo dependency-direction DDD fitness and documentation contracts on the reconstructed exact child head. If protected main or the parent moves first, read and adopt the intervening delta rather than force-rebasing.Protected-main
AGENTS.mdand live governance remain authoritative. No self-approval, bypass, force-push, destructive rebase, workflow/ruleset/secret mutation, gate weakening, tag, release, or publish is authorized here.