1 /

Every era needed a new tool.
The AI era is no different.

SCCS
1972
SCCS
Single-file deltas
CVS
1986
CVS
Multi-file commits
SVN
2000
Subversion
Atomic commits
Git
2005
Git
Distributed branching
h5i
now
h5i
next-gen ai-aware git

The code survives.
The reasoning doesn't.

"Why did Claude touch src/session.rs?
That wasn't in the ticket."

— Every engineering team, every week

Git records

  • Which lines changed
  • Author and timestamp

Git misses

  • Why those files were touched
  • What the AI read before editing
  • Where the AI was uncertain

A Git sidecar that captures
everything Git can't

Stores structured metadata in .git/.h5i/ — no new infrastructure, no lock-in, works with any git remote.

h5i commit --prompt …

AI provenance

Prompt, model, agent ID, and test results linked to every commit.

h5i notes

Session analysis

Files read vs. edited, uncertainty heatmap, blind-edit detection.

h5i context

Reasoning workspace

Version-controlled OBSERVE / THINK / ACT trace that survives session resets.

h5i compliance

Compliance & policy

Enforce AI commit rules and generate audit reports across date ranges.

Every Claude session becomes
a permanent audit trail

h5i notes show

Exploration footprint

Every file the AI read vs. edited, including implicit dependencies.

h5i notes coverage

Blind-edit detection

Files modified without reading first — the leading indicator of latent bugs.

h5i notes review

Review surface

Composite risk score — tells you exactly which PRs need human eyes.

~/my-project
$ h5i notes show

── Exploration Footprint ──────────────────
  Session a3f8c12 · 89 msgs · 34 tool calls

  📖 src/auth.rs           ×4  (Read, Grep)
  📖 src/session.rs        ×3  (Read)
  ✏  src/billing/token.rs  ×2  ⚠ BLIND EDIT

$ h5i notes review

  #1  a3f8c12  score 0.81  ████████░░
      refactor billing token refresh
      ⚠ blind edit · high uncertainty

Reasoning that survives
session resets

Version-controlled OBSERVE / THINK / ACT trace stored in refs/h5i/context. Snapshots on every commit. Branches like git.

h5i context trace

Trace entries

Log each reasoning step as OBSERVE, THINK, or ACT — persists across session resets.

h5i context search "…"

Targeted retrieval

BM25 over traces + git co-change. Replaces exploratory Read chains with ranked candidates.

init · feat/auth
OBSERVE auth.rs ×4
THINK use Arc injection
branch: experiment/mutex
THINK try Mutex
✗ abandoned
ACT inject Arc into middleware
commit · "analyzed auth"
OBSERVE tests/ ×2
commit · "updated tests"

6× fewer file reads.
Same answer.

Agents burn tokens every session re-deriving what they already figured out last time. h5i claims records each conclusion with its evidence pinned as a Merkle hash over the files it depends on — stays live until any evidence blob changes, then auto-invalidates.

h5i claims add "…" --path src/api.rs

Content-addressed facts

Evidence = sha256 over (path, blob_oid) pairs at HEAD. Git tells you when they're stale — no TTL, no guessing.

h5i context prompt

Preamble injection

Live claims render as ## Known facts at session start. Agent treats them as pre-verified — skips re-reading.

A/B evaluation
── A/B · 10 trials per arm ────────────────
  metric            No claims   With claims      Δ
  ────────────────  ─────────   ───────────  ─────
  Read tool calls   5.6 ± 1.0     1.0 ± 0    −82%
  Cache-read tok.    510,284       117,433    −77%
  Assistant turns  17.1 ± 1.8   4.8 ± 1.2    −72%
  Wall time           52s ± 9      18s ± 5    −65%
  Task fidelity         9/10       10/10  ✓

  ✔  All 10 trials read exactly 1 file —
     the one the claims point at.

Enforce rules.
Generate audit reports.

h5i policy init

Policy rules

Define TOML rules — require audit flag, minimum prompt length, model allowlist, test coverage threshold.

h5i policy check

Pre-commit enforcement

Checks staged files against policy before every commit. Blocks on errors, warns on violations.

h5i compliance --since …

Audit report

AI contribution ratio, audit coverage, policy violations, and top-risk files over any date range.

~/my-project
$ h5i policy check

   model declared (claude-sonnet-4-6)
   audit flag present
   test metrics missing          [error]
   prompt length < 20 chars      [warn]

  1 error · 1 warning — commit blocked

$ h5i compliance --since 2026-04-01

── Compliance Report ──────────────────────
  AI-generated:    74% of commits (30 days)
  Audit coverage:  91%
  Policy errors:   3  warnings: 8
  Top risk file:   src/billing/token.rs

Everything you need to
audit AI-generated code

h5i commit --audit

Integrity audit

12 deterministic rules — credential leaks, CI tampering, scope creep.

h5i blame <file>

AI-aware blame

Per-line authorship with agent name, model, and test badge.

h5i rewind <sha>

Safe rewind

Non-destructive restore to any past commit. WIP auto-backed up.

h5i context scan

Injection detection

Scans the reasoning trace for prompt-injection patterns.

h5i memory snapshot

Memory tracking

Snapshots Claude's memory at every commit, diffs across versions.

h5i serve

Web dashboard

Timeline, Integrity, Intent Graph, Memory, Sessions at localhost:7150.

h5i vs. plain Git

Capability
Plain Git
h5i
Who changed what
AI provenance — prompt, model, agent
Which files the AI read, not just edited
Blind-edit and uncertainty detection
Reasoning persists across sessions
Targeted retrieval — no exploratory reads
Works with existing git remotes