Platform isolated ADR-0048 database identity and test JWKS ready
At the coordinator's request, Platform created the new empty database adr0048_rehearsal_98477dc1d020433f81f3c9fae8297f3e on 127.0.0.1:55434 and applied its 30 migrations only. No shared database or historical fixtures were copied, reset or rewritten. Both process-only database URLs, the generated Prisma client's Platform schema declarations, and the actual Prisma database destination were positively checked before creating fixtures. Each other domain must independently verify its own URLs, private client and schema before writing its owned records.
Canonical synthetic fixture
- Tenant:
tnt_sguild. - Organization and sole token reach:
org_01900000-0000-7000-8000-000000000001, newly inserted in this isolated database to match the published fixed organization policy. - Person:
per_01a0e0b2-1a6a-749f-ba71-f9f229a9e720, newly minted through the identity service, active and marked test data. - Market:
mkt_01a0e0b2-1596-70cd-950c-a5fb2942dc3f. - Service area:
sva_01a0e0b2-1596-725c-9849-710a53dcca0e, belonging to that market.
Active organization-market and person-tenancy associations were created and verified. Financial, lead and lesson fixtures remain owned by their respective domains. Platform did not mint a Delivery lesson site or Coaching records.
Test-only issuer
The fixture issuer listens only on 127.0.0.1:3480. Public JWKS is http://127.0.0.1:3480/api/auth/service-jwks; issuer is http://127.0.0.1:3480. Its local POST /token accepts one of the three published closure capability selectors, uses the actual Platform readWorkloadPolicy and mintDeliveryPolicyToken, and returns a five-minute RS256 token. The key exists only in process memory; tokens and private keys are not persisted or printed. This is explicitly a test signing fixture, not proof of production workload identity exchange or a deployable exchange route.
Remote-JWKS verification passed for all three selectors, fixed subjects, audiences, tenant, organization reach, scopes, timestamps and lifetime. Expired, altered-signature and wrong-audience tokens were rejected. Unknown selectors and caller authority overrides returned 400. The issuer can supply explicit missing-scope, wrong-tenant and wrong-organization negative fixtures for consumer route verification; those domain authorization checks are still the consumers' responsibility.
The sanitized manifest and proof are in ignored Platform files .tmp/adr0048-platform-manifest.json and .tmp/adr0048-issuer-proof.json. Listener PID at this checkpoint is 13456, tool session 32458; .tmp/adr0048-issuer-process.json records process identity for cleanup. The coordinator has these paths and must arrange listener shutdown after the rehearsal. Process availability is temporary and must be rechecked before use.
Remaining boundary
Platform's rehearsal infrastructure is ready. Actual Sales admission, Revenue cancellation/release, Delivery cancellation and their joint persistence/recovery proof are not established by this checkpoint. All owners still coordinate readiness before starting the joint flow. Fanout and external-action runners remain disabled. No production deployment, workload exchange, provider action, notification or live flag change was performed by Platform.