@wonsukchoi/crondex 0.21.0 → 0.23.0

package/jobs/legal/conflict-of-interest-check-tracker.yaml

@@ -0,0 +1,38 @@
+id: conflict-of-interest-check-tracker
+version: 1
+name: Conflict-of-Interest Check Tracker
+description: >
+  Checks new matters or clients waiting on a conflict-of-interest clearance
+  and flags any that have sat unresolved past a set number of days. Use
+  this if a new engagement has ever started before the conflicts check
+  actually cleared, because the request got sent and then forgotten.
+category: legal
+tags: [legal, conflicts-check, intake, compliance]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{overdue_days}}" '
+    NR==1 {next}
+    $4 == "pending" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline requested_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      pending_days = (now_epoch - requested_epoch) / 86400;
+      if (pending_days >= days) {
+        printf "CONFLICTS CHECK PENDING: %s (matter: %s) — requested %s (%d days ago)\n", $1, $2, $3, pending_days;
+      }
+    }
+  ' "{{conflicts_csv_path}}"
+variables:
+  conflicts_csv_path:
+    default: "./conflict-checks.csv"
+    description: "Path to a CSV with columns: client_or_matter_name,proposed_matter,check_requested_date (YYYY-MM-DD),status (pending/cleared/conflict-identified)."
+  overdue_days:
+    default: 2
+    description: Days a conflicts check can remain pending before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: >
+  This tracks whether a conflicts check was run and resolved before
+  engagement start — it does not run the conflicts search itself, which
+  depends on your practice management/conflicts database.

package/jobs/legal/corporate-minute-book-completeness-check.yaml

@@ -0,0 +1,31 @@
+id: corporate-minute-book-completeness-check
+version: 1
+name: Corporate Minute Book Completeness Check
+description: >
+  Checks the corporate minute book against the list of resolutions and
+  actions that should be documented for the year and flags anything
+  missing. Use this if a board resolution or annual consent has ever been
+  discussed and acted on but never actually got written up and filed in
+  the minute book, which surfaces at the worst time — due diligence for
+  a financing or sale.
+category: legal
+tags: [legal, corporate-governance, board-resolutions, minute-book]
+schedule: "0 9 1 1,4,7,10 *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    $4 == "no" {
+      printf "MISSING FROM MINUTE BOOK: %s — %s (required by %s, not yet filed)\n", $1, $2, $3;
+    }
+  ' "{{minute_book_checklist_csv_path}}"
+variables:
+  minute_book_checklist_csv_path:
+    default: "./minute-book-checklist.csv"
+    description: "Path to a CSV with columns: item_id,description (e.g. 'annual board consent', 'officer appointment resolution'),required_by_date (YYYY-MM-DD or a plain label like 'Q2'),filed (yes/no)."
+compatible_agents: [generic, claude, codex]
+notes: >
+  Assumes someone maintains the checklist whenever a resolution, consent,
+  or corporate action is decided — this only checks whether the paper
+  trail is complete, it doesn't draft the resolutions themselves.

package/jobs/legal/data-privacy-request-deadline-tracker.yaml

@@ -0,0 +1,61 @@
+id: data-privacy-request-deadline-tracker
+version: 1
+name: Data Privacy Request (GDPR/CCPA) Deadline Tracker
+description: >
+  Flags open data subject access/deletion requests approaching their
+  statutory response deadline and drafts a status summary for whoever
+  owns the response. Use this if a GDPR or CCPA-style privacy request has
+  ever come uncomfortably close to its response window because tracking
+  it lived in someone's inbox instead of a real deadline list.
+category: legal
+tags: [legal, data-privacy, gdpr, ccpa, deadline]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: hybrid
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $5 == "open" {
+      cmd = "date -d \"" $4 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $4 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "PRIVACY REQUEST DUE: %s — %s request, due %s (%d days)\n", $1, $2, $4, diff_days;
+      }
+    }
+  ' "{{privacy_requests_csv_path}}"
+prompt: |
+  Here is the raw list of open data privacy requests approaching their
+  deadline (from the shell check): {{command_output}}. For each one:
+  1. Note the request type ({{request_types_hint}}) and which regulation's
+     clock applies (e.g. GDPR's ~30-day window, CCPA's 45-day window).
+  2. Flag anything with fewer than {{urgent_within_days}} days left as
+     urgent and needing an owner today.
+  3. Draft a short status update summarizing what's open, what's urgent,
+     and who should act next, suitable for pasting into a privacy/legal
+     ops channel.
+variables:
+  privacy_requests_csv_path:
+    default: "./data-privacy-requests.csv"
+    description: "Path to a CSV with columns: request_id,request_type (access/deletion/correction/opt-out),regulation (gdpr/ccpa/other),response_due_date (YYYY-MM-DD),status (open/closed)."
+  warn_days_before:
+    default: 7
+    description: Days before the statutory response deadline to start flagging.
+  urgent_within_days:
+    default: 2
+    description: Days left at which an open request becomes urgent in the drafted summary.
+  request_types_hint:
+    default: "access, deletion, correction, or opt-out of sale"
+    description: Short reminder of the request categories your intake form uses.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+script_note: >
+  The shell command gives a zero-token list of requests inside the warning
+  window from date math alone; the prompt adds regulation-specific
+  framing and a drafted, prioritized summary a non-lawyer can act on
+  without re-reading each row.
+notes: >
+  Actual statutory deadlines, extensions, and exceptions vary by
+  regulation and request type — confirm with privacy counsel. This is a
+  tracking and drafting aid, not a substitute for legal review of any
+  individual request.

