Events that this project's journeys wait on but which have never arrived from the app. Each one is a step where users currently get stuck forever. Start here.

Every active journey in this project and the events each one depends on.

What one journey does, step by step in plain English, plus the state of every event it needs. Use this to understand what a missing event actually blocks before deciding where to track it.

The generated constants file for this project's events, in the language you ask for. Write it into the repo and call the constants instead of string literals — event matching is exact, so a typo is a journey that silently never advances. Regenerating produces an identical file.

Call this once you have actually written the tracking calls. It tells the dashboard the events exist in the app but haven't arrived yet, which distinguishes 'nobody has done this' from 'done, waiting on a release'. Do not call it for events you only planned to add.

Create a DRAFT journey from a plan. Read the payghaam://journey-plan-schema resource first — it has the format and a worked example. The draft sends nothing; a person reviews and activates it in the dashboard, and it is labelled there as machine-written. Requires an author key (ek_mcpa_). If the plan is invalid you get the specific problems back and can fix and retry.

Which Payghaam project this key belongs to and whether anything needs instrumenting.