Release readiness
Public developer launch gates.
Orchet Store is ready for public developers only when a new developer can publish an agent, a reviewer can approve it, and a user can connect and invoke it from chat without private help.
Current operating mode.
The public developer path is: Create account -> create developer key -> scaffold agent -> deploy agent -> submit manifest -> review -> approval -> users connect from chat. Submissions are open for supported protocols, with human review before agents are available in the Orchet Store.
| Mode | Meaning |
|---|---|
| Open developer portal | Any signed-in developer can create a key, submit a supported agent, and track review status. |
| Human-reviewed Store | Agents become available to users only after Orchet review approves the contract and listing. |
| Chat-first usage | Users install or connect agents from chat when a task needs that capability. |
Developer path gates.
A fresh developer account must be able to create a key, scaffold, validate, deploy, submit, and track a submission.
- Developer key creation works from /developer/keys and produces a CLI token shown once.
- SDK/API submission is hosted-first: manifest URL, OpenAPI URL, health URL, and contact email are enough for a simple HTTPS agent.
- MCP and A2A submissions create reviewable contract snapshots or return clear pending-changes feedback.
- Submission status explains pending checks, reviewer feedback, approval, rejection, and resubmission steps.
Review path gates.
Reviewers need enough information to approve safely without editing the database by hand.
- Admin review loads without production schema errors.
- Reviewer can inspect tool schemas, OAuth scopes, risk, support contact, and runtime locator.
- Approval writes a published Orchet Store listing with an Agent Contract snapshot.
- Rejection and request-changes states are visible to the developer.
User path gates.
The user should not need to understand the Store to complete a task. Orchet should surface the right connect card inside chat.
- User asks for a capability in chat.
- Orchet selects the approved agent contract.
- If connection is missing, Orchet renders the inline connect card.
- After OAuth succeeds, Orchet resumes the original request.
- The runtime calls the approved tool and renders the result in the same thread.
Operations gates.
Public launch also requires deploy safety. A missing migration, registry load failure, or connect-card regression should fail before users see it.
- Production schema checks run before deploy.
- Runtime registry health checks confirm approved partner contracts load.
- New submissions can be disabled without breaking existing approved agents.
- Monitoring tracks submission failures, review decisions, registry skips, OAuth completion, and tool invocation success by agent id.
Operational readiness decision.
Keep the developer portal open, but expand promotion only after the Weather Demo golden path keeps passing with developers outside the Orchet team: submit, review, approve, publish, connect from chat, invoke, and render.