BP-1233·v5.0Locked

Carrier Onboarding Master

Master Data · Shared · global, master

EP
Elena Petrova
consultant
Compliance score
20/100
Blocking gaps
2
AI suggestions
33
Open issues
22
Baseline locked— maker-checker enforced. Open a branch to propose changes.
Section · configuration_arch

Configuration Architecture

Edited 1h ago by Priya Raman·81% complete
Blueprint BP-1233 vv5.0 ├─ rule_set "release" │ ├─ window: 36h │ ├─ consolidation: enabled │ └─ equipment_policy: $ref(cfg_05) ├─ reference_data │ ├─ lane_groups: 42 │ └─ carriers: 18 ├─ choreography │ ├─ in.edi214 → normalize → publish │ └─ out.api.shipment → enrich → emit └─ governance ├─ approver_role: lead └─ baseline_lock: false
Derived configurations (0)
    Requirement traceability
    4 traced · 1 uncovered
    Req ID
    Requirement
    Priority
    Coverage
    Source
    REQ-OM-001
    Multi-leg consolidation with 36h window across NA inbound flows
    must
    covered
    Acme RFP §3.1
    REQ-OM-002
    Carrier capacity caps must respect contracted lane volume
    must
    covered
    Acme RFP §3.2
    REQ-OM-003
    Equipment policy override per shipper account
    should
    partial
    Workshop W3
    REQ-OM-004
    EDI 214 inbound normalization with event dedup
    must
    partial
    Acme RFP §5.4
    REQ-OM-005
    Role-based field masking for PII on order detail
    must
    uncovered
    Compliance Memo
    REQ-OM-006
    Demo dataset must cover EU peak-week pattern
    should
    partial
    Workshop W5
    REQ-OM-007
    Cutover playbook with rollback within 4h RTO
    must
    covered
    SOW Annex B
    REQ-OM-008
    Reuse pattern OM-STD-04 for consolidation engine
    should
    covered
    Architect Review