AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — ERP-to-WMS Event Schema, Idempotency Keys, and Exception Queue Design

Document ID: L0254 · Cluster Domain: AI Yard Appointment Triage vs. Dock Door Locks · Funnel Stage: TOFU · Target Reader: Supply Chain CIOs, Enterprise Integration Architects & VP of Supply Chain Systems Primary Focus Keywords: ai yard gate appointment triage erp integration, ai yard gate appointment triage, ai yard gate appointment triage software

---

Data Ownership Failure Modes in Split-Brain AI Yard Appointment Triage vs. Dock Door Locks Landscapes

This technical integration and data-ownership blueprint for AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — ERP-to-WMS Event Schema, Idempotency Keys, and Exception Queue Design (L0254) specifies the exact system-of-record boundaries, canonical data objects, idempotency keys, and message choreography required to govern ai yard gate appointment triage erp integration. When Warehouse Management Systems (WMS), Transportation Management Systems (TMS), Distributed Order Management (DOM), and core ERP ledgers exchange state updates without strict sequence locks, split-brain inventory and duplicate financial postings become inevitable.

At the core of this operational domain lies a non-negotiable engineering principle: Governing AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks across Joliet (IL), Haslet (TX) & Inland Empire (CA) High-Velocity Yard & Cross-Dock Hubs and Bhiwandi, Pataudi (NCR) & Sriperumbudur Mega Logistics Parks requires replacing post-facto spreadsheet reconciliation with deterministic state-transition gates (ARRIVAL CLASSIFIER → BOUNDED PLANNER → YMS INTERLOCK → DWELL CLOCK LOCK → ZERO FALSE DETENTION) that hard-lock physical edge capture to statutory filings and ERP sub-ledger settlement. Whenever organizations allow physical warehouse, yard, port, or transit execution to advance faster than digital state verification, the gap between what occurred on the floor and what is recorded in the enterprise ledger widens into structural financial leakage.

The Three Structural Failure Modes of Uncontrolled Execution

In live production audits across Joliet (IL), Haslet (TX) & Inland Empire (CA) High-Velocity Yard & Cross-Dock Hubs and Bhiwandi, Pataudi (NCR) & Sriperumbudur Mega Logistics Parks, three recurring failure modes explain why legacy SOPs and passive visibility dashboards fail to control AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks:

1. Unverified Physical-to-Digital Handover: An AI yard-scheduling agent automatically reassigns a late-arriving refrigerated load to Dock Door 14 based on ETA predictions, unaware that Dock Door 14 is an ambient-only door without cold-seal cushions or lacks hazardous-material containment.
2. Asynchronous Exception Discovery & Commercial Lag: Auto-rescheduling a late inbound carrier into an outbound staging window starves the outbound wave of forklift labor and causes three on-time parcel linehaul trailers to miss their hub sort cutoffs.
3. Split-Brain State & Statutory Desynchronization: Verbal or AI-chat appointment changes fail to stamp whether the reschedule was CARRIER_FAULT_LATE vs. SHIPPER_DOCK_CONGESTION, allowing the carrier to bill $250 in detention from their original scheduled time rather than their actual gate-in time.

Core Control Thesis (L0254): You cannot fix a missing physical control gate at 01 · ETA & GATE ANPR (ARRIVAL CLASSIFIER) or 02 · AI SLOT ADVISOR (BOUNDED PLANNER) with an accounting spreadsheet or an LLM chatbot at month-end. Deterministic execution locks must fire at the exact millisecond of physical custody or state transfer, while bounded AI agents (DWELL CLOCK LOCK) accelerate exception evidence assembly for accountable human sign-off (ZERO FALSE DETENTION).

---

End-to-End Integration Topology and Message Sequence Flow

To eliminate silent state drift across AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks, the execution architecture enforces five sequential control gates linking edge hardware capture (Gate ANPR/OCR cameras, RFID tractor/trailer tags, dock-door vehicle restraint interlocks (Rite-Hite/Dok-Lok), MHE forklift terminals, and real-time ELD/GPS ETA feeds) and bilateral protocol exchanges (ASC X12 EDI 214 (Carrier ETA & Appointment Status), EDI 204/856, Yard Management System (YMS) dock schedules, and India ULIP FASTag / e-Way Bill validity-window logs) directly to the ERP financial sub-ledger:

