Product evidence

Trace AI engineering from session cost to durable delivery.

Clavinci is a commercial, company-operated engineering intelligence product. It joins structured AI-tool activity to code, delivery, review, and stability outcomes without collecting the work itself.

Evidence checked: 2026-07-16

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.

02 / inputs

The inputs Clavinci joins

Each source contributes structured evidence. Content that is not required for measurement stays outside the event contracts.

01

AI sessions

Session boundaries, tools, models, token classes, cache reads and creates, timestamps, project context, tool events, and compaction metadata.

02

Git and code change

Commit identity, repository and branch context, file paths, diff statistics, line deltas, parent relationships, and deployment markers.

03

Delivery and planning

Jira issue keys, types, status transitions, priority, assignee, story points, sprint membership, epics, and lifecycle timestamps.

04

Review and operations

Pull request events, review state, CI timing and outcomes, deployments, hotfixes, incidents, on-call pages, and restoration timing.

03 / joins

The joins that make the evidence useful

  1. 01

    Session to commit

    Time proximity, file overlap, explicit session trailers, and Jira matches produce proportional links. Attribution versions can be replayed, disputed by engineers, and resolved by an admin.

  2. 02

    Commit to work

    Issue keys in commits, branches, and pull requests connect code changes to Jira issues, sprints, epics, story points, spillover, aging work, and time in status.

  3. 03

    Commit to delivery

    Commit SHA and pull request identity connect attributed work to review timing, CI, deployments, DORA, rollback, rework, and 30-day survival.

  4. 04

    Delivery to stability

    Incident adapters connect changes to hotfixes, change failure, incident rate, mean time between incidents, on-call load, reopen rate, and restoration time.

04 / outcomes

Questions the joined model can answer

The product measures cost, delivery, review, stability, quality, and adoption from the same attributed cohorts.

  1. 01

    Actual and API-equivalent cost per issue, story point, CI run, and merged line that survives 30 days

  2. 02

    DORA, AI lead-time delta, change failure, rollback, rework, and durable code survival

  3. 03

    Sprint velocity, spillover, cycle count, time in status, aging work, stale issues, and epic economics

  4. 04

    Pull request size, first review, merge after approval, iterations, self-merge, reviewer turnaround, and review load

  5. 05

    Hotfixes, incidents, mean time between incidents, on-call page rate, reopen rate, and restoration time

  6. 06

    Re-rolls, suggestion acceptance, tool-task fit, prompt complexity, churn, compaction, adoption, and tool mix

05 / boundary

The measurement boundary is part of the product

Structured evidence captured

  • Token counts, model identifiers, session ids, timestamps, cache classes, and tool events
  • Commit SHAs, branches, file paths, line deltas, pull request events, CI timing, and deployment markers
  • Jira keys, types, status, priority, story points, sprint and epic membership, and transitions
  • Incident identifiers, severity, timestamps, on-call events, and restoration timing

Content structurally excluded

  • Prompts and responses
  • Source code and file contents
  • Pull request descriptions and review comment text
  • Jira descriptions, comments, attachments, and free-text custom fields
  • CI output, logs, environment variables, secrets, and credentials

06 / integrations

Current collection and outcome surfaces

AI collector implementations

  • Claude Code
  • Codex
  • Cursor
  • Gemini
  • Kiro CLI
  • Kiro IDE
  • OpenCode
  • OpenClaw
  • Every Code

Delivery and operational sources

  • git
  • GitHub Actions
  • GitLab CI
  • Jira
  • PagerDuty
  • Opsgenie
  • Incident.io
  • structured file adapters

07 / implementation

What is implemented now

Checked-in implementation

The checked-in product contains nine AI collector implementations, git collection, replayable attribution, pricing and cost calculation, Jira and incident adapters, DORA, sprint, PR, stability and AI-quality metric packages, local and cloud APIs, governed dashboard surfaces, notifications, and collection-health aggregation.

08 / limitations

Current limitations and non-goals

  1. 01

    Clavinci does not offer customer-managed, self-hosted, or on-premise deployment.

  2. 02

    Jira is the current work-tracker integration. Linear, Asana, Shortcut, and GitHub Issues are not current product integrations.

  3. 03

    Clavinci does not provide developer surveys, industry benchmark programs, generalized BI, portfolio finance workflows, AI code review, or pull request automation.

  4. 04

    The product measures structured metadata. Its content boundary intentionally rules out content-aware coding-agent context and code analysis.

  5. 05

    Public prices, plan boundaries, and service commitments are not final and must not be inferred from the implementation status.

Evidence checked: 2026-07-16

Product evidence

  1. Checked-in implementation
  2. Architecture and data-flow reference
  3. Product requirements and non-goals
Clavinci is built to make the full engineering outcome path inspectable while keeping the work itself outside the measurement system.