@wonsukchoi/crondex 0.22.0 → 0.23.0

package/jobs/insurance/quote-to-bind-conversion-tracker.yaml

@@ -0,0 +1,41 @@
+id: quote-to-bind-conversion-tracker
+version: 1
+name: Quote-to-Bind Conversion Rate Tracker
+description: >
+  Calculates the quote-to-bind conversion rate over the trailing period
+  and flags it when it drops below target, so sales/underwriting leaders
+  catch a pricing or process problem while it's still small. Use this if
+  a falling close rate has ever gone unnoticed for a full quarter because
+  nobody was watching quotes lost, only policies written.
+category: insurance
+tags: [insurance, sales, quoting, conversion, underwriting]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{target_conversion_pct}}" '
+    NR==1 {next}
+    {
+      quotes++;
+      if ($2 == "bound") bound++;
+    }
+    END {
+      pct = (quotes > 0) ? (bound / quotes) * 100 : 0;
+      printf "CONVERSION RATE: %.1f%% (%d of %d quotes bound) — target %d%%\n", pct, bound, quotes, target;
+      if (pct < target) {
+        printf "BELOW TARGET: conversion rate is under the %d%% target\n", target;
+      }
+    }
+  ' "{{quotes_csv_path}}"
+variables:
+  quotes_csv_path:
+    default: "./quotes-weekly.csv"
+    description: "Path to a CSV with columns: quote_id,status (bound/lost/pending) for the trailing reporting period."
+  target_conversion_pct:
+    default: 25
+    description: Target minimum quote-to-bind conversion rate percentage before this is flagged as below target.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Sales-funnel metric for new business production, distinct from
+  underwriting-queue-sla-monitor, which measures decision speed rather
+  than the rate at which quotes actually convert to bound policies.

package/jobs/insurance/reinsurance-treaty-renewal-tracker.yaml