Stage-by-Stage Control Gate Walkthrough

• 01 · ETA & GATE ANPR (ELD / FASTag + Camera): Captures primary physical telemetry (US: EDI 214 + Gate OCR in the US; IN: FASTag + ANPR Timestamp in India) and enforces ARRIVAL CLASSIFIER via two hard predicates: |t_in - t_appt| <= 15m? and Stamps ON_TIME vs WORK_IN. No downstream document or wave release can initialize until this gate commits.
• 02 · AI SLOT ADVISOR (Candidate Door Ranking): Validates commercial and statutory dispatch/execution prerequisites (US: Scores Yard Shunts; IN: Checks E-Way Expiry) under BOUNDED PLANNER. The system verifies Proposes Work-In Window and Cannot Unlock Dock Restraint before opening the physical yard gate, releasing the pick wave, or transmitting the customs/carrier filing.
• 03 · DOOR & CREW GATE (Physical & Labor Lock): Evaluates in-transit, receiving, or billing settlement events (US: TempZone + OSHA Lock; IN: Bay Height + MHE Crew) through YMS INTERLOCK. Whenever Protects Outbound Cutoffs or Verifies Crew Capacity detects a deviation outside tolerance, the transaction is bifurcated—isolating the disputed variance while preserving flow for verified units.
• 04 · DOCK EXECUTION (Restraint & Scan Timers): Invokes DWELL CLOCK LOCK (US: Dok-Lok Engage -> Release; IN: Chock Lock + GRN Scan) to correlate multi-source logs, photos, and tariff clauses (Logs Exact Unload Window). Critically, this layer enforces Forfeits Late Carrier Claim—the AI agent has zero write authority over operational locks or general-ledger tables.
• 05 · DETENTION AUDIT (TMS / ERP AP Sync): Finalizes the three-way tie-out (US: Feeds EDI 210 Gate; IN: Feeds Halting Bill Gate) under ZERO FALSE DETENTION, executing 100% Timestamp Backed and Immutable Yard Ledger only after cryptographic and human controller sign-off criteria are satisfied.

---

Mathematical Invariants for Cross-System Reconciliation: Equipment-Compatible Dock-Door Assignment & Fault-Stamped Detention Clock Reset

Replacing subjective operator judgment with deterministic software locks in AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks requires explicit mathematical formulations embedded inside WMS / TMS Execution Engine and ERP Financial Sub-Ledger. Below is the complete three-part Equipment-Compatible Dock-Door Assignment & Fault-Stamped Detention Clock Reset governing ai yard gate appointment triage erp integration:

1. Hard Dock-Door Physical Compatibility & Labor Constraint

$$\text{Feasible}(l, d, \tau) = \mathbb{I}(\text{TempZone}(l) = \text{TempZone}(d)) \cdot \mathbb{I}(\text{Height}(l) \le \text{Clearance}(d)) \cdot \mathbb{I}\left(\sum_{d' \in \mathcal{Z}(d)} M_{d'}(\tau) + m_l \le M_{\text{max},\mathcal{Z}}(\tau)\right)$$

