Provasign Documentation
Welcome. This is the home of the long-form documentation for Provasign — certified delivery for AI coding agents — and its open-source foundation: Grove (code knowledge graph), Prism (context delivery), and Fuse (semantic merge).
If you just want to install and try it, the installation guide has the five-minute path. This page exists for the people who need to understand it deeper before they bring it to their team, their CISO, their CFO, or their auditor.
Licensing
Provasign is the product; Grove, Prism, and Fuse are its open-source foundation under a split-license model:
| Component | Role | License |
|---|---|---|
| Provasign | The product — certified delivery | AGPL-3.0 |
| Grove | Embedded code-graph engine (+ standalone CLI) | MIT |
| Prism | Context delivery for AI agents | MIT |
| Fuse | Semantic git merge driver | MIT |
Provasign’s AGPL applies to the Provasign product and its Provasign-specific docs and source tree. Grove, Prism, and Fuse remain MIT licensed — adopt them independently in commercial products without obligation.
Read by Role
| If you are a… | Start here |
|---|---|
| Developer evaluating Provasign for daily use | Overview · Agent Setup |
| Team lead rolling it out to your team | Use Cases → Change Management |
| Engineering executive building the business case | Why Provasign |
| CFO / finance sizing the cost and savings | Why Provasign → What This Costs You |
| CISO / security evaluating the threat model | Use Cases → Security |
| Compliance / audit evaluating evidence quality | Use Cases → Audit |
| Anyone wanting the founder’s pitch | Why Provasign |
Read by Topic
| Topic | Document |
|---|---|
| The case for Provasign — what we built, why we built it, what we deliberately didn’t build | Why Provasign |
| How It Works — capture → gate → certify → sign → replay | How It Works |
| Comparisons — Provasign vs CI/CodeRabbit/Sigstore · Prism vs Copilot semantic search · Grove vs LSP/Sourcegraph · Fuse vs git/AI-merge | Comparisons |
| FAQ — top questions across technical, security, financial, and operational lenses | FAQ |
| Troubleshooting — common issues, how to diagnose, how to fix | Troubleshooting |
| Architecture — embedded Grove engine, single-binary design, data flows, security model | Architecture |
Read by Product
| Component | One-line | Documentation |
|---|---|---|
| Provasign (the product) | Certified delivery for agent-produced code | Overview · Provasign README |
| Grove | Code knowledge graph embedded in Provasign (+ standalone CLI) | Architecture · Grove README |
| Prism | Graph-ranked context for any AI agent | Other Dev Tools · Prism README |
| Fuse | Symbol-aware git merge driver | Other Dev Tools · Fuse README |
Read by Concept
Each of these explains one technical idea in depth.
| Concept | Document |
|---|---|
| Progressive disclosure — how Prism cuts token use ~99% on session re-reads | Other Dev Tools → Prism |
| Symbol-level merge — what Fuse does that line-level merge cannot | Other Dev Tools → Fuse |
| In-loop certification — moving quality gates from CI into the agent loop | How It Works |
| Intent capture — committing the prompt as a YAML alongside the code | Use Cases → Traceability |
Read by Integration
How Provasign hooks into the tools you already use. provasign init auto-detects each and writes its MCP config — see Features → Works with your agent and Agent Setup.
| Tool | Setup |
|---|---|
| Claude Code | Agent Setup |
| GitHub Copilot (VS Code) | Agent Setup |
| Cursor | Agent Setup |
| Codex CLI | Agent Setup |
| Windsurf | Agent Setup |
| Zed | Agent Setup |
Status
The site is organized around Provasign. Every link on this page points to a live page; the open-source tools (Grove, Prism, Fuse) are documented in their repository READMEs, with Grove also covered in Architecture.
| Area | Pages |
|---|---|
| Product | Overview, Why Provasign, How It Works, Architecture, Features |
| Use cases | Security, Audit, Change Management, Traceability |
| Get started | Installation, Agent Setup |
| Reference | Comparisons, FAQ, Troubleshooting, Other Developer Tools |
Contributing to the Docs
These docs live in docs/ in the main repository. PRs welcome.
Quality bar:
- Real numbers over adjectives. “35–92% token savings” beats “huge savings.”
- Honest tradeoffs. Every product has things it doesn’t do well. Say so.
- Specific competitors. Vague “other tools in the space” is worth nothing. Name names.
- One audience per page. A doc trying to talk to a CFO and a developer at the same time talks to neither.