Monthly Commission (Mentor/Instructor/SMI)
Runbook (copy-paste)
Set these two and the rest follows. Everything lands in one folder per month.
YR=2026; MM=07; MON=Jul; MONTH=July # the commission month (MON = 3-letter, for file names)
YM="$YR-$MM"
DIR="/c/Users/ali_m/Downloads/$MONTH $YR Commission" # folder uses the FULL month name (June 2026 Commission, July 2026 Commission)
REPO="/c/Users/ali_m/OneDrive/Business/Colaberry Novedea/AI Projects/Colaberry Enterprise AI Leadership Accelerator"
ARCHIVE="/c/Users/ali_m/OneDrive/Business/Colaberry Novedea/Stats/Commissions/SMI Comm"
WORK="$REPO/tmp/commission-$YM" # scratch for the pipeline JSON
mkdir -p "$DIR" "$WORK"
set -a && . "$REPO/.env" && set +a # GMAIL_*, MANDRILL_API_KEY, SMTP_* for steps 1 and 7
# 1. Jackie's LATEST workbook -> $DIR/<YYYY>_<MM>_ColaberryTrainingCommissions_Original.xlsx
# (find the newest message first - she re-sends corrections under changed subjects)
# Runs LOCALLY - the repo .env has the Gmail creds. gmail_dl.js writes straight to the
# renamed path, so there is no separate rename step and nothing to md5sum.
node "$REPO/scripts/commission/gmail_dl.js" <messageId> \
"$DIR/${YR}_${MM}_ColaberryTrainingCommissions_Original.xlsx"
# 2. staff total + table image
python "$REPO/scripts/commission/build_staff_png.py" \
"$DIR/${YR}_${MM}_ColaberryTrainingCommissions_Original.xlsx" \
"$DIR/$MON $YR Staff Commission.png" "$MON"
# 3. cut the reusable pipeline out of Ali's SMI Commission.sql
python "$REPO/scripts/commission/extract_pipeline.py" \
"$ARCHIVE/SMI Commission.sql" "$WORK/smi_pipeline.sql"
# 4. run it against CCPP from inside accelerator-backend (see "Running queries against CCPP").
# THE ONLY STEP THAT NEEDS PROD. The auto-mode classifier blocks writes to the prod host
# (scp, base64-pipe and ssh-stdin alike) until Ali grants a Bash permission rule.
# CM_YEAR / CM_MONTH are REQUIRED - the script exits 2 rather than guess a month.
# Ship smi_pipeline.sql + run_smi_pipeline.js to /app, then:
# docker exec -w /app -e CM_YEAR=$YR -e CM_MONTH=${MM#0} accelerator-backend \
# node run_smi_pipeline.js
# It prints COMPANY_PAID= and ALI_COMM=. Copy smi_detail/smi_summary/ipbc_<mon>.json
# back into $WORK, then delete them and the scripts from the container.
# 5. build the month tabs (same CM_YEAR / CM_MONTH contract; reads the prior month
# from $ARCHIVE and refuses if the JSON's newest month is not the reporting month)
CM_YEAR=$YR CM_MONTH=${MM#0} CM_DIR="$DIR" CM_DATA_DIR="$WORK" \
python "$REPO/scripts/commission/build_month_tabs.py"
# 6. THE GATE - nothing sends unless this exits 0
python "$REPO/scripts/commission/preflight.py" --month $YM --dir "$DIR"
# 7. dry run, read the body, then send - both run LOCALLY off the .env sourced above.
# The sender embeds Ali's REAL Outlook signature (logo + button) from the kit and refuses to
# send without it. The kit is .claude/skills/inbox-zero/assets/{ali_signature.html,
# ali_signature_logo.png}; if this checkout lacks it, point ALI_SIG_DIR at a tree that has it.
export ALI_SIG_DIR="$REPO/.claude/skills/inbox-zero/assets"
node "$REPO/scripts/commission/send_commission_email.js" --dir "$DIR"
node "$REPO/scripts/commission/send_commission_email.js" --dir "$DIR" --send
# then CONFIRM IN GMAIL (one signature block, the button, the two figures). The SMTP 250 is
# a signal, not the thing. Then archive Jackie's email AND the BCC copy: both are addressed.
# 8. close the loop, then archive
python "$REPO/scripts/commission/preflight.py" --month $YM --dir "$DIR" --record
cp "$DIR/${YR}_${MM}_SMI Commisions.xlsx" "$DIR/IPBC Group $MON $YR.xlsx" "$ARCHIVE/"
rm -rf "$WORK" # smi_detail.json carries student names and repo tmp/ is NOT gitignoredrun_smi_pipeline.js and build_month_tabs.py take the reporting month from
CM_YEAR / CM_MONTH and have no defaults. That is deliberate: both were
previously hardcoded to the month last run, so an unchanged re-run would have
silently rebuilt the prior month's numbers under the new month's filename. They
now exit rather than guess, and build_month_tabs.py additionally asserts that
the newest month in smi_detail.json is the month you asked for.
Keep the month folder path short. Windows still enforces a 260-character path limit and
openpyxl fails on longer ones; ~/Downloads/<Mon> <Year> Commission is well inside it.
The recurring monthly payroll hand-off. It always starts with an email from
jackie@colaberry.com (historically mika@colaberry.com) and always ends with one
email from Ali to accounting@colaberry.com.
This is payroll. Every number in the outbound email must trace to a file, and two of the five inputs come from outside this repo. Never estimate, interpolate, or "reasonably assume" a commission figure. If an input is missing, stop and ask.
The contract
Inbound trigger — email from jackie@colaberry.com, subject like April Commission 2026
or Updated Ali Commission 2026, body "Hi Ali / <Month> Commission is done.", with one
.xlsx attached. The same workbook is also posted to the Basecamp New Leaders Group
thread (New Leaders Group) <Month> Commission <Year>.
Outbound deliverable — one email:
| Field | Value |
|---|---|
| To | accounting@colaberry.com |
| Bcc | ali@colaberry.com |
| Subject | <Mon> <Year> Commission (Mentor/Instructor/SMI) — 3-letter month: Feb, Mar, Apr |
| Body line 1 | Staff Commission: $<total> |
| Body line 2 | Ali Commission: $<total> |
| Body | then the staff commission table image, inline |
| Signature | Ali's standard block (see below) |
Attachments (4):
<YYYY>_<MM>_ColaberryTrainingCommissions_Original.xlsx<YYYY>_<MM>_SMI Commisions.xlsx← note the historical misspelling, keep itIPBC Group <Mon> <Year>.xlsx<Mon> <Year> Staff Commission.png(Feb was a separate attachment; Mar was inlinecid:. Either is accepted.)
Sends to date:
Feb 2026 Commission (Mentor/Instructor/SMI)— 2026-06-06 — Staff $11,325 / Ali $1,907.19Mar 2026 Commission (Mentor/Instructor/SMI)— 2026-07-09 — Staff $10,000 / Ali $2,143.44Apr 2026 Commission (Mentor/Instructor/SMI)— 2026-08-12 — Staff $11,950.00 / Ali $2,077.45 (first run of this skill end to end)May 2026 Commission (Mentor/Instructor/SMI)— 2026-08-19 — Staff $9,425.00 / Ali $1,699.25 (CompanyPaid $15,104.44, tier 0.15; no IPBC rows, so both the IPBC tab and the SMIIPBC - Enrollmentline are absent, as in April)Jun 2026 Commission (Mentor/Instructor/SMI)— 2026-09-06 — Staff $9,175.00 / Ali $1,966.28 (CompanyPaid $17,478.02, tier 0.15; IPBC is back after two absent months — 1 row, $96.00. Jackie's attachment arrived already namedJune Commission 2026 updated.xlsx, so the "take the LATEST version" check passed on the first file for once.)Jul 2026 Commission (Mentor/Instructor/SMI)— 2026-09-17 — Staff $6,875.00 / Ali $3,557.79 (CompanyPaid $27,904.24, tier 0.17 / 12.75%: the first month over the $20,000 boundary; preflight raised the RATE TIER CHANGED warning exactly as designed. IPBC 46 rows, $9,956.80. Jackie's email said "June Commission is done" in the body but the subject, the filename and the Staff Sessions dates (7/1 to 7/25) were all July; the workbook decides, not the body line. First send with Ali's real Outlook signature kit instead of the typed-in lookalike.)
Step 1 — Take the LATEST version of Jackie's workbook
Mentors dispute their own lines in the Basecamp thread and Jackie re-posts a corrected file. Always process the most recent attachment, not the first one.
Real example (April 2026): Jackie sent the workbook 2026-08-10; Dozie replied "Please add the
April 28th class, the total should be $1900 and not $1700"; Jackie re-sent the corrected
workbook 2026-08-11 under the subject Updated Ali Commission 2026. Processing the 8/10 file
would have underpaid Dozie by $200.
Before continuing, search for later messages in both channels:
# Gmail (MCP): both the direct thread and any "Updated ..." subject
from:jackie@colaberry.com newer_than:30d
# Basecamp thread
subject:"(New Leaders Group)" <Month> CommissionDownload the attachment (Gmail MCP has no attachment reader — use the prod backend's own Gmail credentials):
scripts/commission/gmail_dl.js <messageId> /app/out.xlsx # run inside accelerator-backendSave it, renamed, to ~/Downloads/<Month> <Year> Commission/:
<YYYY>_<MM>_ColaberryTrainingCommissions_Original.xlsxThis is a pure rename — the bytes must not change. Verified: February Commission 2026.xlsx
and 2026_02_ColaberryTrainingCommissions_Original.xlsx are md5-identical, likewise March.
Confirm with md5sum before and after.
Step 2 — Staff Commission total + the table image
The workbook has 7 sheets. Only Staff Commissions matters here: column A = Name,
column T = Total Comm.
Staff Commission = SUM(column T). Nothing else. Verified: March summed to exactly $10,000 and February to exactly $11,325, both matching the sent emails.
Run the bundled generator — it prints the total and renders the PNG in the established style
(white ground, 1px black grid, Name | Total Comm header, right-aligned $X,XXX.00, bold
Total row):
python scripts/commission/build_staff_png.py \
"<...>/<YYYY>_<MM>_ColaberryTrainingCommissions_Original.xlsx" \
"<...>/<Mon> <Year> Staff Commission.png" "<Mon>"Self-check before trusting it: run the same script against
~/Downloads/February Commission 2026.xlsx; it must print 11325.00. If it doesn't, the
sheet layout changed — stop and re-read the workbook rather than shipping a wrong total.
Ignore the Mgmt sheet. Manager Commission and Shveta's $390 were dropped from the email
after Jan 2026; Feb and Mar carry Staff + Ali only. Do not reintroduce them.
Step 3 — SMI Commissions workbook ⚠ OPERATOR INPUT REQUIRED
<YYYY>_<MM>_SMI Commisions.xlsx is a long-lived workbook (~5.5 MB, one tab per month back
to 2017). Each month a new tab named <Mon> <Year> is added at the front, holding a full
re-export, and the file is saved under the new month's name.
Tab layout, columns A–I (all pasted values — there are no formulas anywhere in the file):
| Col | Field |
|---|---|
| A | SMIC_SalesRep (SMI for nearly every row) |
| B | SMIC_Name (student; the IPBC invoices roll up to one row named IPBC - Enrollment) |
| C–D | OrderMonth, OrderYear |
| E | TotalPaid |
| F | AliComm (tiered — see below) |
| G | SalesRepComm (NULL for SMI rows; the export writes the literal string NULL) |
| H–I | MonthlyPaid, MonthlyPaidMinus25per — the month total, repeated on every row |
Columns K–N hold the running summary: Name | OrderMonth | OrderYear | Comm, one row per
month, Name = ALI.
Ali Commission = the month's Comm in that K:N block = ROUND(SUM(AliComm), 2).
The rate is TIERED — do not hardcode 11.25%
TotalPaidMinus25Per is TotalPaid × 0.75, and the rate on it depends on CompanyPaid
(the month's SMI total):
| Row type | AliComm |
|---|---|
SMIC_SalesRep = 'SMI', CompanyPaid < 20,000 |
TotalPaidMinus25Per × 0.15 → effective 11.25% |
SMIC_SalesRep = 'SMI', CompanyPaid 20,000–50,999 |
TotalPaidMinus25Per × 0.17 → effective 12.75% |
SMIC_SalesRep = 'SMI', CompanyPaid ≥ 51,000 |
TotalPaidMinus25Per × 0.20 → effective 15% |
| Named sales rep (not SMI, not Job Referral) | TotalPaidMinus25Per × 0.05 |
| Job Referral Sales Rep, or NULL | (TotalPaid × 0.75) × 0.15 |
Every month sent so far has sat in the bottom tier, which is the only reason a flat 11.25%
appeared to work. A month clearing $20,000 changes the rate. Let the SQL decide; preflight.py
cross-checks the figure against the tier and shouts when the tier moves.
Measured 2026 (from CCPP on 2026-08-13) — note July:
| Month | CompanyPaid | Tier | Effective | AliComm |
|---|---|---|---|---|
| Jan | $18,810.80 | 0.15 | 11.25% | $2,116.22 |
| Feb | $16,952.80 | 0.15 | 11.25% | $1,907.19 |
| Mar | $19,052.83 | 0.15 | 11.25% | $2,143.44 |
| Apr | $18,466.26 | 0.15 | 11.25% | $2,077.45 |
| May | $15,104.44 | 0.15 | 11.25% | $1,699.25 |
| Jun | $17,478.02 | 0.15 | 11.25% | $1,966.28 |
| Jul | $28,053.24 | 0.17 | 12.75% | $3,576.79 |
July 2026 crosses the boundary. At the old flat 11.25% it would come out $3,155.99 — $420.80 short. March cleared the boundary by only $947, so this is genuinely volatile month to month, not a one-off. Never carry a rate forward from last month.
These are point-in-time figures: late payments and reversals keep landing in past months, so re-run rather than quoting this table. It is here to show the boundary is live, not as a source.
The source query
C:\Users\ali_m\OneDrive\Business\Colaberry Novedea\Stats\Commissions\SMI Comm\SMI Commission.sql
That folder is also the archive — every month's <YYYY>_<MM>_SMI Commisions.xlsx and
IPBC Group <Mon> <Year>.xlsx lives there. Copy the new month's files back into it after
sending.
The file is UTF-16LE; decode before use (open(p,'rb').read().decode('utf-16')).
Three things to know before running it:
- Drop the hand-toggled filter. The two trailing
SELECTs carryWHERE OrderMonth NOT IN (2,3,4,5)— a leftover Ali edits by hand. Run the pipeline up to and including theINTO #SMI_CommIIIstatement, then supply your own unfiltered SELECTs.scripts/commission/run_smi_pipeline.jsdoes exactly that. - It depends on
GETDATE(). The#AdjustAmountblock projects contracted payments forward forDATEDIFF(MM, GETDATE(), SMIC_PayEndDate)months, so historical row counts shift between runs. This is normal and visible in the archive — the Jan/Feb/Mar 2026 tabs hold 6,556 / 5,316 / 5,377 rows. Monthly totals are stable even though row counts are not; verified by reproducing Nov 2025 through Mar 2026 to the cent months later. #AdjustAmountis why a couple of students show at ~2× their actual payments. Students withSMIC_Status = 11who paid more than once in a month get their contractedSMIC_PaymentAmountprojected forward, and theNOT INde-dup misses when the name join resolves differently — so the actual and contracted rows both land. It is longstanding behaviour baked into every prior month; do not "fix" it silently.
After building the tab, validate:
- The new tab's
MonthlyPaidis identical on every row of the month. - The K:N
ALIrow for the month equalsSUM(F)rounded to 2dp. - Prior months in K:N still match what was emailed for those months. This is the real regression test — Feb must be 1,907.19, Mar 2,143.44, Dec 2025 3,768.11, Nov 2025 1,177.93. If an old month moved, the basis was restated and that needs flagging, not shipping.
- Carried-over tabs survived the openpyxl round-trip unchanged (row count +
TotalPaidsum).
Step 4 — IPBC Group workbook
IPBC Group <Mon> <Year>.xlsx is the supporting detail for the single IPBC - Enrollment
line in the SMI tab. Same pattern: one tab per month, newest first, columns straight out of
vw_ADF_PaySimple plus the SMIC_* join columns; rows are the IPBC - Enrollment invoices.
Cross-check: the tab's Amount Paid must sum to the IPBC - Enrollment row's TotalPaid
in the SMI tab. Verified for March 2026: 0.01 + 49 + 0.01 + 0.01 = 49.03, matching the
SMI tab's IPBC - Enrollment 49.03 exactly. If the two disagree, one of the exports is stale.
These are the same rows the main query rolls up — the ones with no name match, which is what
makes them IPBC - Enrollment:
SELECT p.[Customer #], p.Source, p.[Order Date], p.Status, p.Total,
p.[Amount Paid], p.[Balance Due], p.ModifiedDate,
p.SMIC_SalesRep, p.SMIC_CommID, p.SMIC_UserID
FROM [dbo].[vw_ADF_PaySimple] p
LEFT JOIN ( SELECT DISTINCT SMIC_Name, SMIC_ID, PS_CUSTOMERID
FROM dbo.vw_ADF_Student_Marketing_SalesRepsCommSystem
UNION ALL
SELECT StudentName, SMIC_ID, PS_CustomerID
FROM [dbo].[vw_ADF_Student_Marketing_SalesRepsIPBC_Signups] ) b
ON p.[Customer #] = b.PS_CUSTOMERID
WHERE p.[Amount Paid] > 0 AND b.SMIC_Name IS NULL
AND Month(p.[Order Date]) = @mm AND Year(p.[Order Date]) = @yyyyIf it returns nothing, the month still gets a tab containing the single cell
No Data for the month — the established convention (see the Feb/Mar/May 2024 tabs). April
2026 was such a month: no IPBC enrolments, so no IPBC - Enrollment row in the SMI tab either.
Step 5 — Preflight, then send
Nothing goes to accounting until preflight.py exits 0. It derives both figures from the
files rather than trusting anything typed, and it is the only thing that writes the
send_manifest.json the sender requires.
python scripts/commission/preflight.py --month 2026-05 --dir "~/Downloads/May 2026 Commission"Six gates, any FAIL blocks the send:
| # | Gate | Catches |
|---|---|---|
| 1 | Idempotency vs ledger.json |
Double-sending a month to accounting |
| 2 | All four attachments present, non-zero, under 20 MB | A missing or truncated file |
| 3 | Staff total re-derived from column T, header shape asserted | A moved column silently changing the total |
| 4 | Ali figure read from K:N, cross-checked against the tier | Pasting the wrong rows, or the wrong rate |
| 5 | Every prior month still computes to what was emailed | A restated basis |
| 6 | Carried-over month tabs survived the rebuild | openpyxl round-trip corruption |
Then dry-run, send, and close the loop:
node scripts/commission/send_commission_email.js --dir "<dir>" # dry run, prints the body
node scripts/commission/send_commission_email.js --dir "<dir>" --send # in accelerator-backend
python scripts/commission/preflight.py --month 2026-05 --dir "<dir>" --recordThe sender carries no figures of its own — it reads the manifest, re-hashes all four attachments against it, and aborts if any file changed since preflight. Verified by break test: a one-byte change to an attachment aborts with exit 1; a missing manifest exits 2.
The body, exactly as Feb / Mar / Apr said it:
Staff Commission: $11,950.00
Ali Commission: $<from step 3>
<staff commission table image>
<Ali's real Outlook signature: logo, name, title, Colaberry Inc., address, email + site, button>Amounts carry thousands separators and 2 decimals. No em-dashes in body copy; the sender asserts
this on the text part. The signature is not typed into the script (Ali, 2026-09-15: "I have a
valid signature - use that and don't duplicate"): send_commission_email.js reads
ali_signature.html and attaches ali_signature_logo.png inline under the cid the block names,
asserts the block appears exactly once, and aborts if the kit is missing (ALI_SIG_DIR, then
.claude/skills/inbox-zero/assets, /tmp/ali-signature, /root/ali-signature). The text/plain
part carries the plain fallback block with the slash title, same as sendAsAli.js.
Step 6 — After sending
- Reply to any waiting nudge (Nazma/HR chases this for payroll — e.g. "Could you please send over the commission list? As we are approaching payroll").
- Keep the month's folder at
~/Downloads/<Month> <Year> Commission/with all four artifacts. - Do not add a PROGRESS.md entry. Per CLAUDE.md, outbound email sent on Ali's behalf and ad-hoc data pulls are explicitly out of scope for PROGRESS.md. Changes to this skill do belong there.
Cast
| Who | Role |
|---|---|
jackie@colaberry.com |
Event Manager — produces the staff commission workbook (took over from mika@colaberry.com around Apr 2026) |
accounting@colaberry.com |
Destination; processes the payout |
nazma@colaberry.com |
Sr. HR Manager — chases for payroll |
| Basecamp New Leaders Group | Where mentors dispute lines and Jackie posts corrections |
Running queries against CCPP
CCPP holds no credentials locally. Run read-only queries from the prod backend, which already
has MSSQL_* in its environment and the mssql package installed:
B64=$(base64 -w0 query.js)
ssh root@95.216.199.47 "echo '$B64' | base64 -d > /tmp/q.js \
&& docker cp /tmp/q.js accelerator-backend:/app/q.js \
&& docker exec -w /app accelerator-backend node q.js; \
docker exec accelerator-backend rm -f /app/q.js; rm -f /tmp/q.js"Clean up the script and any downloaded PII afterwards. Note the view's column names contain
spaces and must be bracketed: [Customer #], [Order Date], [Amount Paid].
CCPP is the ONLY step that needs prod
Steps 1, 2, 3, 5, 6 and 7 all run locally. The repo-root .env carries GMAIL_*,
MANDRILL_API_KEY and SMTP_*, so gmail_dl.js and send_commission_email.js do not need
to be shipped to accelerator-backend — load the env and run them on the workstation:
set -a && . ./.env && set +a
node scripts/commission/gmail_dl.js <messageId> "<dir>/<YYYY>_<MM>_ColaberryTrainingCommissions_Original.xlsx"
node scripts/commission/send_commission_email.js --dir "<dir>" --sendOnly run_smi_pipeline.js genuinely needs prod, because MSSQL_* exists nowhere else.
Verified end to end on the June 2026 run: local Gmail download and local Mandrill send both
worked, and the send was confirmed in Gmail rather than trusted from the SMTP 250.
The auto-mode classifier blocks writes to prod
On the June 2026 run, every route for getting a file onto the prod host was denied by the
auto-mode classifier — base64 -w0 | ssh 'base64 -d > file', scp, and
ssh 'cat > file' alike. Plain read-only ssh root@... "hostname" and docker exec ... ls
were never blocked; the boundary is writing to production, not SSH itself.
This stalls the run at step 4 with no way past it, and the figure it produces cannot be
guessed — see the "never estimate" rule at the top. Either add a standing Bash permission rule
for scp/ssh to 95.216.199.47, or expect to ask Ali to authorize it mid-run. Do not
fall back to the stale figures in the tier table below; they are point-in-time and were already
three weeks old when June ran.
Bundled scripts
Run in this order. All of them run locally off the repo-root .env except
run_smi_pipeline.js, which needs MSSQL_* and therefore has to execute inside
accelerator-backend.
| # | Script | Purpose |
|---|---|---|
| 1 | gmail_dl.js |
Downloads Jackie's attachment by message id (the Gmail MCP connector cannot read attachments). Runs locally on the repo .env's GMAIL_*; no need to ship it to prod. |
| 2 | build_staff_png.py |
Reads Staff Commissions, prints the staff total, renders the table PNG. Self-validates against February. |
| 3 | extract_pipeline.py |
Decodes SMI Commission.sql (UTF-16LE) and cuts it at the end of the INTO #SMI_CommIII statement. Refuses to emit anything that still carries the hand-toggled OrderMonth NOT IN filter or is missing a temp table. |
| 4 | run_smi_pipeline.js |
Runs that pipeline against CCPP; writes smi_detail.json, smi_summary.json, ipbc_<mon>.json. |
| 5 | build_month_tabs.py |
Copies last month's SMI + IPBC workbooks, prepends the new <Mon> <Year> tab to each, saves under the new month's name. |
| 6 | preflight.py |
The gate. Six checks, writes send_manifest.json on pass. Nothing sends without it. |
| 7 | send_commission_email.js |
Reads the manifest, re-hashes every attachment, sends via Mandrill with the PNG inline as cid:staffcomm. Dry run by default. |
| 8 | preflight.py --record |
Appends the month to ledger.json after a confirmed send. |
| — | verify_month.py |
Standalone read-back, kept for ad-hoc inspection. preflight.py supersedes it in the flow. |
| — | ledger.json |
Every month ever sent. Idempotency record, regression baseline, and tier history in one file. |
Step 7 uses raw nodemailer rather than sendWithBcAttach, which hard-requires a Basecamp
ticketId. This email has no originating ticket — Feb and Mar went straight from Outlook with
no BC attachment — and the helper's own guard directs that case to raw nodemailer.
If a mentor disputes after the send
It happens (Dozie did it for April, before the send). The basis is Jackie's workbook, so:
- Jackie issues a corrected workbook — she owns the staff numbers, not us.
- Re-run from Step 1 with the new file into the same month folder.
preflight.pywill refuse: the month is in the ledger. That is working as designed. Pass--forceonce you have confirmed a correction is genuinely intended.- Subject the correction clearly, e.g.
Apr 2026 Commission (Mentor/Instructor/SMI) - corrected, and say in one line what moved and for whom. Do not resend a bare duplicate. --recordagain afterwards; add anoteon the ledger entry saying what changed.
Ali's own figure never changes in this scenario — it comes from CCPP, not from Jackie's sheet.