Operational Interpretation & Gate Enforcement: Ensures that load $l$ can be assigned to dock door $d$ in slot $\tau$ only if temperature-zone and trailer-height physical constraints match AND total required MHE/forklift operators $M_{d'}(\tau) + m_l$ in dock zone $\mathcal{Z}(d)$ do not exceed shift crew capacity $M_{\text{max},\mathcal{Z}}(\tau)$. In production deployments across Joliet (IL), Haslet (TX) & Inland Empire (CA) High-Velocity Yard & Cross-Dock Hubs and Bhiwandi, Pataudi (NCR) & Sriperumbudur Mega Logistics Parks, this equation is evaluated synchronously at ARRIVAL CLASSIFIER and BOUNDED PLANNER before any physical movement or external message transmission is committed.

2. Detention Free-Time Clock Reset Under Late Carrier Arrival

$$t_{\text{detention-start}}(l) = \begin{cases} \max(t_{\text{gate-in}},\; t_{\text{appt}}) + T_{\text{free}} & \text{if } t_{\text{gate-in}} \le t_{\text{appt}} + \delta_{\text{grace}} \text{ (On-Time Arrival)} \\ t_{\text{actual-dock-assign}} + T_{\text{free}} & \text{if } t_{\text{gate-in}} > t_{\text{appt}} + \delta_{\text{grace}} \text{ (Work-In Status)} \end{cases}$$

Operational Interpretation & Gate Enforcement: When a carrier arrives past the appointment grace window $\delta_{\text{grace}}$ (typically 15–30 minutes), the load enters WORK_IN_LATE_ARRIVAL status, forfeiting the original appointment detention clock and resetting free time $T_{\text{free}}$ to actual dock placement. By evaluating this expression automatically within DeterministicStateLock / ControlGateLedger and CompliancePayloadRecord (ASC X12 / GSTN-ULIP), the platform eliminates manual spreadsheet guesswork and immediately quantifies the financial or operational exposure at YMS INTERLOCK.

3. Drop-and-Hook Yard Jockey Shunt Optimization

$$\min \sum_{j \in \mathcal{J}} \left(c_{\text{travel}} \cdot d(y_l, d) + P_{\text{outbound-cutoff}}(d, \tau)\right)$$

Operational Interpretation & Gate Enforcement: Allows the AI yard advisor to rank candidate yard spots $y_l$ and shunt sequences for yard hostlers while protecting outbound carrier cutoff doors. This binary/threshold predicate serves as the hard interlock for ZERO FALSE DETENTION, ensuring that ThreeWaySettlementMatch & VarianceHoldQueue never releases an unverified settlement or corrupts inventory/cost valuation.

---

Canonical Data Objects, Primary Keys, and Write-Authority Matrix

In a distributed supply chain landscape governing AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks, integration failures rarely stem from network downtime; they stem from ambiguous write authority and missing idempotency guarantees across Edge Capture & Telemetry Layer, WMS / TMS Execution Engine, Statutory & EDI Messaging Hub, ERP Financial Sub-Ledger. The matrix below defines the canonical data contract for every integration boundary:

Event-Driven Integration Invariants

1. Strict Monotonic State Versioning (StateVer): Every state mutation on DeterministicStateLock / ControlGateLedger increments a monotonically increasing integer StateVer. If an asynchronous webhook or EDI message arrives with msg.StateVer <= current.StateVer, the integration broker drops the duplicate payload and logs an idempotent no-op rather than regressing state.
2. Bi-Directional Checksum Binding: Outbound statutory and commercial documents (ASC X12 EDI 214 (Carrier ETA & Appointment Status), EDI 204/856, Yard Management System (YMS) dock schedules, and India ULIP FASTag / e-Way Bill validity-window logs) embed a cryptographic hash of the underlying ImmutableScanEvent / DeviceTelemetryPacket line items. When the counterparty returns an acknowledgment or invoice (US: TempZone + OSHA Lock / IN: Bay Height + MHE Crew), YMS INTERLOCK verifies that the line-item hash and unit totals match before permitting ZERO FALSE DETENTION.

---

Idempotent API, ASC X12 EDI, and India ULIP/GSTN Payload Contracts

To guarantee zero message loss and zero duplicate processing across AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks, integration architects must enforce strict payload contracts across both US (FMCSA 49 CFR § 395.3 (driver Hours of Service 14-hour on-duty window and coercion prohibition under 49 CFR § 390.6)) and Indian (CGST Rule 138(10) (NIC e-Way Bill validity window—200 km per day for normal cargo; mandatory extension within 8 hours before/after expiry if yard congestion delays unloading across midnight)) data exchanges:

Canonical Event Envelope & Idempotency Specification

Every asynchronous message exchanged between Edge Capture & Telemetry Layer, WMS / TMS Execution Engine, Statutory & EDI Messaging Hub, and ERP Financial Sub-Ledger must carry the following deterministic header fields:

• event_id: UUIDv7 (time-ordered) generated at the physical capture edge.
• idempotency_key: Deterministic SHA-256 digest of (tenant_id + entity_id + stage_code + state_version + capture_hash).
• stage_gate: Enumerated stage identifier (STAGE_01_ARRIVAL_CLASSIFIER through STAGE_05_ZERO_FALSE_DETENTION).
• market_regime: US_FEDERAL_COMMERCIAL (US: Scores Yard Shunts / US: TempZone + OSHA Lock) or IN_STATUTORY_GST_ULIP (IN: Checks E-Way Expiry / IN: Bay Height + MHE Crew).
• verification_predicates: Boolean assertion map confirming |t_in - t_appt| <= 15m?, Proposes Work-In Window, and Protects Outbound Cutoffs before ThreeWaySettlementMatch & VarianceHoldQueue accepts the posting.

---

Dead-Letter Queue Triage, Out-of-Order Event Handling, and AI Schema Mapping

A defining architectural requirement across all modern supply chain implementations is the strict separation between deterministic transactional locks and bounded AI orchestration:

• Deterministic Execution Engine (WMS / TMS Execution Engine & ERP Financial Sub-Ledger): Owns all state transitions across ImmutableScanEvent / DeviceTelemetryPacket, DeterministicStateLock / ControlGateLedger, CompliancePayloadRecord (ASC X12 / GSTN-ULIP), and ThreeWaySettlementMatch & VarianceHoldQueue. It evaluates Equipment-Compatible Dock-Door Assignment & Fault-Stamped Detention Clock Reset with zero probabilistic variance and enforces ARRIVAL CLASSIFIER, BOUNDED PLANNER, YMS INTERLOCK, and ZERO FALSE DETENTION.
• Bounded Read-Only AI Layer (04 · DOCK EXECUTION · DWELL CLOCK LOCK): Operates exclusively on read-replicas and unstructured document stores. When YMS INTERLOCK flags an exception (Protects Outbound Cutoffs), the AI layer executes Logs Exact Unload Window—parsing OCR PDFs, matching dock/yard camera frames, extracting relevant clauses from FMCSA 49 CFR § 395.3 (driver Hours of Service 14-hour on-duty window and coercion prohibition under 49 CFR § 390.6) or CGST Rule 138(10) (NIC e-Way Bill validity window—200 km per day for normal cargo; mandatory extension within 8 hours before/after expiry if yard congestion delays unloading across midnight), and pre-populating a structured exception brief.
• Immutable Guardrail (Forfeits Late Carrier Claim): The AI agent service principal is denied database INSERT, UPDATE, or DELETE privileges on inventory balances, rate cards, customs filings, and ERP AP/AR sub-ledgers. Every commercial claim, tariff override, or statutory filing requires explicit cryptographic sign-off by the designated human role owner.

---

Dual-Market Integration Stress Test: Worked US ($) and India (₹) Payload Reconciliation

To ground AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — ERP-to-WMS Event Schema, Idempotency Keys, and Exception Queue Design in concrete operational economics, the worked scenarios below trace how deterministic control gates eliminate structural leakage in both a high-volume United States corridor and a high-velocity Indian logistics network:

United States Worked Scenario (Joliet (IL), Haslet (TX) & Inland Empire (CA) High-Velocity Yard & Cross-Dock Hubs)

• Facility & Operating Profile: 750,000 sq. ft. food & beverage distribution center in Joliet, IL with 68 dock doors handling 115 inbound/outbound truck appointments per day.
• Baseline Throughput & Financial Footprint: 3,450 truck appointments/month (18% arrive > 30 mins outside scheduled window = 621 reschedules/month).
• Pre-Control Legacy Failure & Leakage: Chaotic radio-based dock reassignments and unrecorded 'work-in' timestamps result in $21,800/month ($261,600/year) in invalid carrier detention payouts and missed outbound wave cutoffs.
• Deterministic Control-Gate Intervention & Verified Outcome: Using an AI ETA agent to propose work-in slots while enforcing hard YMS door-compatibility, forklift-capacity, and WORK_IN_LATE detention-reset locks saves $20,200/month ($242,400/year).
• Statutory & Protocol Audit Trail: Full alignment across FMCSA 49 CFR § 395.3 (driver Hours of Service 14-hour on-duty window and coercion prohibition under 49 CFR § 390.6), OSHA 29 CFR 1910.178(k) & (m) (powered industrial truck wheel chocks and dock-lock vehicle restraints before forklift entry), and standard MTSA work-in detention clauses., linking ImmutableScanEvent / DeviceTelemetryPacket (US: EDI 214 + Gate OCR) through ThreeWaySettlementMatch & VarianceHoldQueue (US: Feeds EDI 210 Gate).

India Worked Scenario (Bhiwandi, Pataudi (NCR) & Sriperumbudur Mega Logistics Parks)

• Facility & Operating Profile: 500,000 sq. ft. FMCG & retail park in Bhiwandi with 44 dock bays managing 95 daily FTL placements and inbound receipts.
• Baseline Throughput & Financial Footprint: 2,850 truck movements/month (₹36,40,000/month yard detention/halting & labor overtime baseline).
• Pre-Control Legacy Failure & Leakage: Manual gate registers fail to separate late transporter arrival from warehouse unloading delays, leaking ₹7,65,000/month (₹91,80,000/year) in halting claims and expired e-Way Bill penalties.
• Deterministic Control-Gate Intervention & Verified Outcome: Linking ANPR gate-in timestamps and ULIP FASTag ETA feeds to deterministic YMS bay locks and automated e-Way Bill expiry alerts recovers ₹7,15,000/month (₹85,80,000/year).
• Statutory & Protocol Audit Trail: End-to-end compliance with CGST Rule 138(10) (NIC e-Way Bill validity window—200 km per day for normal cargo; mandatory extension within 8 hours before/after expiry if yard congestion delays unloading across midnight), Motor Vehicles Act driving-hour norms, and Indian Factories Act / BOCW dock safety interlocks., binding ImmutableScanEvent / DeviceTelemetryPacket (IN: FASTag + ANPR Timestamp) to ThreeWaySettlementMatch & VarianceHoldQueue (IN: Feeds Halting Bill Gate).

---

Statutory Audit-Trail Persistence Across US and Indian Regimes

An integration architecture for AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks is incomplete if its message logs cannot withstand a federal regulatory inspection or statutory tax audit several years after transaction execution:

• US Audit-Trail Persistence (Joliet (IL), Haslet (TX) & Inland Empire (CA) High-Velocity Yard & Cross-Dock Hubs): To satisfy FMCSA 49 CFR § 395.3 (driver Hours of Service 14-hour on-duty window and coercion prohibition under 49 CFR § 390.6), OSHA 29 CFR 1910.178(k) & (m) (powered industrial truck wheel chocks and dock-lock vehicle restraints before forklift entry), and standard MTSA work-in detention clauses., the integration broker must archive immutable, WORM-compliant (Write-Once-Read-Many) copies of every ImmutableScanEvent / DeviceTelemetryPacket, CompliancePayloadRecord (ASC X12 / GSTN-ULIP) (US: Scores Yard Shunts / US: TempZone + OSHA Lock), and ThreeWaySettlementMatch & VarianceHoldQueue settlement record, indexed by load/order ID, lot/LPN, and cryptographic SHA-256 payload digest.
• India Audit-Trail Persistence (Bhiwandi, Pataudi (NCR) & Sriperumbudur Mega Logistics Parks): To satisfy CGST Rule 138(10) (NIC e-Way Bill validity window—200 km per day for normal cargo; mandatory extension within 8 hours before/after expiry if yard congestion delays unloading across midnight), Motor Vehicles Act driving-hour norms, and Indian Factories Act / BOCW dock safety interlocks., the system must retain complete JSON/XML request-and-response envelopes for IN: Checks E-Way Expiry, IN: Bay Height + MHE Crew, and IN: Feeds Halting Bill Gate across the statutory 8-year GST/Customs retention window, preserving the exact linkage between physical gate/dock scans and financial tax notes.

---

Cutover Verification Protocol and Related Integration Blueprints

Before certifying AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks (L0254) for production operation across Joliet (IL), Haslet (TX) & Inland Empire (CA) High-Velocity Yard & Cross-Dock Hubs and Bhiwandi, Pataudi (NCR) & Sriperumbudur Mega Logistics Parks, engineering, operations, and finance leaders should verify the following six control invariants:

1. Edge Capture Integrity: Confirm that Gate ANPR/OCR cameras, RFID tractor/trailer tags, dock-door vehicle restraint interlocks (Rite-Hite/Dok-Lok), MHE forklift terminals, and real-time ELD/GPS ETA feeds writes immutable events to ImmutableScanEvent / DeviceTelemetryPacket and that ARRIVAL CLASSIFIER blocks any transaction violating |t_in - t_appt| <= 15m? or Stamps ON_TIME vs WORK_IN.
2. Pre-Release Statutory Gate: Verify that BOUNDED PLANNER validates US: Scores Yard Shunts (under FMCSA 49 CFR § 395.3 (driver Hours of Service 14-hour on-duty window and coercion prohibition under 49 CFR § 390.6)) and IN: Checks E-Way Expiry (under CGST Rule 138(10) (NIC e-Way Bill validity window—200 km per day for normal cargo; mandatory extension within 8 hours before/after expiry if yard congestion delays unloading across midnight)) with Proposes Work-In Window and Cannot Unlock Dock Restraint enforced prior to physical dispatch or wave release.
3. Mathematical Tolerance Engine: Validate that all three equations of Equipment-Compatible Dock-Door Assignment & Fault-Stamped Detention Clock Reset (*Hard Dock-Door Physical Compatibility & Labor Constraint*, *Detention Free-Time Clock Reset Under Late Carrier Arrival*, *Drop-and-Hook Yard Jockey Shunt Optimization*) execute deterministically inside DeterministicStateLock / ControlGateLedger and CompliancePayloadRecord (ASC X12 / GSTN-ULIP).
4. Automated Variance Split: Ensure YMS INTERLOCK evaluates Protects Outbound Cutoffs and Verifies Crew Capacity in real time, isolating disputed lines without stalling undisputed settlement flows.
5. Read-Only AI Segregation: Audit RBAC permissions for DWELL CLOCK LOCK to verify that Logs Exact Unload Window operates strictly under Forfeits Late Carrier Claim with zero direct write access to ThreeWaySettlementMatch & VarianceHoldQueue.
6. Three-Way Sub-Ledger Close: Confirm that ThreeWaySettlementMatch & VarianceHoldQueue enforces ZERO FALSE DETENTION (100% Timestamp Backed; Immutable Yard Ledger) with complete US ($) and India (₹) audit-trail persistence.

Related Logistics & Supply Chain Control Playbooks

Explore the broader Logistics & Supply Chain Control Library or review the companion playbooks in this cluster:

• AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — Architecture, System-of-Record Locks, and Worked USD/INR Example (L0252) — Complementary MOFU guide covering *ai yard gate appointment triage architecture* under Agentic AI vs. Deterministic WMS/TMS Control Gates.
• AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — Software Evaluation Matrix, Audit Trail Rules, and Pilot Checklist (L0253) — Complementary BOFU guide covering *ai yard gate appointment triage evaluation guide* under Agentic AI vs. Deterministic WMS/TMS Control Gates.
• AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — 3PL & Enterprise Implementation Playbook with SLA Tolerance Math (L0255) — Complementary BOFU guide covering *ai yard gate appointment triage implementation* under Agentic AI vs. Deterministic WMS/TMS Control Gates.
• AI Yard Gate Appointment Rescheduling: Managing Late Carrier Arrivals Within Dock Door Locks — Cost-Leakage Prevention, Variance Reconciliation, and CFO Sign-Off (L0256) — Complementary MOFU guide covering *ai yard gate appointment triage cost reconciliation* under Agentic AI vs. Deterministic WMS/TMS Control Gates.