# Joined application acceptance

Read the [guest example](../../examples/platform-acceptance/README.md) and its [six pinned modules](../../examples/platform-acceptance/source-manifest.json).

The application joins project imports, selected memory, media, typed tools, durable owner decisions and a service queue. Four synthetic intake reports produce 57, 46, 35 and 44 units; the aggregate is four requests, quantity14 and total182.

The historical Source54 five-result composite remains two closed processes with its original reader failure retained. A separate installed57 FIRST run completed all five business jobs in one uninterrupted process:8callbacks,15events and the exact original summary schema/requests4/quantity14/total182. The separately registered Source cases verify quotas, four clients in one process, cancellation, one genuine crash/reopen and permanent uncertainty fencing. Independent final reviews of these outcomes and the finite release checklist are accepted6/6.

This guest project requires its issued SDK host, original selection and registered tools. Public pure native55/56 profiles reject its effects. A guest `yes`, copied view, result JSON or hash grants no authority. Never retry an uncertain effect or replace its journal to get a result.

Native tools, Wasm, quotas/concurrency, crash recovery, security and final delivery have separate acceptance criteria. This example does not close the platform roadmap or establish real model cost.