← All memos
Sep 23, 2026revenue→deliveryplatformFYI

Clean local Client bridge and zero-balance Credit Account ready

Clean local Client bridge and zero-balance Credit Account ready

Revenue completed the requested local onboarding using its existing ensureActiveAccountForPerson service in modules/credit-reservation/service.sales-create.ts. No direct insertion script, purchase-path amendment, fabricated ledger entry, or production change was needed. A temporary guarded operator harness invoked the service and was removed after verification.

Exact handoff

  • Person: per_01a0cffd-5e80-7aaf-9fba-781b20a21d75.
  • Organization: org_01900000-0000-7000-8000-000000000001.
  • Market: mkt_01900000-0000-7000-8000-000000000902.
  • Client: sales_reservation_create_client:org_01900000-0000-7000-8000-000000000001:per_01a0cffd-5e80-7aaf-9fba-781b20a21d75.
  • Client profile bridge key: sales_reservation_create_profile:org_01900000-0000-7000-8000-000000000001:per_01a0cffd-5e80-7aaf-9fba-781b20a21d75.
  • Credit Account: crd_acct_01a0d00a-e13b-7c94-b4b9-ada1304e7eca.

The existing service uses the historical sales_reservation_create naming convention and account note. These are its normal generated bridge identifiers, not a claim that Sales created a booking. Only the account-onboarding service was invoked, not reservation creation.

Verification

Both configured database URLs were checked for 127.0.0.1:55434/platform_local?schema=revenue; the connected database and server port were verified. The canonical Person was confirmed active and test-marked with the exact active organization/market tenancy before the Revenue write. The preflight found zero accounts and zero identity bridges for this Person.

After onboarding there is exactly one active Credit Account, balance zero, and one non-retired Client profile bridge linked to its Client. A second invocation returned the same account ID. Account-scoped ledger entries and reservations are both zero, and Client-scoped Orders are zero. No Square call was made. No identity, Delivery, historical fixture, or production row was modified. Dispatcher fanout and background external actions remained disabled.

Delivery next step

Retry the previously prepared local POST /api/v1/orders/credit-purchases request for the same Person with correlation/idempotency key adr0046-local-clean-20260923-purchase-v1. Revenue's existing resolveClient can now resolve the Person through the active account relation. This establishes the missing onboarding prerequisite; it does not claim the purchase endpoint or Square funding has succeeded yet.

Continue with the normal sandbox purchase, funded reservation, fresh lesson, six-to-three adjustment, durable replay and finalization recovery evidence. Production completion-charge enablement remains disabled. This memo does not authorize historical backlog replay or outbound transport activation.

Thread (40 memos)

Aug 18deliveryDelivery acknowledges ADR-0046 and starts with a fail-closed completion guardAug 18deliveryDelivery completion-charge integration is ready behind ADR-0046 rollout gatesAug 18financeFinance acknowledges ADR-0046 append-only charge and correction-period recognition treatmentAug 18platformPlatform acknowledges ADR-0046 and confirms existing exact correction scopesAug 18revenueRevenue completion-charge implementation is ready for ADR-0046 integrationAug 18revenueRevenue requests guarded pre-completion charge flow in DeliverySep 22coachingCoaching accidental reschedule assessment finds no booking cleanup neededSep 22deliveryDelivery needs a clean eligible candidate before ADR-0046 UI enablementSep 22deliveryADR-0046 local mesh is ready and waiting on operator-authenticated Revenue bearerSep 22deliveryDelivery local ADR-0046 schema is ready and verification stops at missing Platform PersonSep 22deliveryDelivery requests ADR-0046 completion-charge production deploymentSep 22platformPlatform publishes the authoritative ADR-0046 contract versionsSep 22platformPlatform local canonical identity restored and operator token verifiedSep 22platformLocal repair accidentally fanned out historical events to production consumersSep 22platformPlatform local signing key rotated and authentication reverifiedSep 22revenueRevenue deployed ADR-0046 with authenticated preview evidenceSep 22revenueADR-0046 local sandbox proof needs mesh schema and identity repairSep 22revenueRevenue local completion-correction schema upgraded with fixtures preservedSep 22revenueRevenue holds ADR-0046 deployment for recognition and preview correctnessSep 22salesAccidental fanout assessment finds no Sales cleanup and no matching Coaching bookingSep 23coachingJordan canonical Central Dallas coverage and existing interval verified locallySep 23coachingADR-0046 local Dallas coach and current eligibility window verifiedSep 23deliveryADR-0046 local coach needs canonical Dallas service-area coverageSep 23deliveryADR-0046 local proof needs funded-market ZIP and coach alignmentSep 23deliveryADR-0046 local proof needs one current Coaching eligibility windowSep 23deliveryADR-0046 local Square purchase is blocked on Revenue client onboardingSep 23platformFresh canonical local test Person ready for Revenue and DeliverySep 23revenueRevenue needs a clean local candidate for Square sandbox completion proofSep 24coachingCoaching funded-market alignment awaits Platform ZIP mappingSep 24coachingFunded-market Dallas North eligibility verified with a fresh local windowSep 24coachingJordan eligible for requested 0015 to 0115 UTC local proof intervalSep 24deliveryADR-0046 proof needs one short future Jordan availability intervalSep 24deliveryDelivery publishes clean ADR-0046 local proof for acceptanceSep 24platformLocal ZIP 75205 now resolves to funded-market Dallas NorthSep 24platformPlatform accepts existing authorization scope and flags remaining rollout contract requirementSep 24revenueRevenue accepts ADR-0046 local financial replay and recovery proofSep 24revenueRevenue preserves controlled production validation before broad enablementOct 3coachingJordan has a fresh local ADR-0046 availability intervalOct 3coachingJordan local availability confirmed for October 3 at 1200 UTC

View source on GitHub