@@ -0,0 +1,38 @@
+id: reinsurance-treaty-renewal-tracker
+version: 1
+name: Reinsurance Treaty Renewal Tracker
+description: >
+  Warns before a reinsurance treaty's renewal or non-renewal notice date
+  so terms can be renegotiated or the market re-shopped in time. Use this
+  if a treaty has ever auto-renewed on unfavorable terms because the
+  notice window quietly passed.
+category: insurance
+tags: [insurance, reinsurance, treaty, renewal]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline notice_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (notice_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "NOTICE DEADLINE APPROACHING: %s (%s) — non-renewal notice due %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{treaties_csv_path}}"
+variables:
+  treaties_csv_path:
+    default: "./reinsurance-treaties.csv"
+    description: "Path to a CSV with columns: treaty_name,reinsurer,non_renewal_notice_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 60
+    description: How many days before the non-renewal notice deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks the reinsurer-facing treaty notice deadline, not a primary
+  policy renewal — distinct in scope from policy-renewal-reminder, which
+  tracks retail/commercial policies sold to policyholders.

package/jobs/insurance/siu-fraud-referral-tracker.yaml

@@ -0,0 +1,36 @@
+id: siu-fraud-referral-tracker
+version: 1
+name: SIU Fraud Referral Tracker
+description: >
+  Checks claims referred to the Special Investigations Unit for suspected
+  fraud and flags any referral that hasn't been triaged or closed within
+  the target window. Use this if a fraud-flagged claim has ever sat in an
+  SIU queue for months with no documented outcome.
+category: insurance
+tags: [insurance, siu, fraud, claims, compliance]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the SIU referral log: {{siu_referrals_summary}}.
+  1. List each open referral: claim number, referral date, referral
+     reason, and current SIU status.
+  2. Flag any referral open longer than {{triage_sla_days}} days without
+     a documented triage decision (accept for investigation, decline,
+     refer to law enforcement, or close as unsubstantiated).
+  3. For referrals nearing a statutory reporting deadline, note that
+     explicitly so it doesn't get missed.
+  4. Do not draw conclusions about guilt — flag for human SIU review only.
+variables:
+  siu_referrals_summary:
+    default: "paste or summarize the current SIU referral log here"
+    description: Summary or export of claims currently referred to the Special Investigations Unit.
+  triage_sla_days:
+    default: 15
+    description: Days a referral can sit without a documented triage decision before it's flagged.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Fraud-investigation triage tracking, distinct from
+  claims-aging-backlog-tracker which tracks ordinary claim age rather
+  than SIU investigation status. Sensitive — restrict access to the SIU
+  team and legal/compliance.

package/jobs/insurance/subrogation-recovery-tracker.yaml

@@ -0,0 +1,41 @@
+id: subrogation-recovery-tracker
+version: 1
+name: Subrogation Recovery Tracker
+description: >
+  Checks open subrogation files against at-fault third parties and flags
+  ones with no recovery activity in a while, so pursuit doesn't quietly
+  stall until the statute of limitations closes the door. Use this if a
+  recoverable claim has ever gone unpursued long enough to lose the
+  chance at reimbursement entirely.
+category: insurance
+tags: [insurance, subrogation, recovery, claims]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the open subrogation file list: {{subrogation_files_summary}}.
+  1. List each open file: claim number, at-fault party, recovery amount
+     sought, and date of last recovery activity.
+  2. Flag any file with no activity in more than {{stale_after_days}}
+     days as needing follow-up (demand letter, arbitration filing, or
+     status call to the at-fault carrier).
+  3. Separately flag any file approaching its statute-of-limitations
+     deadline within {{sol_warn_days}} days as urgent.
+  4. Draft a short follow-up note for each stale file, referencing the
+     claim number and recovery amount.
+variables:
+  subrogation_files_summary:
+    default: "paste or summarize the current open subrogation file list here"
+    description: Summary or export of open subrogation recovery files.
+  stale_after_days:
+    default: 21
+    description: Days without recovery activity before a file is flagged as stale.
+  sol_warn_days:
+    default: 45
+    description: Days before a statute-of-limitations deadline to flag a file as urgent.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Tracks pursuing reimbursement from an at-fault third party after a
+  claim is paid — a different direction and timeline from
+  claim-status-check, which tracks the insurer's own claim to the
+  policyholder before payment.

package/jobs/insurance/underwriting-queue-sla-monitor.yaml

@@ -0,0 +1,45 @@
+id: underwriting-queue-sla-monitor
+version: 1
+name: Underwriting Queue SLA Monitor
+description: >
+  Checks pending underwriting submissions against the target
+  turnaround-time SLA and flags any that are approaching or past it. Use
+  this if a broker submission has ever sat in an underwriter's queue for
+  weeks with no decision because nobody was watching the clock.
+category: insurance
+tags: [insurance, underwriting, sla, queue]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v sla="{{sla_days}}" -v warn="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline submitted_epoch; close(cmd);
+      age_days = (today - submitted_epoch) / 86400;
+      remaining = sla - age_days;
+      if (remaining <= 0) {
+        printf "SLA BREACHED: %s (%s) submitted %s — %d days in queue, SLA is %d\n", $1, $3, $2, age_days, sla;
+      } else if (remaining <= warn) {
+        printf "SLA AT RISK: %s (%s) submitted %s — %d days remaining\n", $1, $3, $2, remaining;
+      }
+    }
+  ' "{{submissions_csv_path}}"
+variables:
+  submissions_csv_path:
+    default: "./underwriting-submissions.csv"
+    description: "Path to a CSV with columns: submission_id,submitted_date (YYYY-MM-DD),underwriter,decision_date (blank if undecided)."
+  sla_days:
+    default: 10
+    description: Target number of business days to reach a decision from submission.
+  warn_days_before:
+    default: 2
+    description: Days before the SLA deadline to start flagging a submission as at-risk.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks new-business/renewal underwriting decision turnaround, distinct
+  from endorsement-request-followup-check which tracks mid-term policy
+  change requests after a policy is already bound.

package/jobs/logistics/3pl-performance-scorecard.yaml

