Marketplace listings, IDE plugins, and similar high-visibility surfaces should amplify a trustworthy product. Nerviq uses a first-tier gate so distribution follows contract quality, public proof, and operational reliability instead of racing ahead of them.
A first-tier surface is any public integration where Nerviq will be judged as a category product, not just as a repo utility. Those surfaces need a higher release bar than a private experiment.
| Dimension | Why it exists |
|---|---|
| Contract stability | Machine-readable contracts, explicit score semantics, and no dependency on scraping unstable CLI text. |
| Public proof density | Inspectable public evidence exists across multiple repo shapes, not just marketing copy. |
| Operational reliability | Canonical test/build/deploy paths are green and reproducible for outside users. |
| Ownership and support | One repo owns the surface, release/update flow is defined, and issues can be triaged cleanly. |
| Category fit | The integration reinforces Nerviq as agent governance / AI development control plane instead of blurring it into another category. |
The gate is intentionally conservative. A surface can be interesting and still remain gated if it would arrive before the product story is strong enough.
| Surface | Status | Reading of that status |
|---|---|---|
| GitHub Action marketplace | Gated | The repo action can exist before the marketplace listing. Broader distribution waits for the full first-tier bar. |
| JetBrains plugin | Gated | IDE distribution waits until the plugin contract, install path, and support posture strengthen the core category. |
| Shared/team dashboard | Gated | Monetization-facing surfaces stay behind trustworthy fleet semantics and clear control-plane ownership. |
| Community seeding | Later | Community distribution follows public proof and category clarity instead of compensating for their absence. |
The release bar is not abstract. It creates an explicit checklist for when a surface like GitHub Marketplace or a JetBrains plugin should move from backlog to launch.
Contracts must already exist or be easy to state precisely.
Public proof needs to be inspectable outside the repo owner's claims.
Docs, release flow, and ownership need to be synchronized.
The surface must make the control-plane story clearer, not noisier.
A working prototype alone is not enough.
Interest from a marketplace does not override contract or proof gaps.
A surface is not ready just because the code can technically be shipped.
Distribution does not get to substitute for product clarity.