Belongs to
What Nerviq is
AI agent governance.
AI development control plane.
Configuration intelligence for coding-agent workflows.
Category Kit
Nerviq is the control plane for AI-enabled development.
Nerviq is not just a collection of checks. It governs how AI coding agents operate across a repo, aligns multiple tool surfaces, and keeps that setup inspectable over time. This page defines the category language behind that position.
AI agent governanceAI development control planeRepo-native
Category definition
The shortest precise way to describe Nerviq is: a repo-native governance layer for AI coding agents and AI-enabled development workflows.
Repo-native
Scope
Nerviq starts from the repo and the active agent surfaces around it, not from abstract policy alone.
Cross-platform
Mode
It aligns multiple AI coding tools instead of treating each one in isolation.
Inspectable
Output
Scores, snapshots, contracts, and proof surfaces make the operating model visible.
Does not replace
What Nerviq is not
Full SAST or deep application security review.
A prompt library or starter-kit collection.
A single-vendor IDE helper.
A generic policy engine with no repo context.
Comparison matrix
Nerviq overlaps with a few neighboring categories, but the center of gravity is different. This matrix is the shortest honest way to explain where the product fits.
| Category | What that category does well | Where Nerviq differs |
|---|---|---|
| SAST / code scanners | Find code-level vulnerabilities and risky patterns. | Nerviq focuses on agent configuration, governance, drift, and the operating model around AI-enabled development. |
| Policy-as-code | Define enforcement rules and compliance logic. | Nerviq is repo-native and AI-workflow-aware, with cross-platform agent surfaces, Harmony, and proof flows. |
| IDE plugins | Improve one editor experience. | Nerviq governs the repo across tools instead of attaching itself to one vendor surface only. |
| Prompt libraries / starter kits | Speed up first setup. | Nerviq keeps the setup measurable, aligned, and auditable after day one. |
| General DevEx tooling | Standardize engineering workflows broadly. | Nerviq is specifically about AI-enabled development posture and multi-agent drift. |
Operating model
Nerviq becomes infrastructure when it sits inside the workflow, not just beside it.
Start
1. Detect and baseline
Use audit, harmony-audit, and snapshots to establish the live starting point.
Reduce drift
2. Align and fix
Use Harmony, plan/apply, and reviewable fixes to close contradictions safely.
Make it repeatable
3. Govern and gate
Add permissions, hooks, deny rules, org/team/repo policies, and CI drift gates so the setup stays governed.
Turn posture into standard
4. Prove and scale
Preserve score semantics, benchmark evidence, and integration contracts so fleets and external systems can rely on the same operating model.
Adoption playbook
The route to standardization is gradual. Nerviq should create value at one repo, then one team, then one org, before asking the market to treat it like infrastructure.
| Stage | Primary user | Nerviq job |
|---|---|---|
| Single repo | Developer or team lead | Find drift, score the setup, fix the basics, and create proof. |
| Team standard | DevEx / engineering lead | Define operating profiles, policy packs, and CI drift gates. |
| Org control plane | Platform / security / governance | Apply policy inheritance, fleet semantics, and integration contracts. |
| Market standard | External ecosystem | Publish proof, gate first-tier integrations, and keep category language consistent. |