@@ -0,0 +1,45 @@
+id: 3pl-performance-scorecard
+version: 1
+name: 3PL Performance Scorecard
+description: >
+  Reviews a third-party logistics provider's recent performance across
+  on-time delivery, damage rate, and cost against your service agreement
+  targets. Use this if a 3PL relationship has ever drifted from "great at
+  onboarding" to "quietly underperforming" without a regular scorecard
+  catching it.
+category: logistics
+tags: [logistics, 3pl, performance, scorecard]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Pull the last {{period_days}} days of performance data for 3PL
+  provider {{provider_name}} from {{data_source_hint}}.
+  1. Summarize on-time delivery rate, damage/loss rate, and average
+     cost per shipment.
+  2. Compare each metric against the service agreement targets:
+     OTD >= {{otd_target_pct}}%, damage rate <= {{damage_target_pct}}%.
+  3. Flag any metric missing target, note the trend versus the prior
+     period if available, and suggest whether it warrants a QBR
+     conversation or is within normal variance.
+variables:
+  provider_name:
+    default: "your-3pl-provider"
+    description: Name of the 3PL provider being scored.
+  data_source_hint:
+    default: "your TMS or the 3PL's reporting portal"
+    description: Where shipment-level performance data for this 3PL can be pulled.
+  period_days:
+    default: 30
+    description: Lookback window for the scorecard period.
+  otd_target_pct:
+    default: 95
+    description: Contracted on-time delivery target.
+  damage_target_pct:
+    default: 1
+    description: Contracted maximum acceptable damage/loss rate.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Aggregate multi-metric scorecard for an outsourced logistics provider,
+  distinct from carrier-otd-performance-scorecard which tracks a single
+  metric (on-time delivery) per carrier from your own shipment CSV.

package/jobs/logistics/bol-freight-class-accuracy-audit.yaml

@@ -0,0 +1,33 @@
+id: bol-freight-class-accuracy-audit
+version: 1
+name: Bill of Lading Freight Class Accuracy Audit
+description: >
+  Reviews recent bills of lading for freight class or NMFC codes that
+  look mismatched against the described commodity, which is a common
+  cause of reclassification fees. Use this if a shipment has ever come
+  back with a surprise reclass charge because the BOL freight class
+  didn't match what was actually shipped.
+category: logistics
+tags: [logistics, freight, bol, compliance, billing]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the bills of lading listed in {{bol_source_hint}} for the last
+  {{lookback_days}} days.
+  1. For each BOL, compare the declared freight class/NMFC code against
+     the described commodity and dimensions/weight.
+  2. Flag any BOL where the class looks mismatched (e.g. density-based
+     class inconsistent with stated weight/cube, or a commodity code
+     that doesn't match the item description).
+  3. For each flagged BOL, note the likely correct class if determinable
+     and the estimated reclassification fee risk.
+variables:
+  bol_source_hint:
+    default: "your TMS or freight audit vendor's BOL archive"
+    description: Where recent bills of lading can be reviewed.
+  lookback_days:
+    default: 7
+    description: How many days of BOLs to review per run.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — freight classification judgment (NMFC density/commodity rules) isn't reliably scriptable from a CSV; this needs interpretation of the BOL description against the shipped item.

package/jobs/logistics/cargo-insurance-claim-status-check.yaml

@@ -0,0 +1,39 @@
+id: cargo-insurance-claim-status-check
+version: 1
+name: Cargo Insurance Claim Status Check
+description: >
+  Checks open cargo loss/damage insurance claims for ones that have gone
+  quiet and need a follow-up push. Use this if a damaged-freight claim
+  has ever sat untouched with the insurer for months because nobody was
+  tracking it against the filing deadline or a status update.
+category: logistics
+tags: [logistics, cargo, insurance, claims]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{claims_portal_hint}} for open cargo loss/damage claims.
+  1. List each open claim: claim number, shipment reference, date filed,
+     and current status.
+  2. Flag any claim with no status update in the last
+     {{stale_days}} days, or approaching a filing/documentation deadline
+     within {{deadline_warn_days}} days.
+  3. Suggest the follow-up action for each flagged claim (submit missing
+     documentation, request adjuster update, escalate).
+variables:
+  claims_portal_hint:
+    default: "your cargo insurer's claims portal or broker"
+    description: Where open cargo insurance claims and their status are tracked.
+  stale_days:
+    default: 14
+    description: Days without a status update before a claim is flagged as stale.
+  deadline_warn_days:
+    default: 5
+    description: Days before a claim deadline to start warning.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Scoped to freight loss/damage claims against a cargo policy, tracked
+  per shipment through the insurer/broker — distinct from a general
+  claim-status job in that it follows freight-specific deadlines (e.g.
+  concealed damage notice windows) rather than a generic policyholder
+  claim.

package/jobs/logistics/carrier-load-tender-acceptance-check.yaml

