Governance
Enterprise Alignment
Compliance verification against enterprise architecture principles, Gold standards, and integration patterns. Documents where the transformation aligns and where deviations are required.
Why this matters
Enterprise architecture compliance is a gate for programme funding. Deviations require documented rationale and approval. Alignment reduces review friction and accelerates approvals.
What this informs
Steering committee confidence, deviation approval process, and architecture review board submission.
What remains unresolved
Disaster recovery design pending infrastructure partner. Cost chargeback model requires finance alignment.
Principles
6
Aligned
4
Partial
3
Under Review
1
Deviations
2
Architecture serves the business, not the other way around
Every architectural decision is justified by a business outcome. Technology choices follow business capability needs, not vendor roadmaps or technical preference.
Interoperability by default
All systems expose well-defined APIs. Integration is a first-class architectural concern, not an afterthought. Data flows are documented, governed, and observable.
Observability and control
Every component emits health signals. Logging, tracing, and metrics are mandatory, not optional. Operational visibility is a prerequisite for production readiness.
Scalability and modularity
Components scale independently. Boundaries are drawn along business domains, not technology layers. A module can be replaced without cascading changes.
Domain-driven design
Service boundaries follow business domains. Data ownership is explicit. Bounded contexts prevent cross-domain coupling. Ubiquitous language is shared between business and technology.
Enterprise-aligned by design
Solutions align with enterprise architecture standards, security policies, and governance frameworks. Deviations are documented as architecture decisions with clear rationale.
| Requirement | Category | Status | Notes |
|---|---|---|---|
| API-first integration pattern | Integration | aligned | All new services will expose RESTful APIs. Facade layer provides API boundary for legacy. |
| Centralised identity and access management | Security | aligned | Enterprise SSO integration planned for Phase 1. Service accounts via OAuth 2.0. |
| Data classification and handling | Data | partial | Classification framework defined. China data sovereignty requires separate handling procedures. |
| Cloud-first deployment | Infrastructure | aligned | Composable architecture designed for cloud-native deployment. China requires separate cloud provider. |
| Observability baseline | Operations | partial | OpenTelemetry recommended. Full observability stack selection pending ADR-005 implementation. |
| Disaster recovery and business continuity | Operations | under-review | DR requirements defined. Multi-region failover design depends on infrastructure partner selection. |
| Cost transparency and chargeback | Governance | partial | Cost model defined at domain level. Chargeback mechanisms require finance team alignment. |
| Vendor exit strategy | Procurement | aligned | Composable architecture inherently supports vendor substitution. API contracts are vendor-agnostic. |
China data sovereignty requires separate cloud infrastructure
ApprovedEnterprise standard is single cloud provider globally. China operations require a China-approved provider (Alibaba Cloud, Tencent Cloud, or Huawei Cloud) for regulatory compliance. Architecture review board approved this deviation on 2026-03-18.
WeChat Mini Program as primary mobile channel in China
Pending approvalEnterprise standard is native app for mobile experiences. China market dynamics require WeChat Mini Program as the primary interface. Deviation documentation submitted to architecture review board.
Enterprise Integration Pattern Alignment
How the proposed composable architecture maps to the enterprise integration standards and approved patterns.
DraftEnterprise Architect
Decision Layer
Decisions Supported
ADR-005 (observability), ADR-006 (SAP retention). Alignment report validates architecture choices against enterprise standards.
Dependencies
Depends on future-state scenario selection. Deviation approvals depend on architecture review board schedule.
Next Actions
Submit deviation documentation for WeChat. Complete DR design when infrastructure partner is selected. Align cost model with finance.
Confidence
Medium — majority of requirements aligned. Two deviations documented, one approved, one pending.