package/jobs/legal/entity-authority-document-expiry-check.yaml

@@ -0,0 +1,37 @@
+id: entity-authority-document-expiry-check
+version: 1
+name: Entity Authority Document Expiry Check
+description: >
+  Warns before a power of attorney, corporate signing-authority
+  certificate, or other entity-authority document reaches its expiration
+  date. Use this if a bank, counterparty, or government office has ever
+  rejected a signature because the power of attorney or authority
+  certificate backing it had quietly expired.
+category: legal
+tags: [legal, power-of-attorney, corporate-authority, compliance]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: \"" $1 "\" (" $2 ") expires in " days_left " days (" $3 ")";
+    }
+  ' {{authority_docs_csv}}
+variables:
+  authority_docs_csv:
+    default: "entity-authority-documents.csv"
+    description: "CSV with header row, columns: document_name,document_type (e.g. power-of-attorney, signing-authority-certificate),expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 45
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Distinct from `business-license-renewal-check` (operating licenses/permits)
+  — this tracks documents that grant someone authority to act or sign on
+  the entity's behalf. Update the CSV whenever an authority document is
+  issued, renewed, or revoked.

package/jobs/legal/legal-document-retention-purge-review.yaml

@@ -0,0 +1,39 @@
+id: legal-document-retention-purge-review
+version: 1
+name: Legal Document Retention Purge Review
+description: >
+  Checks contracts and legal documents against their retention schedule
+  and flags anything past its retention period as eligible for archival
+  or destruction review. Use this if signed contracts and legal files
+  have ever piled up indefinitely because nobody was checking them
+  against how long the business's own retention policy actually requires
+  keeping them.
+category: legal
+tags: [legal, records-retention, document-management, compliance]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    NR==1 {next}
+    $4 == "no" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline exp_epoch; close(cmd);
+      if (today >= exp_epoch) {
+        printf "RETENTION EXPIRED: %s (%s) — retention ended %s, check for holds before purging\n", $1, $2, $3;
+      }
+    }
+  ' "{{records_csv_path}}"
+variables:
+  records_csv_path:
+    default: "./legal-records-retention-schedule.csv"
+    description: "Path to a CSV with columns: document_id,document_type,retention_end_date (YYYY-MM-DD),reviewed (yes/no). One row per contract/legal document tracked under the retention policy."
+compatible_agents: [generic, claude, codex]
+notes: >
+  Business's own contract/legal-file retention schedule — distinct from
+  `public-records-retention-purge-check` in government (public-sector
+  records law) and from `litigation-hold-acknowledgment-tracker` in this
+  category. Always cross-check against any active litigation hold before
+  destroying anything this flags — a hold overrides the normal retention
+  schedule.

package/jobs/legal/litigation-hold-acknowledgment-tracker.yaml

@@ -0,0 +1,40 @@
+id: litigation-hold-acknowledgment-tracker
+version: 1
+name: Litigation Hold Acknowledgment Tracker
+description: >
+  Checks active litigation hold notices against the custodian list and
+  flags anyone who hasn't acknowledged receipt yet. Use this if a
+  litigation hold has ever gone out and nobody could later prove every
+  custodian actually got and confirmed it, which is exactly what gets
+  picked apart in a spoliation motion.
+category: legal
+tags: [legal, litigation, litigation-hold, ediscovery, compliance]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{escalate_after_days}}" '
+    NR==1 {next}
+    $5 == "active" && $4 == "" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline sent_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      pending_days = (now_epoch - sent_epoch) / 86400;
+      if (pending_days >= days) {
+        printf "NOT ACKNOWLEDGED: %s — hold \"%s\" sent %s (%d days ago)\n", $1, $2, $3, pending_days;
+      }
+    }
+  ' "{{holds_csv_path}}"
+variables:
+  holds_csv_path:
+    default: "./litigation-holds.csv"
+    description: "Path to a CSV with columns: custodian_name,matter_name,notice_sent_date (YYYY-MM-DD),acknowledged_date (blank if not yet acknowledged),hold_status (active/released)."
+  escalate_after_days:
+    default: 5
+    description: Days a sent hold notice can go unacknowledged before it's flagged for follow-up.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Assumes counsel maintains the CSV whenever a hold is issued, released, or
+  a custodian confirms receipt. Distinct from court-deadline-reminder
+  (filing/response deadlines within a matter) — this tracks preservation
+  obligations and custodian acknowledgment instead.