@@ -0,0 +1,34 @@
+id: carrier-load-tender-acceptance-check
+version: 1
+name: Carrier Load Tender Acceptance Check
+description: >
+  Checks recently tendered loads for carriers that haven't accepted or
+  rejected within the expected window. Use this if a tendered load has
+  ever sat unconfirmed until the ship date was already at risk.
+category: logistics
+tags: [logistics, carrier, tender, booking]
+schedule: "0 */3 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{tms_or_broker_portal}} for load tenders sent to carriers in the
+  last {{lookback_hours}} hours.
+  1. List each tendered load: load/reference number, carrier, and time
+     since tendered.
+  2. Flag any load still showing "pending" or unacknowledged past
+     {{escalate_after_hours}} hours.
+  3. For flagged loads, suggest the next action — re-tender to a backup
+     carrier, call the carrier directly, or escalate to the broker —
+     based on how close the ship date is.
+variables:
+  tms_or_broker_portal:
+    default: "your TMS load board or broker portal"
+    description: Where tendered loads and their acceptance status are visible.
+  lookback_hours:
+    default: 48
+    description: How far back to check for tendered loads.
+  escalate_after_hours:
+    default: 6
+    description: Hours a tender can sit unacknowledged before it's flagged as at risk.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — tender status and acceptance workflows vary by TMS and broker platform, and re-tender decisions need judgment about ship-date risk.

package/jobs/logistics/carrier-otd-performance-scorecard.yaml

@@ -0,0 +1,41 @@
+id: carrier-otd-performance-scorecard
+version: 1
+name: Carrier On-Time Delivery Performance Scorecard
+description: >
+  Tracks each carrier's on-time delivery rate over recent shipments and
+  flags any carrier that's dropped below your target. Use this if a
+  carrier's reliability has ever quietly slipped for months before a
+  customer complaint made it obvious.
+category: logistics
+tags: [logistics, carrier, otd, performance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{otd_target_pct}}" '
+    NR==1 {next}
+    {
+      total[$1]++;
+      if ($2 == "on-time") ontime[$1]++;
+    }
+    END {
+      for (c in total) {
+        pct = (ontime[c] / total[c]) * 100;
+        if (pct < target) {
+          printf "BELOW TARGET: %s — %.1f%% on-time (%d of %d shipments), target %d%%\n", c, pct, ontime[c], total[c], target;
+        }
+      }
+    }
+  ' "{{shipments_csv_path}}"
+variables:
+  shipments_csv_path:
+    default: "./carrier-shipments.csv"
+    description: "Path to a CSV with columns: carrier_name,status (on-time or late) — one row per recent outbound shipment."
+  otd_target_pct:
+    default: 90
+    description: Minimum acceptable on-time delivery percentage per carrier.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks outbound carrier delivery performance to customers, not inbound
+  supplier delivery of materials — pair with your TMS or carrier
+  scorecard export to keep the CSV current.

package/jobs/logistics/carrier-rate-contract-renewal-check.yaml

