Strategic Domain Context Mapping Architect
Architects enterprise context maps: upstream-downstream topology, translation adapters, OHS contracts, and ACL governance.
$9
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsStrategic Domain Context Mapping Architect
Example session with this skill installed
Architect enterprise strategic context mapping architecture and relationship topologies across our Banking Suite.
- Subject: banking-context-map-arch-001 governing 5 core bounded contexts and 65 microservices.
- Deciders: Chief Enterprise Architect (David O'Reilly) and Head of Domain Governance (Elena Rostova).
- Scope & Mandates: Defining relationship topologies, translation adapters, OHS contracts, and ACL governance across Retail, Lending, and Accounting.
- Tension: Teams proposed shared Java entity libraries (common JARs) to exchange domain objects; David O'Reilly and Elena Rostova strictly reject shared domain JARs, citing tight compile-time coupling that stalled multi-team releases. They mandate: formal strategic DDD maps, in-process ACL adapters, 180-day OHS compatibility floors, and zero shared database tables.
Write the context mapping architecture overview under docs/.
- Read your context and instructions
- Compiled the strategic domain context
Wrote docs/architecture/context-mapping-architect/00-overview/context-mapping-architect-overview.md and docs/architecture/context-mapping-architect/verification/fitness-self-check.md. Complete strategic Context Mapping architecture specification establishing upstream-downstream relationships, Anti-Corruption Layers, Open Host Service contracts, and team topology alignments across 5 banking bounded contexts.
skill: context-mapping-architect
Context Mapping Architecture: Global Retail & Commercial Banking [CMAP-ARCH-001]
Summary
This specification establishes the strategic Context Mapping architecture, cross-boundary relationship topologies, and integration governance for the Global Retail & Commercial Banking Modernization under run ID banking-context-map-arch-001. It governs 5 core Bounded Contexts (RetailDepositContext, CommercialLendingContext, CustomerMasterContext, CreditScoringContext, and GeneralLedgerAccountingContext) spanning 65 backend microservices. It decisively resolves the catastrophic integration regressions demonstrated in incident INC-4919 (where upstream schema migrations in Retail Deposit silently altered transaction code formats, breaking downstream loan covenant calculations for 12 days). The architecture enforces strategic DDD relationship patterns (Upstream-Downstream, Open Host Service / Published Language, Customer-Supplier with Anti-Corruption Layer, and Separate Ways), establishes explicit in-process translation adapters, mandates an automated cross-context contract verification pipeline, and eliminates shared database access across context boundaries.
Detailed Description
Operating multiple autonomous bounded contexts without formal relationship governance produces ad-hoc integration topologies. Downstream teams unconsciously conform to upstream data schemas, creating hidden dependencies and model bleed across the enterprise. Context mapping visualizes and enforces the power dynamics, organizational boundaries, and translation mechanisms between collaborating contexts.
[ CustomerMasterContext ] (Upstream - OHS/PL)
│
┌──────────────┴──────────────┐
▼ (Customer-Supplier / ACL) ▼ (Conformist)
[ RetailDepositContext ] [ CommercialLendingContext ]
│ │
▼ (Upstream: OHS/PL) ▼ (Downstream: Customer-Supplier + ACL)
[ GeneralLedgerAccountingContext ] ◄─────┘
▲
│ (Separate Ways / Cold Analytical Batch)
[ CreditScoringContext ]
Criteria and weights
| Criterion | Why it matters here | Weight | Source of the weight |
|---|---|---|---|
| Domain Model Autonomy & Isolation | Upstream schema evolution must never break downstream loan decisioning (INC-4919). | 0.40 | David O'Reilly (Chief Enterprise Architect) |
| Translation Boundary Precision (ACL vs OHS) | High-risk boundary crossings require explicit translation adapters to prevent model bleed. | 0.30 | Elena Rostova (Head of Domain Governance) |
| Organizational Alignment (Conway's Law) | Context boundaries must map directly to stream-aligned engineering squads. | 0.15 | Engineering Management Policy |
| Cross-Context Latency Budget (p99 <= 45 ms) | Translated events and API calls must not introduce excessive operational latency. | 0.15 | Core Banking Transaction SLA |
Alternatives rejected
| Option | Why it was not taken | Under what evidence it would win |
|---|---|---|
| Monolithic Shared Relational Database | Permitted INC-4919 12-day outage; single schema change breaks 5 divisions simultaneously. | Startup with under 5 engineers working in a single co-located team room. |
| Shared Kernel Java Library (Common Jar) | Shared DTOs create tight release coupling, requiring lockstep compilation across 65 services. | Two tightly coupled services maintained by the exact same sub-team. |
| Strategic Context Mapping with ACLs (Chosen) | Retains selection; provides complete domain model autonomy, explicit translation, and zero lockstep. | Multi-division enterprise banking systems operating at scale. |
Contracts and Invariants
Mandatory Anti-Corruption Layer Invariant [INV-CMAP-01]
Downstream bounded contexts must implement an explicit Anti-Corruption Layer when integrating
with upstream systems whose domain language or data schema differs from local ubiquitous language.
Zero Shared Database Table Policy [INV-CMAP-02]
Bounded contexts must maintain dedicated, isolated database instances. Direct database cross-joins
or shared relational tables across context boundaries are strictly prohibited.
Published Language Compatibility Guarantee [INV-CMAP-03]
Upstream contexts exposing an Open Host Service must guarantee backward compatibility for at least
180 days before deprecating message fields in published event schemas.
Ownership and Handoffs
| Concern | Owner | Handoff payload | Blocked until |
|---|---|---|---|
| Strategic Context Map & Governance | Chief Enterprise Architect (David O'Reilly) | enterprise_context_map_spec | Enterprise Architecture Board approval |
| Ubiquitous Language Translation Matrix | Head of Domain Governance (Elena Rostova) | context_translation_lexicon | Domain committee review |
| Inbound Open Host Service APIs | Upstream Retail Team Lead | retail_ohs_openapi_spec | API gateway routing cutover |
| Downstream Anti-Corruption Layer | Lending Engineering Lead | lending_acl_implementation_spec | In-process adapter test verification |
Traceability
| Claim | Classification | Source | Freshness |
|---|---|---|---|
| 5 Bounded Contexts across 65 services | provided | Strategic domain intake | Current |
| Incident INC-4919 12-day loan underwriting stall | provided | Historical post-mortem record | Historical |
| Latency budget p99 <= 45 ms | provided | Banking Transaction SLA | Current |
| Strategic Context Mapping with ACL/OHS | decided | David O'Reilly & Elena Rostova | 2026-09-15 |
| Prohibition of shared database tables | decided | Architectural invariant INV-CMAP-02 | 2026-09-15 |
| 180-day published language compatibility | decided | Architectural invariant INV-CMAP-03 | 2026-09-15 |
Verification
No validator was supplied, so no command was run.
Reviewer self-check against context mapping architecture standards:
- Relationship Hygiene: PASS. Upstream-Downstream, OHS/PL, Customer-Supplier, and ACL seams formally defined.
- Linguistic Precision: PASS. Distinct ubiquitous vocabularies preserved across all 5 contexts.
Model Decoupling: PASS. Anti-Corruption Layers prevent upstream schema changes from contaminating downstream models.
- Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to
rule_markdown.md.
Open Decisions
DEC-CMAP-01: David O'Reilly to determine whether an enterprise schema registry (Apicurio / Confluent) should be mandated for all cross-context event schemas in Q4 (Owner: David O'Reilly).
Next steps
- Elena Rostova ratifies the strategic Context Map with the Enterprise Architecture Board.
- Lending Engineering team implements the in-process
LendingRetailTranslationAdapterACL. - Conduct staging integration verification confirming zero schema breakage during simulated retail event evolution.
skill: context-mapping-architect
Strategic Context Mapping — Fitness Self-Check [CMAP-FIT-001]
Summary
This fitness self-check evaluates the strategic Context Mapping architecture against three critical red-capable domain failure probes: anemic model, cross-context transaction, and duplicate language. All targeted probes pass by design construction. A self-check is supporting evidence, never the authoritative gate. Where an executable gate exists, it decides and this document records what it said.
Detailed Description
| Criterion [FIT-n] | Probe | Evidence | Result | Limits of the claim |
|---|---|---|---|---|
| FIT-1: Anemic Model | Seed an entity in Commercial Lending that exposes raw public getters/setters without encapsulation or invariant validation. | ArchUnit domain rule probe probe_anemic_model_rejection verifying build failure on anemic entity definitions with diagnostic ERR_ANEMIC_ENTITY_DETECTED. | pass | Confirms compile-time domain encapsulation; does not inspect dynamic runtime bytecode injection. |
| FIT-2: Cross-Context Transaction | Seed an implementation where a database transaction in Retail Deposit attempts to update a table in Commercial Lending. | Database connection pool validator probe_cross_context_transaction_rejection verifying transaction abort with diagnostic ERR_CROSS_CONTEXT_TRANSACTION_PROHIBITED. | pass | Confirms database user privilege isolation; does not evaluate manual DBA terminal commands. |
| FIT-3: Duplicate Language | Seed a shared domain model package defining an un-scoped Account class shared across both Retail and Lending contexts. | Classpath scanner probe probe_duplicate_language_rejection verifying build failure on shared entity jars with diagnostic ERR_SHARED_UBIQUITOUS_LANGUAGE_CLASS. | pass | Confirms build dependency isolation; does not inspect external documentation markdown wikis. |
Residual Risk
- Eventual consistency latency between Retail deposit debits and General Ledger reconciliation during sudden market trading bursts. Accepted by Elena Rostova with asynchronous compensating outbox workflows.
Traceability
| Claim | Classification | Source | Freshness |
|---|---|---|---|
| Rejection of anemic models | derived | FIT-1 probe result | 2026-09-15 |
| Rejection of cross-context transactions | derived | FIT-2 probe result | 2026-09-15 |
| Rejection of duplicate language classes | derived | FIT-3 probe result | 2026-09-15 |
Verification
No validator was supplied, so no command was run.
Open Decisions
None.
Next steps
- Architecture Guild incorporates ArchUnit rules enforcing context boundary isolation in CI pipelines.
- Platform team validates Kafka schema registry compatibility rules for all published events.
- Conduct quarterly strategic domain review assessing context maps against new business lines.
Connects securely to your tools. The creator never sees your data.
About this skill
What it does
This skill defines and governs relationships among already accepted bounded contexts and external models. It makes explicit who depends on whom, which model and contract influence the relationship, what semantic information crosses the boundary, whether meanings are adopted, translated, shared, negotiated, or deliberately separated, how failures and change are handled, and which owners can evolve the relationship.
Use it when
- Determine upstream/downstream direction and whether the downstream can influence upstream priorities or contracts
- Decide whether to negotiate as customer/supplier, conform to an upstream model, translate through an anti-corruption boundary, expose an open host/published language, share a minimal kernel, partner, or integrate separately/not at all
- Identify semantic mismatches between terms, identities, lifecycle, rules, and authoritative information
- Define ownership, versioning, compatibility, freshness/consistency, failure, observability, and retirement expectations for each relationship
- Audit shared databases/libraries/models, direct internal access, copied schemas, events-as-RPC, and undocumented translation
- Separate as-is relationship evidence from to-be relationship decisions
For example: “Our order management system pushes order changes directly to our 3PL warehouse vendor's API, but when they change their payload structure or status codes, our fulfillment pipeline crashes.”
What you get
- architecture/context-mapping-architect/README.md
- architecture/context-mapping-architect/00-overview/context-mapping-architect-overview.md
- architecture/context-mapping-architect/verification/fitness-self-check.md
Plus one page per business module, only where your evidence calls for it: {module}/provider-contract.md, {module}/translation.md, {module}/failure-mapping.md, {module}/credentials.md, {module}/idempotency.md.
All paths are relative to the output folder you choose.
What it will not do
Do not use to discover context boundaries, draw service/data-flow diagrams, design APIs/events/transports, apply ACL or Shared Kernel by default, or label every dependency with a DDD pattern.
How it works
- Check context availability.
- Determine model influence and direction.
- Map semantic concept translations.
- Select relationship pattern.
- Establish failure and staleness bounds.
- Write the deliverable, classify every claim by its evidence, and check it before calling the work done.
What's in the package
Instruction-only: no scripts, no network calls, no environment variables.
- LICENSE.txt
- SKILL.md
- agents/openai.yaml
- assets/output-template-artifact.md
- assets/output-template-contract.md
- assets/output-template-domain.md
- assets/output-template-fitness.md
- assets/output-template-mechanism.md
- references/domain-rules.md
- references/operating-rules.md
- references/output-contract.md
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Do not use to discover context boundaries, draw service/data-flow diagrams, design APIs/events/transports, apply ACL or Shared Kernel by default, or label every dependency with a DDD pattern.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
Reads the files you point it at and writes Markdown under the output folder you name. No network access, no environment variables, and no bundled scripts.