Dispatch 375
Week of Nov 16 to Nov 22 ↗

Paid access and the house wall

The team spent the day reinforcing two critical boundaries: the billing engine’s ability to survive transaction failures, and the application’s strict segregation of internal and customer resources. The work…

Commits
71
Systems
9
Read
2min
NOVEMBER 19, 2026Thursday403 WORDS · 2 MIN READ · 71 COMMITSops-center132agent-dispatch58unicorn-stable49contact-24181654
Day signal

Drawn from this entry's own record: its date, its length and the work around it. No stock art.

Key points

  1. The team made paid grant completion explicit to prevent perpetual pending states.
  2. Past-due payments keep plans active for seven days before falling back.
  3. The team enforced a hard rule blocking non-house org access to internal tools.
  4. The agent dispatcher now handles leftover files correctly during exit commits.

The team spent the day reinforcing two critical boundaries: the billing engine’s ability to survive transaction failures, and the application’s strict segregation of internal and customer resources. The work was heavy on tests and edge cases, but the result is a system that handles money and access with far more resilience than before.

On the billing side, the paid plan grant system received a thorough overhaul. The team focused on making the completion of a paid grant recoverable rather than fragile. Previously, a swallowed app-workspace plan failure could leave a grant in a perpetual pending state. Now, the completion process is explicit, and errors propagate correctly so the system can retry or fail cleanly. The team also tightened the logic around subscription state changes. Past-due payments now keep the plan active for a maximum of seven days before falling back to free limits, and the system properly handles late cancellations of replaced subscriptions to avoid accidental downgrades. A significant addition was the credit pack workflow; purchases now fund the organization’s pool directly, with refunds reversing the gateway keys accurately. The team ensured that every step, from checkout to ledger entry, is auditable and idempotent.

Simultaneously, the application enforced a hard rule: non-house organizations cannot access internal tools or customer-effective org data. This was implemented across the board. Every model-calling route, from medical services to browser automation, now refuses requests from a non-house effective organization. The image tool, memory manager, and voice synthesis components all check this gate before engaging external APIs. This prevents data leakage and ensures that customer agents only see what they are authorized to see. The team also fixed a regression where linked-org home preferences were incorrectly applied outside of entitlement mode, ensuring buyers land in the correct organization on their first visit.

On the billing side, the paid plan grant system received a thorough overhaul.

Operational stability received attention as well. The agent dispatcher was fixed to handle leftover files correctly during exit commits, preventing stray binaries or large archives from cluttering the repository. The dispatcher now probes the staged-path list accurately and handles deletions without error. Additionally, the team addressed a resource contention issue where multiple high-demand models were idle while other processes held resources, ensuring smoother execution for the dogfood gateway hooks.

Also today: the team cleaned up CI workflows to run preflight agreement tests and documented the rules for LLM key management. The audit logger now serializes decimal values as fixed-precision strings to avoid floating-point drift in financial records.

From the recordWhere the work went309 commits across 9 repositories, and 11 receipts on the board
  1. ops-center132
  2. agent-dispatch58
  3. unicorn-stable49
  4. contact-ops24
  5. legal-ops18
  6. unicorn-brigade16
  7. tax-planning-ops5
  8. customer-ops4
  9. 1 other repository3