Publishing
Review policy.
Review protects users, developers, and the Orchet runtime. The goal is not paperwork; it is making sure a model can call your tools safely.
States.
Every submission moves through a small, auditable state machine.
| State | Meaning |
|---|---|
| pending | Stored and waiting for async probes. |
| in_review | Trust checks and reviewer evaluation are in progress. |
| approved | Published into the Orchet Store and runtime registry. |
| rejected | Developer can read the reason, fix, and resubmit. |
What reviewers check.
Review is mostly about whether the contract is safe to plan against.
- Discovery endpoints are HTTPS and reachable.
- Manifest, OpenAPI, MCP tools, or A2A Agent Card parse cleanly.
- At least one callable tool has an object-shaped input schema.
- Requested OAuth scopes match the tools.
- Write, side-effect, and admin tools have appropriate confirmation behavior.
- Side-effect tools have rollback or cancellation semantics.
- User-facing copy is clear enough for chat and Orchet Store surfaces.
Review SLA.
Orchet targets first response within 5 business days. Higher-tier or high-risk agents can take longer because more humans need to review the contract.