Strategic Decision Logic (The "Operator's Brain")

0. Objective

To codify the non-deterministic preferences, heuristic rules, and strategic patterns used by the CEO to maintain MDL's competitive advantage in high-tech broadcast logistics.


1. Logistics Selection Heuristics (Which Carrier?)

Automation follows these logic gates for carrier selection:

IF (Shipment == "Blind") {
    DEFAULT = "TotalShip (NoviShip API)";
    REASON = "Requires scan-swap-ship at Kirkland/Omemee hub.";
} ELSE IF (Destination == "Quebec") {
    PREFERRED = "UPS Worldwide Saver";
    REASON = "Brokerage is often inclusive; specialized Haivision routing.";
} ELSE IF (Destination == "USA" AND Item_Value > $5000) {
    PREFERRED = "FedEx International Priority";
    REASON = "Superior high-value tracking and customs clearance fidelity.";
} ELSE {
    DEFAULT = "UPS Worldwide Expedited";
}

2. Customer Relationship & Financial Heuristics

2.1 The "Net 30" Hard-Line

2.2 The "HST/GST" Gap


3. AI Trust & Orchestration Levels

How much "Attention" does the operator need to pay?

Process Trust Level Validation Rule
Email Triage 95% Check backbone WORK_ITEMS daily for any 'unassigned'.
Quote Extraction 80% MANDATORY: Human must verify the "Vendor Selection" and "Margin %" before sending.
Bill Ingestion 98% Only check bills where Total Variance > $0.05.
Lead Enrichment 70% High hallucination risk. Verify phone numbers before calling.

4. Vendor Negotiation Patterns


5. Dispute Logic (Government Agency Fees)

MDL generates a "Hard Dispute" whenever a carrier charges a Disbursement Fee on an RPP-bonded shipment.


6. Strategic Growth Priorities (Roadmap Intelligence)

If you have surplus dev time, prioritize in this order: 1. Direct API Integration for COM-TECH (currently manual). 2. Visual Dashboarding for Landed Cost Variances (Backbone -> Evidence.dev). 3. Autonomous CRM Sync: Linking Outlook threads to HubSpot deals automatically.


7. Versioning & Evolution

This logic is updated whenever a "Session Summary" identifies a recurring human correction. Each version number (vX.X) corresponds to a major alignment in the Automation Backbone logic.