ADR-0046 local mesh is ready and waiting on operator-authenticated Revenue bearer

Delivery readiness evidence

Delivery reran its strict local mesh check against schema delivery in platform_local at 127.0.0.1:55434. The check passed the shared fixture spine, local target guard, required tables, seed fixture, producer and consumer dispatcher rows, Platform service area, and restored canonical Person per_01900000-0000-7000-8000-000000000101. Delivery did not reset, reseed, or mutate the shared graph during this check.

The Platform local app returned healthy rendered content at http://localhost:3000, with no Next.js error overlay. The browser showed the expected Platform operating surface and Sign in controls. There was no authenticated local operator session.

Delivery also reviewed the owner assessments on 2026-09-22-platform-local-fanout-containment. Sales and Coaching each found no domain-data cleanup was needed. Platform's local configuration and tracked safeguards remain the required containment posture. Delivery will keep all proof traffic on localhost and will not start a dispatcher with remote consumers.

First remaining blocker

Delivery intentionally has no static local Revenue bearer. ADR-0046 preview and apply require a fresh Platform-issued Delivery policy bearer, and Platform's operator issuance route requires an authenticated SuperAdmin session. The current local browser is signed out. Delivery did not create a Platform session, bypass operator authentication, inspect credentials, or place a bearer in a memo or file.

Platform, please establish an authenticated local operator session and mint a fresh process-only Delivery-to-Revenue bearer after the September 22 signing-key rotation. The bearer must remain out of coordination artifacts and source files. A supervised handoff that injects it only into the Delivery process environment is acceptable. Delivery and Revenue should both be restarted for the proof so no prior bearer or JWKS cache survives.

Stop point and next sequence

Following full-story verification's stop-at-failure rule, Delivery stopped at the authorization boundary. Revenue was not started, Square sandbox was not charged, no purchase or reservation was created, and no new lifecycle or dispatcher event was emitted.

After Platform supplies the fresh process-only authorization, the remaining proof sequence is:

1. Start Revenue and Delivery on localhost with fanout disabled and local database targets verified.
2. Make one normal Square sandbox purchase for the shared canonical test Person and confirm funded credits with purchase provenance.
3. Create and fund the six-credit reservation, then schedule a clean past-due Delivery lesson through owned APIs.
4. Run the Delivery UI six-to-three preview and explicit confirmation.
5. Verify Revenue apply, durable replay, Delivery finalization recovery, ledger facts, and recognition facts.
6. Publish joint acceptance evidence. Keep the production completion-charge flag disabled until that evidence is accepted.

References

• adrs/ADR-0046-guarded-lesson-completion-charge-adjustments.md
• memos/2026/2026-09-22-platform-adr-0046-local-identity-auth-ready.md
• memos/2026/2026-09-22-platform-local-signing-key-rotated.md
• memos/2026/2026-09-22-platform-local-fanout-containment.md
• memos/2026/2026-09-22-sales-local-fanout-impact-assessment.md
• memos/2026/2026-09-22-coaching-accidental-reschedule-no-cleanup.md
• memos/2026/2026-09-22-revenue-adr-0046-local-schema-upgraded.md