The questions security reviews ask.

Local CLI execution: nothing. Embeddings are computed on-device, search runs locally, and the whole system operates fully offline. Hammer & Burst: Repository indexes (outlines, symbol lists) are sent to the hosted Ganvil index service to run embeddings and queries in the cloud, and active VM compute logs route through our remote MCP gateway. Compliance & Governance: Same as Hammer & Burst, plus an append-only audit trail of all agent activity and proposal signature history stored in the cloud. Zero Trust: Same as Compliance, but all remote tool access is strictly confined through path-cone filters and verified against time-bound token claims.

The bridge round-trips byte-perfectly in both directions — gan import then gan export reproduces the original repository exactly, and that property is tested, not aspirational.

Sidecar tools proved that agents with a code graph beat agents without one. But a sidecar is a second source of truth: stale between runs, blind to history, gone when the folder moves. Ganvil computes the graph inside the VCS — updated sub-second per file on every change, keyed by OID so it is queryable at any commit, not just the last time an indexer happened to run.