Architecture
AuraScore 81/100

Multimodal Freight Integration and Data Fabric Architecture

Architect an enterprise integration fabric for multimodal freight data exchange, customs processing, and partner EDI/API harmonization.

Use this template when architecting global supply chain integration platforms connecting ocean, rail, air, and road carriers. It generates an enterprise data fabric architecture report emphasizing standard harmonization and compliance.

Template

Role: Principal Enterprise Integration Architect specializing in multimodal supply chain logistics.

Context

  • Active transportation modes: {{freight_modalities}}
  • Carrier & partner interface standards: {{edi_and_api_standards}}
  • Trade and customs compliance mandates: {{regulatory_compliance_mandates}}
  • Enterprise integration baseline: {{integration_middleware_stack}}
  • Partner onboarding target SLA: {{partner_onboarding_sla}}
  • Continuity and disaster recovery targets: {{disaster_recovery_rpo_rto}}

Task

Author a comprehensive enterprise architecture report detailing a resilient multimodal data fabric that unifies asynchronous EDI, modern REST/JSON webhooks, customs compliance pipelines, and end-to-end milestone tracking.

Method

  1. Define canonical data models (CDM) that normalize disparate schemas across {{freight_modalities}} into standard logistics milestones.
  2. Design the translation and transformation layer supporting legacy EDI standards and modern API interfaces specified in {{edi_and_api_standards}}.
  3. Architect automated validation and enrichment pipelines for customs documentation to guarantee compliance with {{regulatory_compliance_mandates}}.
  4. Design a self-service partner integration portal architecture to radically accelerate {{partner_onboarding_sla}} through automated testing harnesses.
  5. Model the event-driven integration backbone using {{integration_middleware_stack}}, covering message deduplication, schema validation, and routing.
  6. Detail data governance, master data management (MDM) for locations/carriers, and audit trail immutability.
  7. Architect cross-region disaster recovery and zero-loss failover topologies satisfying {{disaster_recovery_rpo_rto}}.

Constraints

  • MUST define a schema canonicalization strategy that isolates internal systems from external partner format changes.
  • MUST NOT permit unvalidated partner payloads to enter the internal integration event bus.
  • MUST specify end-to-end distributed tracing across protocol translations (e.g., AS2 to Kafka to REST).
  • Architectural recommendations must strictly utilize {{integration_middleware_stack}} capabilities.

Output format

Deliver an advanced enterprise architecture integration report containing:

  1. Canonical Data Fabric & Domain Model Topology
  2. B2B Gateway & Partner Interface Architecture (EDI/AS2/API)
  3. Customs & Compliance Pipeline Specification
  4. Partner Onboarding & Automated Certification Harness Design
  5. Master Data Governance & Observability Framework
  6. High Availability, Failover & Disaster Recovery Plan

Self-review

  • Confirm that all modalities in {{freight_modalities}} have defined milestone translation mappings.
  • Verify that the disaster recovery design mathematically achieves {{disaster_recovery_rpo_rto}}.
  • Check that the partner onboarding workflow directly addresses the target SLA set in {{partner_onboarding_sla}}.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-architecture
transport-logistics
freight-logistics
data-fabric
edi-integration