Publishing & review
Submission → automated certification → human review → published. Transparent at every step.
Lifecycle
| status | meaning | your move |
|---|---|---|
submitted | certification FAILED — the version is parked with its report | fix and resubmit the same version |
in_review | certification passed; queued for operator review | wait — check the console for the verdict |
published | live in the Marketplace; the app card updates to this version | announce it 🎉 |
rejected | review declined — notes attached | address the notes, bump, resubmit |
What reviewers look at
- Scope honesty — permissions match what the package actually does.
- Listing quality — the description says what installs, what data moves where, and which conflict policy a bi-directional sync uses.
- Template quality — workflows read sensibly in a tenant's dry-run preview; agent prompts are grounded.
- Certification warnings — unexplained warnings slow review.
How you hear back
The pipeline is push, not poll, on both sides:
- On submission — the Ivorycom review team is emailed immediately with your app, certification result, and the security-packet summary, with a deep link into the review queue.
- On decision — the email address you submitted with receives the verdict: a publish notice when the version goes live, or a changes-requested email carrying the reviewer's notes verbatim.
- Always in the console — My apps shows each version's live status (
in_review→published/rejected+ notes) the moment the reviewer acts.
Slug ownership & squatting
The first publisher to submit a slug owns it; submissions to another publisher's slug return 409 SLUG_TAKEN. Pick a slug you'll keep — it's your app's permanent identity.
Pricing & revenue share
pricing.model: paid requires monthlyPriceUsd. The platform share is recorded per app as platformShareBps (default 3000 — the 70/30 split in your favor). Payouts launch Q4; pricing metadata captured now carries over unchanged.