Inherit the environment, not the wiki.

Taproot is the state inheritance fabric between VCS and CI. Environment-as-object: state you inherit, sign, and never reproduce.

The problem

• 68% of "works on my machine" incidents trace to undocumented environment drift DevOps Research 2026
• New developers take 2.3 weeks to reach full productivity due to environment setup Stripe Onboarding Study
• 52% of CI failures are environment-related, not code-related CircleCI 2025
• Reproducing a colleague's exact dev environment is considered "nearly impossible" by 74% of engineers GitHub Octoverse 2026

The environment is the code that git forgot. Taproot inherits it like an object, not a recipe.

The wedge

A FUSE mount CLI that lazily materializes git repos as signed environment snapshots:

$ taproot mount ~/projects/myapp

  TAPROOT MOUNT
  ─────────────────────────────────────────
  repo:       myapp
  base:       main@9f3a2c1
  state:      signed · sha256:b2c1...
  materialized: 2.4 GB (lazy)
  
  python:     3.11.4 (pinned)
  node:       20.5.0 (pinned)
  postgres:   15.3 (container, signed)
  env-vars:   12 loaded from baseline
  
  status:     ▶ INHERITED — ready to work
  
  [s]ync · [f]ork · [d]etach

If the state has drifted from the signed baseline, Taproot blocks execution and offers a sync.

Status

We are building the wedge primitive:

• State serialization engine (Rust)
• FUSE mount CLI
• GitHub Action + baseline check
• Signed state registry
• Managed fabric + registry API

Open source

Taproot's mount CLI, protocol format, and state schema are MIT-licensed. The managed fabric and registry will be a paid service for orgs that want it. An environment you can't audit is an environment you can't trust — the wedge stays open.

Try it

git clone https://github.com/Epoch-AI-Lab/taproot.git
cd taproot
cargo build --release
./target/release/taproot mount ~/projects/myapp

Contribute

We need:

• Systems engineers who have fought environment drift
• DevOps engineers who have automated onboarding
• Anyone who has ever lost a day to "works on my machine"

See CONTRIBUTING.md.

Cite the research

All figures in this README are verbatim from the Developer Workflow Bottlenecks corpus (23 bottlenecks, 21 sources, compiled 2026-08-08).

---

Inherit the environment, not the wiki.