platform-usagelisted

### 1. Call chain Two chains reach the transport layer — **read** and **process** — the BC facade's Außentür (G2) exposes no aggregate writes: ``` new MyApp($kernel) ← final Domain facade, holds the Koffer (DomainKernelInterface), one per request/run ↓ $app->counter() ← BC facade (the Außentür) ↓ ->counter() ← Aggregate READ facade `{Agg}Read` (hermetic, reached via $bc->{agg}()) ↓ ->getCounterById($dto) ← DomainResponseInterface ``` ``` new MyApp($kernel) ← final Domain facade, holds the Koffer (DomainKernelInterface), one per request/run ↓ $app->counter() ← BC facade (the Außentür) ↓ ->process() ← Process facade `{BC}Process` (hermetic, reached via $bc->process()) ↓ ->createCounter($dto) ← DomainResponseInterface ``` Three method hops on the `MyApp` instance: BC accessor → `{agg}()`/`process()` accessor → use-case method. **There is no general third chain for aggregate writes from the transport layer.** The aggregate write facade `{Agg}/{Agg}.php` is reachable only family-internally, via the Kernel-Naht (`$this->handle({Agg}::class)`), from classes that extend the Domain Context (Process node bodies, Services — the Context-Familie). A PSR-15 controller, CLI command, or queue consumer is **outside** that family and has no `handle()` of its own — it can only reach `$app->{bc}()->{agg}()` (read) and `$app->{bc}()->process()->{process}()` (write). To let