# App review situations are prepared by World recipes

Date: 2026-09-29. Card: `t_974d735b`, task `t_6c4b84f5`.

The owner said, in message `u-8f60e339` to the volter-manager session at
2026-09-29T17:54:19.547Z: “the answer on how to set up the situation should be
trivial: use a world - if it can't use a world to do that, that's a bug with
the world”. The card names a Room with two people and two agents, each signed in.

The implementation uses the existing split: World owns service lifecycle,
environment, readiness and endpoints; the app's cookbook recipe owns its
opening situation through public APIs. It adds no runtime orchestration
language or kernel capability.

The [RH2 review recipe](../../cookbook/rh2-review/README.md) prepares the app,
applies an organization document, and opens human and agent sessions. Its
loopback entry service passes the human browser a cookie already issued by
RH2 and redirects to the real console. All secrets and session material belong
to the disposable local World. Agent session issuance does not launch an agent
harness or establish that a voice interaction works.

The original owner instruction establishes the required outcome. The choice
of a cookbook recipe and entry service is the implementation decision, pending
the card's independent review and observed acceptance.