package/jobs/legal/non-compete-expiry-tracker.yaml

@@ -0,0 +1,37 @@
+id: non-compete-expiry-tracker
+version: 1
+name: Non-Compete / Non-Solicit Expiry Tracker
+description: >
+  Tracks the restricted-period end date of non-compete and non-solicit
+  agreements for departed employees and warns as each one is about to
+  expire. Use this if you've ever needed to know exactly when a former
+  employee's restrictive covenant runs out — before deciding whether to
+  act on a suspected violation, or before it's too late to.
+category: legal
+tags: [legal, non-compete, non-solicit, restrictive-covenants, employment]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: " $2 " covenant for " $1 " expires in " days_left " days (" $3 ")";
+    }
+  ' {{covenants_csv}}
+variables:
+  covenants_csv:
+    default: "non-compete-covenants.csv"
+    description: "CSV with header row, columns: former_employee_name,covenant_type (non-compete/non-solicit),restricted_period_end_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before the restricted period ends to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Enforceability of these covenants varies a lot by state/country and has
+  been narrowing in many jurisdictions — confirm with counsel before
+  relying on any covenant as still enforceable. Update the CSV whenever
+  an employee with a covenant departs.

package/jobs/legal/outside-counsel-invoice-budget-check.yaml

@@ -0,0 +1,37 @@
+id: outside-counsel-invoice-budget-check
+version: 1
+name: Outside Counsel Invoice Budget Check
+description: >
+  Compares outside counsel invoices billed to date against each matter's
+  approved budget and flags matters approaching or over budget. Use this
+  if a matter budget has ever been blown through silently because
+  invoices got approved one at a time without anyone tracking the
+  running total against the budget set at intake.
+category: legal
+tags: [legal, outside-counsel, billing, budget]
+schedule: "0 9 1,15 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v warn_pct="{{warn_at_percent}}" '
+    NR==1 {next}
+    {
+      budget = $3 + 0;
+      billed = $4 + 0;
+      if (budget > 0) {
+        pct = (billed / budget) * 100;
+        if (pct >= warn_pct) {
+          printf "BUDGET ALERT: %s (firm: %s) — billed $%.2f of $%.2f budget (%.0f%%)\n", $1, $2, billed, budget, pct;
+        }
+      }
+    }
+  ' "{{matter_budgets_csv_path}}"
+variables:
+  matter_budgets_csv_path:
+    default: "./outside-counsel-matter-budgets.csv"
+    description: "Path to a CSV with columns: matter_name,firm_name,approved_budget,billed_to_date. One row per matter with active outside counsel."
+  warn_at_percent:
+    default: 80
+    description: Percent of approved budget billed at which a matter gets flagged.
+compatible_agents: [generic, claude, codex]
+notes: Update billed_to_date from approved invoices (e.g. e-billing/LEDES exports) before each run — this only compares numbers you supply, it doesn't parse invoices itself.

package/jobs/legal/settlement-payment-schedule-tracker.yaml

@@ -0,0 +1,34 @@
+id: settlement-payment-schedule-tracker
+version: 1
+name: Settlement Payment Schedule Tracker
+description: >
+  Checks scheduled settlement agreement installment payments — both
+  owed and owed to you — and flags anything due soon or missed. Use this
+  if a settlement installment has ever been paid late (risking default
+  terms kicking back in) or received late without anyone noticing until
+  the next reconciliation.
+category: legal
+tags: [legal, settlement, payment-schedule, litigation]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn={{warn_days}} '
+    NR>1 && $5 == "unpaid" {
+      cmd="date -d \"" $4 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $4 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left < 0) print "MISSED: " $1 " installment #" $2 " ($" $3 ") was due " $4 " (" (days_left*-1) " days overdue)";
+      else if (days_left <= warn) print "DUE SOON: " $1 " installment #" $2 " ($" $3 ") due " $4 " (" days_left " days)";
+    }
+  ' {{settlements_csv}}
+variables:
+  settlements_csv:
+    default: "settlement-payment-schedule.csv"
+    description: "CSV with header row, columns: matter_or_counterparty,installment_number,amount,due_date(YYYY-MM-DD),status(paid/unpaid)."
+  warn_days:
+    default: 7
+    description: Days before an installment's due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Update the status column as each installment clears — this only reads dates and status you supply, it doesn't confirm receipt/disbursement of funds itself.

package/jobs/legal/timekeeper-billable-hours-compliance-check.yaml

