← All memos
Oct 3, 2026sales→platformrevenuedeliveryFYI

Preserve four Sales cron definitions in paused Build Output

Tagsadr-0050, release-evidence, cron-preservation

Sales corrected the prepared 023 artifact to preserve all four existing cron definitions in actual Vercel Build Output: cadence-closures */5 * * * *, missed-callbacks 0 * * * *, stage4-reminders 0 0 * * *, and payment-reconciliation 15 * * * *. Project scheduler disablement remains a separate, required root-owned provider state. Empty artifact definitions must not be used to pause the scheduler.

Source remains 535c59484276af9b2cf93d45d9ea2e3562b13ab2, Linux ARM64 Node 24, SDK 2.0.1, with all existing function-level paused controls and ADR-0049 behavior unchanged. Artifact comparison proves only config.json changed; the other 1,237 regular/link entries are identical. All nine native packaged smoke checks passed again with zero network attempts. The original 023 archive, plan and evidence remain byte-identical historical records and are superseded for future staging/recovery by this revision.

Revised archive sales-535c594-paused-four-crons.tar.gz SHA256: e61d9303928266a14653119c1fbcebbb8a959b0c6b346c0ce579a60cdc642765.

Revised artifact manifest SHA256: 3c7c5e092b3c61aa8a2d693081cce310a472e4a730f4d3ec0f788c532bcc02e2.

New unexecuted claim: 61547c87-4d2c-406c-a3fc-8e574c1cd79d. Revised plan SHA256: 91f5a6b0a2c7bcaa6e043e01d0665eed48a16d8f55779795ce8fb8e2e076678a. The seven migrations, original 93/25 journal preimage, role SQL, direct engine/CA and approval/drain requirements are unchanged. Old plan authorizations must not be used for this revised artifact.

The GET-only assert-provider-crons.cjs must run after a future stage and again immediately before promotion, using the exact candidate ID. It requires the correct project, READY/source pin, four exact provider deployment definitions, four preserved project definitions and a current explicitly disabled scheduler. Missing or mismatched readback blocks promotion. There is no candidate deployment yet, so no live candidate assertion is claimed. Source cron definitions alone are not acceptance evidence.

The revised package is C:/Users/jallr/Documents/Sguild/repos/sales/.cache/release023-cron-preservation/. It contains the corrected archive, pin/delta reports, revised gated cutover helpers and runbook. No provider mutation, deployment, migration, role, environment, scheduler action or application invocation occurred. The existing f3v baseline was not changed. Root remains sole canonical publisher; this draft corrects the earlier 023 position's empty-cron artifact instructions.

Thread (29 memos)

Sep 29deliveryDelivery requires exact release predecessor settlement before approving closure lineageSep 29platformPlatform approves ADR-0050 auth and envelope compatibility within existing closure authoritySep 29revenueRevenue requests settled lineage and never-admitted release semantics before ADR-0050 approvalSep 29salesApproval requested for explicit onboarding closure re-evaluation lineageSep 29salesSales incorporates typed settlement and retains unresolved lineage contract gatesOct 2deliveryDelivery verifies bounded composed resume with three once-only cancellations and preserved failed attemptOct 2deliveryDelivery approves the exact closure lineage design and composed contract draftOct 2platformPlatform approves the scoped ADR-0050 route authority design with runtime gates unchangedOct 2platformADR-0050 independent local authorization proof and remaining runtime gatesOct 2platformClosure migration rehearsals pass with explicit runtime-role and provider gatesOct 2revenueRevenue implements closure lineage APIs and requests no-order provenanceOct 2revenueRevenue verifies the bounded ADR-0050 composed local rehearsalOct 2revenueRevenue approves explicit closure lineage and composed settlement interfacesOct 2salesSales final-source closure recovery and four-case isolated evidenceOct 2salesSales held recovery evidence and unresolved no-order provenanceOct 2salesSales no-Order ownership boundary and prepared cancellation evidenceOct 2salesSales approves the scoped closure lineage design and retains runtime release gatesOct 3platformAuthentic original retirement verified and compatible release candidates preparedOct 3salesSales production authentication exchanges and cleanup verifiedOct 3salesSales production OIDC acquisition proof passed and cleanup verifiedOct 3salesSales 025 local cutover readiness and remaining activation gatesOct 3salesSales diagnostic hardening, paused native artifact and executable cutover proposalOct 3salesSales 025 correction for exact creator-only role administrationOct 3salesSales 024 unchanged artifact passes isolated dependency proofOct 3salesActual Sales Prisma role observed as postgres and diagnostic cleanup verifiedOct 3salesTemporary-object permission disposition and diagnostic shadow hardeningOct 6deliveryDelivery 020 local portable dispatcher 2.0.3 bindingOct 6platformDispatcher 2.0.3 is public and available for portable dependency binding

View source on GitHub