@@ -0,0 +1,35 @@
+id: carrier-rate-contract-renewal-check
+version: 1
+name: Carrier Rate Contract Renewal Check
+description: >
+  Checks tracked carrier rate agreements against their expiry date and
+  warns before they lapse. Use this if a freight contract has ever
+  quietly expired and shipments kept moving on it anyway, until a rate
+  dispute surfaced with no valid agreement backing it.
+category: logistics
+tags: [logistics, carrier, contract, renewal]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline expiry_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (expiry_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "RENEWAL DUE: carrier agreement %s — expires %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{carrier_contracts_csv_path}}"
+variables:
+  carrier_contracts_csv_path:
+    default: "./carrier-rate-contracts.csv"
+    description: "Path to a CSV with columns: carrier_name,contract_expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 45
+    description: How many days before contract expiry to start warning, to leave time for renewal negotiation.
+compatible_agents: [generic, claude, codex]
+notes: Assumes carrier rate agreements and their term dates are exported or manually tracked from procurement/legal — this is the renewal-deadline backstop, not a contract management system.

package/jobs/logistics/cross-dock-dwell-time-watch.yaml

@@ -0,0 +1,43 @@
+id: cross-dock-dwell-time-watch
+version: 1
+name: Cross-Dock Dwell Time Watch
+description: >
+  Checks freight moving through a cross-dock facility against a target
+  dwell time and flags anything sitting too long between inbound and
+  outbound legs. Use this if freight has ever quietly stalled at a
+  cross-dock for days, turning a same-day transfer into a missed
+  delivery window.
+category: logistics
+tags: [logistics, cross-dock, dwell-time, freight]
+schedule: "0 */2 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v threshold="{{max_dwell_hours}}" '
+    NR==1 {next}
+    {
+      shipment=$1; arrived=$2; status=$3;
+      if (status != "departed") {
+        cmd = "date -d \"" arrived "\" +%s 2>/dev/null || date -j -f %Y-%m-%dT%H:%M:%S \"" arrived "\" +%s 2>/dev/null";
+        cmd | getline arrived_epoch; close(cmd);
+        "date +%s" | getline now_epoch; close("date +%s");
+        dwell_hours = (now_epoch - arrived_epoch) / 3600;
+        if (dwell_hours >= threshold) {
+          printf "DWELL EXCEEDED: shipment %s has been on the dock %.1fh (arrived %s), threshold %dh\n", shipment, dwell_hours, arrived, threshold;
+        }
+      }
+    }
+  ' "{{crossdock_status_csv}}"
+variables:
+  crossdock_status_csv:
+    default: "./crossdock-shipment-status.csv"
+    description: "Path to a CSV with columns: shipment_id,arrived_at (ISO timestamp),status (e.g. staged, departed) — export from your dock/yard management system."
+  max_dwell_hours:
+    default: 12
+    description: Hours a shipment can sit at the cross-dock before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks freight-in-transit dwell between inbound and outbound legs at a
+  cross-dock, distinct from warehousing's dock-schedule-conflict-check
+  (which checks appointment scheduling conflicts, not how long freight
+  actually sits once it's on the dock).

package/jobs/logistics/freight-invoice-rate-audit.yaml

@@ -0,0 +1,38 @@
+id: freight-invoice-rate-audit
+version: 1
+name: Freight Invoice Rate Audit
+description: >
+  Compares billed freight invoice amounts against the contracted rate for
+  each shipment and flags overcharges. Use this if a carrier has ever
+  quietly billed above the agreed rate and it only got caught months
+  later during an annual freight spend review.
+category: logistics
+tags: [logistics, freight, invoice, audit, billing]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v tolerance="{{overcharge_tolerance_pct}}" '
+    NR==1 {next}
+    {
+      invoice_id=$1; contracted=$2; billed=$3;
+      if (contracted <= 0) next;
+      pct_over = ((billed - contracted) / contracted) * 100;
+      if (pct_over > tolerance) {
+        printf "OVERCHARGE: invoice %s — billed $%.2f vs contracted $%.2f (%.1f%% over, tolerance %d%%)\n", invoice_id, billed, contracted, pct_over, tolerance;
+      }
+    }
+  ' "{{invoices_csv_path}}"
+variables:
+  invoices_csv_path:
+    default: "./freight-invoices.csv"
+    description: "Path to a CSV with columns: invoice_id,contracted_rate,billed_amount — export from your freight audit/AP system."
+  overcharge_tolerance_pct:
+    default: 3
+    description: Percent above the contracted rate allowed before flagging as an overcharge worth disputing.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Checks billing accuracy against the contracted rate, not market rate
+  movement — pair with freight-rate-spike-watch if you also want to
+  track whether the contracted rate itself is falling behind the
+  market.

package/jobs/logistics/fuel-surcharge-rate-monitor.yaml

@@ -0,0 +1,40 @@
+id: fuel-surcharge-rate-monitor
+version: 1
+name: Fuel Surcharge Rate Monitor
+description: >
+  Checks the current published fuel surcharge index against your
+  baseline and flags a jump. Use this if a carrier's fuel surcharge has
+  ever crept up for weeks before it showed up as a bigger-than-expected
+  line item on the freight invoice.
+category: logistics
+tags: [logistics, freight, fuel-surcharge, rates]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  surcharge_pct=$(curl -s -H "Authorization: Bearer {{fuel_index_api_token}}" "{{fuel_index_api_url}}" | grep -o '"surcharge_pct":[0-9.]*' | head -n1 | cut -d':' -f2);
+  if [ -z "$surcharge_pct" ]; then echo "ERROR: could not fetch fuel surcharge data from {{fuel_index_api_url}}"; exit 1; fi;
+  if awk "BEGIN{exit !($surcharge_pct - {{baseline_surcharge_pct}} >= {{jump_threshold_pct}})}"; then
+    echo "WARNING: fuel surcharge is ${surcharge_pct}% (baseline {{baseline_surcharge_pct}}%, jumped >= {{jump_threshold_pct}}pt)";
+    exit 1;
+  else echo "OK: fuel surcharge is ${surcharge_pct}%, within tolerance of baseline {{baseline_surcharge_pct}}%"; fi
+variables:
+  fuel_index_api_url:
+    default: "https://api.example-carrier.com/fuel-surcharge/current"
+    description: Carrier or DOE fuel surcharge index API endpoint returning surcharge_pct.
+  fuel_index_api_token:
+    default: "your-api-token"
+    description: Bearer token for the fuel surcharge index API, if required.
+  baseline_surcharge_pct:
+    default: 25
+    description: Baseline fuel surcharge percentage to compare against.
+  jump_threshold_pct:
+    default: 5
+    description: Percentage-point jump above baseline that counts as worth flagging.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Generic REST pattern — point fuel_index_api_url at your carrier's
+  published surcharge schedule or the DOE/EIA weekly diesel price feed
+  used to derive it; adjust field names to match its response shape.
+  Distinct from freight-rate-spike-watch, which tracks the all-in
+  quoted lane rate rather than the fuel surcharge component alone.

package/jobs/logistics/international-shipment-documentation-check.yaml

@@ -0,0 +1,36 @@
+id: international-shipment-documentation-check
+version: 1
+name: International Shipment Documentation Completeness Check
+description: >
+  Checks upcoming international shipments for missing export/import
+  paperwork before they're due to ship. Use this if a shipment has ever
+  reached the port only to get held up because the commercial invoice or
+  certificate of origin was never finalized.
+category: logistics
+tags: [logistics, international, documentation, export, compliance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{shipment_system_hint}} for international shipments scheduled
+  to depart within the next {{lookahead_days}} days.
+  1. For each shipment, verify the required document set is present:
+     commercial invoice, packing list, certificate of origin, and any
+     destination-specific requirements (e.g. import license, phytosanitary
+     certificate) for {{destination_hint}}.
+  2. Flag any shipment missing one or more required documents.
+  3. For each flagged shipment, note which document is missing and who
+     typically owns producing it (shipper, freight forwarder, customs
+     broker).
+variables:
+  shipment_system_hint:
+    default: "your TMS or export documentation system"
+    description: Where upcoming international shipments and their document status are tracked.
+  lookahead_days:
+    default: 5
+    description: How many days ahead to check for shipments needing documentation.
+  destination_hint:
+    default: "your typical export destination(s)"
+    description: Destination country/countries, since required documents vary by destination.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — required document sets vary by destination country and commodity, and need judgment about which regulatory requirements apply.

package/jobs/logistics/linehaul-transit-time-variance-check.yaml

@@ -0,0 +1,43 @@
+id: linehaul-transit-time-variance-check
+version: 1
+name: Linehaul Transit Time Variance Check
+description: >
+  Compares actual transit times against the scheduled transit time per
+  lane and flags lanes running consistently slow. Use this if a lane's
+  transit times have ever crept up gradually until service levels
+  quietly missed the mark for a whole quarter.
+category: logistics
+tags: [logistics, transit, lanes, performance]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v tolerance="{{variance_hours_threshold}}" '
+    NR==1 {next}
+    {
+      lane=$1; scheduled=$2; actual=$3;
+      variance = actual - scheduled;
+      sum[lane] += variance; count[lane]++;
+    }
+    END {
+      for (l in sum) {
+        avg = sum[l] / count[l];
+        if (avg >= tolerance) {
+          printf "SLOW LANE: %s — averaging %.1fh over scheduled transit time across %d shipments\n", l, avg, count[l];
+        }
+      }
+    }
+  ' "{{transit_times_csv_path}}"
+variables:
+  transit_times_csv_path:
+    default: "./lane-transit-times.csv"
+    description: "Path to a CSV with columns: lane,scheduled_transit_hours,actual_transit_hours — one row per completed shipment."
+  variance_hours_threshold:
+    default: 6
+    description: Average hours over scheduled transit time before a lane is flagged as consistently slow.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Aggregates variance across a lane's shipment history, unlike
+  shipment-delay-watch which checks a single shipment's live tracking
+  status — this catches gradual lane-level drift a one-off delay check
+  won't.