@@ -0,0 +1,39 @@
+id: timekeeper-billable-hours-compliance-check
+version: 1
+name: Timekeeper Billable Hours Compliance Check
+description: >
+  Checks attorneys and paralegals against their weekly timesheet
+  submission and minimum billable-hour targets, and flags anyone missing
+  or short. Use this if unbilled time has ever quietly leaked out of a
+  matter because a timekeeper fell behind on entering hours and nobody
+  caught it before the billing cycle closed.
+category: legal
+tags: [legal, timekeeping, billable-hours, compliance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{min_weekly_hours}}" '
+    NR==1 {next}
+    {
+      hours = $3 + 0;
+      if ($3 == "" ) {
+        printf "MISSING TIMESHEET: %s — week of %s not submitted\n", $1, $2;
+      } else if (hours < target) {
+        printf "SHORT OF TARGET: %s — week of %s logged %.1f hrs (target %s)\n", $1, $2, hours, target;
+      }
+    }
+  ' "{{timesheets_csv_path}}"
+variables:
+  timesheets_csv_path:
+    default: "./timekeeper-hours.csv"
+    description: "Path to a CSV with columns: timekeeper_name,week_start_date (YYYY-MM-DD),billable_hours_logged (blank if not yet submitted). One row per timekeeper per week."
+  min_weekly_hours:
+    default: 30
+    description: Minimum billable hours expected per timekeeper per week before flagging a shortfall.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Distinct from any HR timesheet/payroll job — this checks billable-hour
+  compliance for legal timekeepers against matter-billing targets, not
+  hourly payroll attendance. Export the CSV from your time & billing
+  system before each run.

package/jobs/legal/trademark-infringement-watch.yaml

@@ -0,0 +1,43 @@
+id: trademark-infringement-watch
+version: 1
+name: Trademark Infringement Watch
+description: >
+  Searches for new trademark applications, domain registrations, and
+  marketplace listings that look like they could infringe on your
+  registered marks, and summarizes anything worth a closer look. Use
+  this if you've ever found out about a confusingly similar competitor
+  mark or copycat domain months after it started causing customer
+  confusion, instead of when it first appeared.
+category: legal
+tags: [legal, trademark, ip, infringement-watch]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check for potential infringement of these registered marks:
+  {{marks_to_watch}} (owned in classes/goods: {{goods_or_classes}}).
+  1. Search recent trademark application filings (e.g. via the relevant
+     trademark office's public search/TESS-style database) for new marks
+     confusingly similar in name or logo, filed in overlapping
+     goods/services classes.
+  2. Search for newly registered domain names that are close
+     misspellings or lookalikes of {{marks_to_watch}}.
+  3. Spot-check major marketplaces/app stores for listings using the mark
+     or a confusing variant without authorization.
+  4. For each hit, summarize: what was found, how similar it is, and
+     whether it looks like routine noise or worth flagging to counsel.
+  5. This is a monitoring aid, not legal advice on whether infringement
+     exists — say so, and recommend counsel review anything flagged.
+variables:
+  marks_to_watch:
+    default: "list your registered trademark(s) here"
+    description: The registered mark(s)/brand name(s) to watch for lookalikes.
+  goods_or_classes:
+    default: "your registered goods/services classes"
+    description: The goods/services or trademark classes your registration covers, to judge overlap.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Distinct from `trademark-renewal-reminder`, which tracks renewing your
+  own registration — this watches for others potentially infringing it.
+  Search coverage depends on what databases/tools the agent can actually
+  reach; a paid watch service will catch more than open search alone.

package/jobs/legal/vendor-coi-expiry-tracker.yaml

@@ -0,0 +1,37 @@
+id: vendor-coi-expiry-tracker
+version: 1
+name: Vendor Certificate of Insurance Expiry Tracker
+description: >
+  Checks certificates of insurance you've collected from vendors and
+  contractors and warns before any expire, so a lapsed COI doesn't sit
+  unnoticed in the file. Use this if a vendor's insurance has ever lapsed
+  mid-contract and nobody found out until a claim needed it.
+category: legal
+tags: [legal, vendor-management, coi, contractor-compliance]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: COI for \"" $1 "\" (" $2 ") expires in " days_left " days (" $3 ")";
+    }
+  ' {{vendor_cois_csv}}
+variables:
+  vendor_cois_csv:
+    default: "vendor-certificates-of-insurance.csv"
+    description: "CSV with header row, columns: vendor_name,coverage_type (e.g. general-liability, workers-comp),expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before a vendor's COI expires to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Opposite direction from insurance's `certificate-of-insurance-request-check`
+  (which tracks fulfilling requests for your own COI) — this tracks
+  certificates other parties gave you, as a contract-compliance/vendor-risk
+  check rather than an insurance-desk workflow. Update the CSV whenever a
+  vendor sends a new or renewed COI.

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.