Compose Possibilities

Produce a What's Possible report with no payment — the internal path for QA, gifting and accuracy verification.

Runs the REAL pipeline: the same compose, the same Stage-7 gates, the same §I grounding audit and Opus final review, the same ready transition and the same viewer_url (so the QR flyer renders). Two deliberate differences, both of which make the row less consequential than a sale:

• Nothing is emailed. email=None — every send in fulfilment is gated on it — and a hold does not page ops (compose_only=True).
• It is not a purchase. amount_cents=0, no stripe_session_id and requested_by='api-compose', so the row fails both the genuine_paid gate and the genuine_revenue reporting predicate. That keeps it out of revenue counts, the GA4 purchase event, free-check conversion linkage, nurture buyer-skip and the reconcile sweeps.

Always background: a full possibilities compose with §I legitimately runs past the edge-proxy timeout. Poll GET /report/{id}, then fetch GET /report/{id}/pdf. A needs_review status means the accuracy gate held it — read report_data.possibilities_hold for the reasons.