@wonsukchoi/crondex 0.20.1 → 0.22.0

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/publishing/arc-review-copy-followup.yaml

@@ -0,0 +1,35 @@
+id: arc-review-copy-followup
+version: 1
+name: ARC Review Copy Followup
+description: >
+  Flags reviewers, bloggers, or media contacts who received an advance
+  review copy (ARC) but haven't posted or filed a review within a set
+  window, so a nudge can go out before the publication date. Use this if
+  ARCs have ever been sent out and quietly forgotten with no review to show
+  for them.
+category: publishing
+tags: [publishing, arc, review-copies, marketing]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v follow={{followup_days}} '
+    NR>1 && $4 == "no" {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline sent_ts; close(cmd);
+      days_since = int((today - sent_ts) / 86400);
+      if (days_since >= follow) print "FOLLOW UP: " $2 " received ARC for \"" $1 "\" " days_since " days ago, no review posted";
+    }
+  ' "{{arc_recipients_csv}}"
+variables:
+  arc_recipients_csv:
+    default: "./arc-recipients.csv"
+    description: "CSV with header row, columns: title,recipient,sent_date(YYYY-MM-DD),review_posted(yes|no)."
+  followup_days:
+    default: 21
+    description: Days after sending an ARC to wait before flagging a followup nudge.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Mark review_posted=yes in arc-recipients.csv as reviews come in so they
+  stop being flagged. Pair with your publicist's contact list export.

package/jobs/publishing/isbn-registration-tracker.yaml

@@ -0,0 +1,35 @@
+id: isbn-registration-tracker
+version: 1
+name: ISBN Registration Tracker
+description: >
+  Flags upcoming titles that don't yet have an ISBN assigned and registered
+  with the relevant agency, checked against their planned publication date.
+  Use this if a title has ever hit its pub date without an ISBN because
+  registration wasn't started early enough.
+category: publishing
+tags: [publishing, isbn, metadata, pre-press]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v lead={{lead_days}} '
+    NR>1 {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline pub_ts; close(cmd);
+      days_left = int((pub_ts - today) / 86400);
+      if ($3 == "" && days_left <= lead) print "MISSING ISBN: \"" $1 "\" publishes in " days_left " days (" $2 ") — no ISBN registered";
+    }
+  ' "{{titles_csv}}"
+variables:
+  titles_csv:
+    default: "./upcoming-titles.csv"
+    description: "CSV with header row, columns: title,pub_date(YYYY-MM-DD),isbn(blank if not yet assigned)."
+  lead_days:
+    default: 60
+    description: Days before publication to start warning if an ISBN is still missing.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update upcoming-titles.csv as soon as an ISBN is assigned so the title
+  drops off the warning list. Registration lead time varies by agency, so
+  set lead_days to comfortably exceed your agency's typical turnaround.

package/jobs/publishing/manuscript-deadline-tracker.yaml

@@ -0,0 +1,34 @@
+id: manuscript-deadline-tracker
+version: 1
+name: Manuscript Deadline Tracker
+description: >
+  Flags manuscript milestones (first draft, revisions, final delivery) coming
+  due from authors or editors. Use this if a book has ever slipped its
+  production schedule because a manuscript deadline only lived in an email
+  thread nobody rechecked.
+category: publishing
+tags: [publishing, manuscripts, authors, deadlines]
+schedule: "0 9 * * 1-5"
+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 due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "DUE SOON: \"" $1 "\" (" $2 ") milestone due in " days_left " days (" $3 ")";
+    }
+  ' "{{manuscripts_csv}}"
+variables:
+  manuscripts_csv:
+    default: "./manuscripts.csv"
+    description: "CSV with header row, columns: title,milestone(draft|revision|final),due_date(YYYY-MM-DD)."
+  warn_days:
+    default: 7
+    description: Days before a milestone due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Keep manuscripts.csv updated with each title's next milestone as it's
+  scheduled or renegotiated with the author/editor.

