Skip to content
/Acme PlatformDemo data
65%
knowledge coverage

17 of 26 AI-changed files have current review evidence

▲ 4 points over the last 4 weeks. 2 files had a review that is now out of date. 2 open questions from developers.

  • Covered (2+ reviewers) 4
  • One reviewer 13
  • Out of date 2
  • Never reviewed 7
This number covers only the 26 files someone has reviewed with Zevqi so far. Your git scan looked at 26 files and found 7 changed by only one person and 7 with AI-assisted commits and no review evidence yet.

Decisions for this week

  • Re-review services/auth/tokens.ts

    Changed 2 days ago, after Aiko T.'s last passing lesson. Nobody has reviewed the new version.

  • Answer Sam O.'s open question on services/billing/webhooks.ts

    "Is the signature comparison constant-time, and what happens to events that arrive twice?"

  • Re-review services/payments/refund.ts

    Changed 3 days ago, after Priya N.'s last passing lesson. Nobody has reviewed the new version.

  • Get .github/workflows/deploy.yml reviewed

    A sensitive path that nobody has reviewed after an AI change.

  • Answer Dev R.'s open question on lib/ledger/reconcile.ts

    "Why does reconcile() retry a partial ledger write instead of rolling the whole batch back?"

  • Get infra/terraform/iam.tf reviewed

    A sensitive path that nobody has reviewed after an AI change.

  • + 11 more in Files, sorted by level.

Open questions from developers

  • Sam O.Needs investigation1d ago
    services/billing/webhooks.ts

    “Is the signature comparison constant-time, and what happens to events that arrive twice?”

  • Dev R.Needs clarification4d ago
    lib/ledger/reconcile.ts

    “Why does reconcile() retry a partial ledger write instead of rolling the whole batch back?”

Knowledge concentration

13
files, one reviewer
8
of those sensitive
Where one person holds the current knowledge
  • Marcus L.4 files
  • Priya N.4 files
  • Sam O.3 files
  • Aiko T.1 file

This is a risk to the team if that person is away, not a judgement of the person.

No review in 30 days: .github/workflowsdb/migrations

AI changes that need a look

Knowledge coverage, last 12 weeks

12 weeks agothis week

Each week uses only what was known at the end of that week. A file that changes after a review drops out until it is reviewed again.

Files with one reviewer, last 12 weeks

Fewer is better: it means knowledge is shared. Out of date now: 2 files.

Pilot checklist

6 of 6
  1. Team created
  2. First developer joined
  3. First AI change captured
  4. First review completed
  5. A second developer joined
  6. A file reviewed by two people
  7. Weekly summary in Slackoptional
    Settings, then Slack.

Tell us what is missing

A pilot only works if it fits how your team works. What would make this useful enough to pay for, or what got in the way?