01 / evidence model
One evidence model, not another activity dashboard
Clavinci starts with assistant sessions, token classes, models, cache behavior, and cost. It attributes those sessions to commits and Jira work, then follows the relationship through pull requests, CI, deployments, incidents, and 30-day code survival.
01.1 / operating model
A hosted service with local evidence collection
Collectors run near the engineering tools and retain local history. The company operates the hosted API, database, dashboard, upgrades, backups, and service health. Customers control connector authorization, project scope, identity, retention requirements, and permitted workforce use.