package/jobs/publishing/permissions-clearance-tracker.yaml

@@ -0,0 +1,36 @@
+id: permissions-clearance-tracker
+version: 1
+name: Permissions Clearance Tracker
+description: >
+  Flags quoted material, images, lyrics, or other third-party content in a
+  forthcoming title that still needs permissions clearance before the book
+  goes to press. Use this if a title has ever gone to print with an
+  uncleared quote or image because clearance status wasn't tracked
+  centrally.
+category: publishing
+tags: [publishing, permissions, rights-clearance, pre-press]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v lead={{lead_days}} '
+    NR>1 && $4 != "cleared" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline pub_ts; close(cmd);
+      days_left = int((pub_ts - today) / 86400);
+      if (days_left <= lead) print "UNCLEARED: \"" $1 "\" — item \"" $3 "\" status=" $4 ", publishes in " days_left " days";
+    }
+  ' "{{permissions_csv}}"
+variables:
+  permissions_csv:
+    default: "./permissions-clearances.csv"
+    description: "CSV with header row, columns: title,pub_date(YYYY-MM-DD),item_description,status(pending|requested|denied|cleared)."
+  lead_days:
+    default: 30
+    description: Days before publication to start warning about any item not yet marked cleared.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update permissions-clearances.csv as each request is sent, denied, or
+  cleared. A "denied" item still shows up here deliberately — it needs
+  editorial follow-up (cut or replace) before press, not just tracking.

package/jobs/publishing/print-run-reorder-threshold-check.yaml

@@ -0,0 +1,32 @@
+id: print-run-reorder-threshold-check
+version: 1
+name: Print Run Reorder Threshold Check
+description: >
+  Flags titles whose warehouse stock has dropped below the reorder
+  threshold, so a reprint can be queued before the book goes out of stock.
+  Use this if a title has ever gone unavailable for weeks because nobody
+  noticed the print run was running low until it was already sold out.
+category: publishing
+tags: [publishing, print-run, inventory, reprints]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v default_threshold={{default_reorder_threshold}} '
+    NR>1 {
+      threshold = ($3 != "" ? $3 : default_threshold);
+      if ($2+0 <= threshold+0) print "LOW STOCK: \"" $1 "\" at " $2 " units (reorder threshold " threshold ")";
+    }
+  ' "{{stock_csv}}"
+variables:
+  stock_csv:
+    default: "./print-run-stock.csv"
+    description: "CSV with header row, columns: title,units_in_stock,reorder_threshold(optional, blank uses default)."
+  default_reorder_threshold:
+    default: 250
+    description: Fallback reorder threshold (in units) used when a title's row doesn't set its own.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update print-run-stock.csv from your distributor or warehouse inventory
+  export before each run. Reorder threshold should account for reprint
+  lead time, not just current demand.

package/jobs/publishing/rights-license-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: rights-license-expiry-check
+version: 1
+name: Rights and License Expiry Check
+description: >
+  Warns you before a granted or acquired rights/licensing deal (foreign
+  rights, film/TV options, audio, translation) expires or comes up for
+  renewal. Use this if a rights deal has ever lapsed silently because the
+  expiry date only lived in the signed contract's PDF.
+category: publishing
+tags: [publishing, rights, licensing, contracts]
+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 " rights for \"" $1 "\" expire in " days_left " days (" $3 ")";
+    }
+  ' "{{rights_csv}}"
+variables:
+  rights_csv:
+    default: "./rights-licenses.csv"
+    description: "CSV with header row, columns: title,rights_type(foreign|film|audio|translation|other),expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 45
+    description: Days before a rights expiry date to start warning, so renegotiation or renewal can start in time.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Covers both rights you've acquired (e.g. translation rights into a
+  language) and rights you've granted out (e.g. a film option). Keep
+  rights-licenses.csv updated from your contracts database.