CSJ Compliance Command Center — Inconsistency Check

Date: 2026-08-29 Source: Google Sheet "CSJ Compliance Command Center" (exported to data/*.json, one file per tab; snapshot taken 2026-08-29 from sheet last modified 2026-08-29 17:32 UTC) Method: Cross-tab consistency checks across all 14 tabs — state coverage, rule-type and confidence agreement (Tab 1 vs Tab 5), derived-date arithmetic, Deadline Calendar completeness and date agreement, registration-number cross-references, RA-tab coherence, and status-field logic.

What checked out clean

• Rule Type, Rule Confidence, and Derived Next Due in Tab 1 match Tab 5 exactly for all 52 jurisdictions.
• Every charitable-renewal row in the Deadline Calendar matches Tab 1's "Next Renewal Due (AUTO)" date.
• Every Tab 1 "Awaiting Labyrinth Answer? = YES" state has a matching open question in Tab 9.
• "Days Until Due" arithmetic in the Deadline Calendar is correct relative to 2026-08-29.
• Registration numbers agree between the Deadline Calendar and Tabs 1/2 (the "(no # on file)" calendar entries correctly correspond to null registration numbers in Tab 1).
• RA tab (Tab 4) is consistent with Tab 1's "Charitable RA Required" column — every state requiring a charitable RA has an RA row, and vice versa.
• Duplicate state rows in the Deadline Calendar (California ×2, North Dakota ×2, Colorado ×2) are legitimate — each pair is two different filing types (e.g., entity report + charitable renewal), not errors.

Findings (ranked by importance)

1. Future dates in "Last Filed Date" — potentially masking near-term deadlines ⚠️ TIME-SENSITIVE

Three states have a future date in Tab 1's "Last Filed Date" column. The AUTO formula derives "Next Renewal Due" from Last Filed + cycle, so a future "last filed" rolls the next deadline a full year forward:

State	"Last Filed Date"	Sheet's next due	Concern
North Dakota	2026-09-01 (3 days from snapshot date)	2027-09-01	The entered date is ND's fixed due date, not a plausible filing date. If the 2026-09-01 renewal hasn't actually been filed, the sheet hides a deadline due within days.
Pennsylvania	2026-11-15 (~2.5 months out)	2027-11-15	Same pattern — the FY2025 due date appears as "last filed". If the 2026-11-15 filing isn't done, it's invisible in the calendar.
Alaska	2026-09-01	2027-09-01	Alaska is "Not Registered", so a Last Filed date is logically impossible — it's being used as a derivation seed. Harmless while unregistered, but overloads the column's meaning.

Action: Confirm with Labyrinth (or the state portals) whether the ND 2026-09-01 and PA 2026-11-15 filings are done. If they are (as Illinois's calendar row explicitly notes for its filing), add the same "already filed by Labyrinth" annotation; if not, the calendar is missing two live 2026 deadlines. For Alaska, note in the row that the date is a prospective seed, not an actual filing.

2. Washington has no Deadline Calendar row

Tab 1: Registered, next renewal due 2027-05-15, Filing Status "Not Set". It is the only registered state with an upcoming renewal that has no row in the Deadline Calendar — every comparable state has one.

Action: Add a Washington charitable-renewal row (due 2027-05-15) to the calendar and set its Filing Status in Tab 1.

3. Michigan is split across tabs (known gap, but framing disagrees)

• Tab 1 (Charitable): Registered, #64715 — but Next Renewal "Not Set" (needs last-filed date).
• Tab 2 (Entity): "NOT REGISTERED" as a foreign corp — flagged in its notes as a possible gap (charitable reg exists without a MI Certificate of Authority).
• Tab 4 (RA): provider "UNKNOWN - Labyrinth managed?".

This is tracked in Tab 9 ("Michigan Corporate" open question), so it's a monitored gap rather than an oversight — but the three tabs currently tell three different stories about Michigan's standing.

4. Tab 10 (Labyrinth Extraction Checklist) is missing DC's charitable registration

The checklist has an "ENTITY: District of Columbia" row but no plain "District of Columbia" row, even though DC is the home-state charitable registration (BBL Charitable Solicitation endorsement, renewing 2028-07-31). Every other registered state has a charitable-side checklist row.

Action: Add a DC charitable row to the extraction checklist (even if only to mark it N/A — DC may not be Labyrinth-managed).

5. "Columbus, OH" is absent from Tabs 11 and 12

Columbus appears in Tabs 1 and 5 but has no row in Tab 11 (De Minimis Exemptions) or Tab 12 (Deregistration by State). If the fee-savings / deregistration analysis is meant to cover every current registration, the Columbus local registration has no exemption or withdrawal path documented.

Minor / structural (no action needed)

• Tab 11 carries two fully-empty stray columns (exported as col_8, col_9).
• Tab 13 (Fee Savings Analysis) is narrative prose without a real header row — it parses as loose text, not a data table. Fine for humans; just don't treat it as structured data.
• Ohio and Virginia show "Not Registered" alongside a future renewal date — these are prospective if-we-register dates and read as intentional (their notes say so).
• The "Not Set" vs blank differences between "Next Renewal Due (AUTO)" and "Derived Next Due" are representation-only, not conflicts. DC's AUTO date comes from a state document that overrides the derived rule, which is the documented intent of the "Date Basis" column.