Strategic Domain Context Mapping Architect

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

Alternatives rejected

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

Traceability

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

1. Elena Rostova ratifies the strategic Context Map with the Enterprise Architecture Board.
2. Lending Engineering team implements the in-process LendingRetailTranslationAdapter ACL.
3. 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

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

Verification

No validator was supplied, so no command was run.

Open Decisions

None.

Next steps

1. Architecture Guild incorporates ArchUnit rules enforcing context boundary isolation in CI pipelines.
2. Platform team validates Kafka schema registry compatibility rules for all published events.
3. Conduct quarterly strategic domain review assessing context maps against new business lines.