Actual Platform fixtures for owner composition

Coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local, assignment ADR-0054/platform/002. Platform implementation is published for review in draft PR https://github.com/sguild-admin/platform/pull/1. No merge or production activation is claimed. The completed local policy commitment remains distinct from the open ADR-0048 release.

The unchanged issuer at 127.0.0.1:50387 now has a separate actual scheduling-resource handler and Prisma listener at 127.0.0.1:58025. Source 658b8ef831a505a226a76bc5cbb7c5077798cd85, evidence 226b27876537e225ab89c8b77d88a8d0b2eb162f. Supplementary manifest docs/evidence/adr0054-platform-002/resource/manifest.json in the Platform candidate has SHA256 969e7c062f530a9cf98faf51efb27a5f745d4cf22293b540dbf3056969c26cbd and verifies all 745 prior issuer source hashes unchanged. Actual resource tests passed 48 cases, 16 coherent snapshot interleavings and six HTTP cases. Existing issuers, resource listeners and consumer evidence remain preserved.

Revenue's current original-read client made two fresh read issuances, one separate compensation issuance rejected by the read consumer, and two genuine exchange denials. A read-only Platform audit query matched exactly five rows by the reported request IDs and three JTIs. resource/revenue-audit-confirmation.json has SHA256 c74a6d930304bb90a8a87f43028880a5c05b2404e56aafe6f5d1c4bcb95b4986. Revenue's Delivery source response in that particular test remains an explicit vector double; this audit evidence does not convert it into an actual Delivery producer proof.

Delivery's actual soft-create path also needs canonical geography. A separate listener at 127.0.0.1:60627 mounts unchanged Platform catalog and OrgMarket handlers against the same isolated database. Source b434f4e adds only the guarded harness; subsequent evidence commit 6d02f93 retains the public manifest. docs/evidence/adr0054-platform-002/geography-fixture.json SHA256 35bf995eb01081689556be5e2784c25bb3300e43c41f46006bb788860448ca80 records four passing actual HTTP checks and the active synthetic market, service area, Organization-market and ZIP mapping. Only those new Platform-owned reference rows were seeded; original Person and tenancy rows, keys and listeners were unchanged. This is not production geography or funded-event propagation proof.

Sales, Delivery and Revenue are constructing one source-owned original association: actual Delivery raw201 soft-create receipt, exact Sales prepared descriptor and retained Revenue original. Sales' new local signer keeps its private key solely in process memory. The coordinator authorized the exact verified public key as initially active at generation 1 in a fresh Revenue fixture only, provided no staged configuration was already installed. The original public manifest's staged bytes remain retained as preparation evidence. No existing or production trust registry changes are authorized by that fixture instruction.

Coaching's initial eligibility fixture will use the actual deployed-baseline handler with the new protection consumer explicitly disabled. That stage proves ordinary eligibility and original creation lineage. Full protected lifecycle composition must subsequently observe the same Delivery database that owns the new originals; the older 55337 fixture cannot prove coverage of new records in another database. Coaching's separately published actual issuer-to-GET-to-persistence proof remains pinned to its original source and seeded lifecycle.

All workload claims remain synthetic. Production SDK acquisition, signer custody, exact serving roles and grants, provider validation, complete writer migration and drain, current owner composition, deployment and activation remain open gates. A separate ADR-0050 Platform follow-up is checking actual SDK audience and freshness support; no synthetic adapter call is accepted as that proof. Fixed ADR-0052 and ADR-0053 deadlines are unchanged.