Skip to main content

September Builds — Mandate Plans

Mandates PS-020 through PS-028: automation builds, ATS migration, and Docebo configuration. These shift from "do the work" to "build the thing that does the work."

PS-020: Build Lifecycle Agent (Job Changes)​

What to build​

A structured workflow agent that handles the 100+ task job-change checklist. The agent walks through each task, pre-fills what it can from Paylocity data, flags what needs human input, and tracks completion. Proposes changes for human approval (propose-then-approve pattern).

Dependencies​

  • PS-002 instrumentation must be done first. You need to have processed job changes manually in August and documented every step before you can automate them.
  • The 100-task checklist needs to be recovered from Syra or Shlanda (it may be in Paylocity's internal checklist feature, a Google Sheet, or someone's head).
  • Paylocity field access via the CMPRSSN account.

Technical approach​

Follow the existing agent pattern: Apps Script + spreadsheet config + human-in-the-loop gates. The recon agent's runJobChangeCloseout() already verifies job changes on Monday; the lifecycle agent would be the workflow that runs the actual change, not just the verification.

Build pattern​

From methodology/build/: "Deterministic audit" pattern. Agent builds checklist, never calls an AI model. Rules as data (spreadsheet rows). Over-flag-then-converge (catch everything, then tune down false positives with Syra's input).

PS-021: Build Onboarding Orchestration Agent​

What to build​

An agent that coordinates the 9-system onboarding handoff: when a hire is confirmed in Greenhouse, it triggers a sequence of provisioning steps across Paylocity, Drive, Legion, LMS, Lattice, Fringe, Slack. The agent tracks which steps are complete and alerts when one is missing or late.

Dependencies​

  • PS-005 and PS-006 instrumentation from August.
  • Greenhouse API status: if the feed is broken, the agent needs a different trigger (manual input or webhook).
  • Access to all 9 systems (or at least the ones with APIs/export paths).

Technical approach​

Two options:

  1. Apps Script orchestrator (consistent with existing agents) — checks each system via API or inbox export, tracks completion in a spreadsheet, sends Slack notifications for missing steps.
  2. GitHub Action pipeline (like the leave-feed-sftp courier) — better for systems that require SFTP or complex auth.

Likely a hybrid: Apps Script for the core orchestration + GitHub Actions for the systems that need them (SFTP, complex auth).

PS-022: Build LMS Enrollment Automation​

What to build​

Auto-enroll new hires in the right training courses based on role, state, and hire date. Pull enrollment data from the HRIS (Paylocity or Workday) feed, match against the compliance training matrix, and assign courses in Docebo (or Wisetail if Docebo isn't live yet).

Dependencies​

  • Docebo decision (August 6 meeting).
  • Compliance training matrix from Nickole (which trainings for which states/roles).
  • Docebo API access (1,000 calls/hour/IP, OAuth 2.0) or Wisetail (no API; would need email/export workaround).

Technical approach​

If Docebo: use the Docebo REST API to enroll users and track completion. Webhook events (user.enrolled_in_course, user.completed_course) can trigger follow-up actions.

If staying on Wisetail: manual-add workaround via Apps Script (mimic what Nickole does manually).

PS-023: Build Compliance Training Auto-Launch​

What to build​

A scheduled agent that:

  1. Watches for new hires (from Paylocity or the onboarding orchestrator)
  2. Determines which compliance trainings are required (state-specific rules)
  3. Assigns them in the LMS
  4. Tracks completion and follows up on overdue

Dependencies​

  • Same as PS-022 (Docebo decision, training matrix, API access).
  • Anti-harassment audit cadence: twice yearly (mid-year and December). The agent needs to handle both new-hire auto-launch and annual refresh.

Technical approach​

Cron-triggered Apps Script that queries the HRIS for recent hires, looks up training requirements in a config spreadsheet (state x role = required courses), and assigns via LMS API.

PS-024: Build Data-Integrity Monitors (Extend Recon Agent)​

What to build​

Extend the existing reconciliation agent to cover gaps identified during August instrumentation. Likely additions:

  • Cross-system drift detection (Paylocity vs. other systems disagreeing about an employee's status)
  • Real-time anomaly alerts (currently only runs weekly)
  • Auto-clear verification for Syra's Paylocity fixes

Dependencies​

  • PS-013 August assessment of what the recon agent currently misses.
  • Syra's feedback on which findings are noise vs. genuine issues.

Technical approach​

Same Apps Script + spreadsheet pattern. Add new rule types to the FieldRules tab. May add a daily trigger for high-priority checks alongside the weekly full audit.

PS-025: Script ATS Migration (if Pinpoint)​

What to build​

A scripted migration from Greenhouse to Pinpoint:

  • Export all data from Greenhouse (offices, hiring managers, job requisitions, candidate history)
  • Transform into Pinpoint's data model
  • Load into Pinpoint programmatically (not re-keyed by hand)
  • Validate: all offices exist, all hiring managers mapped, all active requisitions moved

Dependencies​

  • ATS decision (August 6 meeting). This mandate only activates if Pinpoint is selected.
  • Greenhouse API access (Harvest API, depreciating August 31 — need to use the latest version).
  • Pinpoint API access and documentation.

Technical approach​

Python or Node script (not Apps Script; this is a one-time migration, not an ongoing agent). Use Greenhouse Harvest API to export, transform, and Pinpoint's API to load.

Timeline​

  • September: build and test migration scripts
  • October-December: run migration, validate
  • January 13, 2027: Greenhouse contract expires (hard deadline)

PS-026: Build Slack Approval Flow​

What to build​

Hiring managers approve roles directly in Slack via Pinpoint's native connector. This replaces email-based approval chains.

Dependencies​

  • Pinpoint selection (same as PS-025).
  • Pinpoint's Slack connector documentation.
  • Slack bot setup (People Team Notifications bot already exists; may need additional scopes).

Technical approach​

Use Pinpoint's native Slack integration if it handles this out of the box. If it doesn't, build a custom Slack Interactive Component (button in a message → approval action → Pinpoint API call).

PS-027: Configure Docebo LMS​

What to build​

Admin configuration of the new LMS:

  • User provisioning setup (HRIS feed auto-creates users)
  • Course structure (categories, tags, required vs. optional)
  • Compliance training automation (auto-launch based on role/state/hire date)
  • SSO (Single Sign-On) configuration if applicable
  • Integration with Slack (training notifications via the People bot)

Dependencies​

  • Docebo decision and contract (August 6 meeting).
  • Docebo sandbox environment access.
  • Nickole's input on course structure and governance.

Technical approach​

Docebo admin UI for initial config. Docebo REST API + SCIM for automated user provisioning. Webhook events for completion tracking.

PS-028: Migrate Training Content from Wisetail to Docebo​

What to build​

Move all active training content from Wisetail/CoCo to Docebo:

  • Inventory existing courses (active vs. archived)
  • Export content from Wisetail (method TBD; Wisetail has no API)
  • Import into Docebo, organize with new tag/category structure
  • Verify all courses are field-ready at launch

Dependencies​

  • Docebo configuration (PS-027) must be at least partially done.
  • Content inventory from Nickole.
  • HCB training lead buy-in — if they don't adopt Docebo, HCB content stays in Wisetail and only HQ content migrates.

Technical approach​

Likely manual export from Wisetail (screen scraping or file downloads), then Docebo API upload. Fixed-scope project; not ongoing work.

Timeline​

  • Q4 2026: Docebo build and content migration
  • Q1 2027: Content migration from Wisetail completed