Fresh canonical local test Person ready for Revenue and Delivery

Canonical candidate

Platform created per_01a0cffd-5e80-7aaf-9fba-781b20a21d75, display name Sandbox Completion Proof 20260923, through mintOrMatchPerson, updatePerson and upsertPersonTenancy. It is active, adult and marked is_test_data=true, with active tenancy in org_01900000-0000-7000-8000-000000000001 and market mkt_01900000-0000-7000-8000-000000000902.

Synthetic contact values are phone 18085550193 and email adr0046.clean.20260923@example.test. They are test identifiers, not customer contact destinations. The preflight found neither contact in the local Person table. The post-create read found zero Revenue credit accounts for the new Person. Revenue must establish its account and funding provenance through its own normal workflow.

Scope and verification

All identity writes used Platform's schema in platform_local at 127.0.0.1:55434. The helper scripts/create-local-adr0046-candidate.ts checks both configured DSNs and the connected server, requires outbound worker flags disabled, defaults to preview, and refuses an apply when either contact already exists. A repeat preview returns the same Person without writing. Existing Avery identity, tenancy and financial history were not updated. No Delivery participant, lesson, reservation, Revenue account, purchase or ledger entry was created by Platform.

The normal test-data update writes a local person.updated event. No worker was started and no event replay or outbound transport was requested. Local fanout and background external actions remain disabled. This memo does not authorize blanket backlog replay. Production settings and feature enablement remain unchanged.

Validation: typecheck passed; 353 unit tests, 32 identity integration scenarios and 3 geography integration scenarios passed. Candidate and tenancy service read-back passed. This confirms Platform's identity prerequisite, not the full sandbox proof.

Handoff

Revenue can use the exact Person ID above for the normal clean account and Square sandbox purchase path. Delivery owns creation of its matching participant and a fresh six-credit lesson/reservation after funding is established, followed by six-to-three adjustment, durable replay and finalization recovery evidence. Preserve the canceled/released deterministic lesson and all earlier history. Any required transport activation must be separately bounded to local destinations and proof events, without replaying the historical backlog.