ARIVARAN GIT

Clone once. Give every agent an isolated worktree.

Arivaran Git makes the mechanism explicit: clone → worktree add → lazy or on-touch materialization → isolated write. Unchanged repository content stays storage-efficient; setup time, merge conflicts, and platform behavior remain workload- and mode-dependent.

Clone. Add. Touch. Write—without duplicating unchanged work.

UnavailableRepository and worktree isolation

Open the canonical product panel Products

Arivaran Git

Unavailable

The diagram shows the mechanism, its current result, and the limit that remains in force.

Step 1 of 3Reuse repository content without repeating it
Measured Linux worktrees keep unchanged hardlinked content shared. Windows user-mode coverage is Preview and its driver-backed acceleration remains acceptance pending. APFS clone mode shares disk blocks across independent inodes.
Step 2 of 3Measured storage efficiency for parallel work
The accepted benchmark supports the storage claim. Setup time remains filesystem-dependent, and the single-page-cache benefit applies to shared-inode modes rather than macOS clone mode.
Step 3 of 3Evidence boundary
macOS clone mode does not share one inode or one page-cache copy. Public Git activation remains unavailable until its separate installer, rollback, and publication gates pass.

Mechanism

Measured Linux worktrees keep unchanged hardlinked content shared. Windows user-mode coverage is Preview and its driver-backed acceleration remains acceptance pending. APFS clone mode shares disk blocks across independent inodes.

Platform state

Linux is GA. Windows user-mode coverage is Preview and driver-backed acceleration is acceptance pending. macOS APFS clone mode is available with acceptance pending; hardlink+MOWI remains unavailable pending EndpointSecurity entitlement and native acceptance.

Evidence boundary

macOS clone mode does not share one inode or one page-cache copy. Public Git activation remains unavailable until its separate installer, rollback, and publication gates pass.

Before you start

Windows driver acceptance still requires catalog binding, kernel-policy verification, installer consumption, install/load, and Driver Verifier evidence. macOS clone acceptance still requires the native clone, isolation, metadata, volume/fallback, installer, and doctor/status matrix.

Evidence reviewed 2026-08-26

Git products

Overview
Arivaran Git — Unavailable
One repository content base can support isolated workspaces through platform-specific modes: shared-inode MOWI where accepted, or independent-inode copy-on-write on APFS.
clone
worktree add
lazy / on-touch
isolated write
1. Mechanism
  Reuse repository content without repeating it
  Measured Linux worktrees keep unchanged hardlinked content shared. Windows user-mode coverage is Preview and its driver-backed acceleration remains acceptance pending. APFS clone mode shares disk blocks across independent inodes.
2. Current outcome
  Measured storage efficiency for parallel work
  The accepted benchmark supports the storage claim. Setup time remains filesystem-dependent, and the single-page-cache benefit applies to shared-inode modes rather than macOS clone mode.
3. Evidence boundary
  Evidence boundary
  macOS clone mode does not share one inode or one page-cache copy. Public Git activation remains unavailable until its separate installer, rollback, and publication gates pass.
Platform state
Linux is GA. Windows user-mode coverage is Preview and driver-backed acceleration is acceptance pending. macOS APFS clone mode is available with acceptance pending; hardlink+MOWI remains unavailable pending EndpointSecurity entitlement and native acceptance.
Before you start
Windows driver acceptance still requires catalog binding, kernel-policy verification, installer consumption, install/load, and Driver Verifier evidence. macOS clone acceptance still requires the native clone, isolation, metadata, volume/fallback, installer, and doctor/status matrix.
Torya Build & Artifact Fabric — Planned
This panel reserves the Git-adjacent build and artifact job while keeping its package, service, and activation evidence separate from Arivaran Git.
1. Mechanism
  Repository-to-artifact handoff
  Source state, build identity, and resulting artifact form one traceable handoff rather than an implied extension of the Git runtime.
2. Current outcome
  One workflow, separate products
  A buyer can understand where build and artifact work fits without treating in-tree components as a published offer.
3. Evidence boundary
  Evidence boundary
  No public Build Artifact activation or download is offered by this page.
Platform state
Platform and deployment support remain tied to accepted Torya and artifact packaging evidence.
Before you start
Approved package boundaries, activation, artifact retention, and service acceptance.
Git SDK and MCP integrations — Planned
SDK and MCP surfaces belong here only after their public package, permissions, and compatibility contract is accepted.
1. Mechanism
  Typed request boundary
  An integration sends an allowlisted operation through a versioned contract and receives a bounded result with explicit failure state.
2. Current outcome
  A discoverable integration seam
  Developers can find the intended integration owner without inferring that an unpublished package is installable.
3. Evidence boundary
  Evidence boundary
  This is a production-dark integration record, not an install promise or an available MCP endpoint.
Platform state
Runtime and editor support remain unavailable until individually packaged integrations have acceptance evidence.
Before you start
Published package identity, authentication scope, compatibility policy, and documentation.
Git editor tooling — Planned
Editor integrations are contextual entry points to the same Git workflow, with independent signing, marketplace, and compatibility gates.
1. Mechanism
  Editor-to-workflow handoff
  The editor requests a reviewed Git operation and returns the user to a visible branch and worktree result.
2. Current outcome
  Less context switching
  The intended workflow is clear while package and marketplace readiness remains explicit.
3. Evidence boundary
  Evidence boundary
  No editor download or marketplace CTA is available from this panel today.
Platform state
No editor or marketplace is claimed supported until its signed package and acceptance record exist.
Before you start
Signed extension packages, marketplace approval, version compatibility, and uninstall evidence.

Unavailable

Public activation is not available yet.

Public activation is unavailable. No install command is published until the signed distribution, deterministic verification, and safe rollback contract passes.

View release status

Release gates

Public activation is unavailable. No install command is published until the signed distribution, deterministic verification, and safe rollback contract passes.

Public, immutable release channelBlocked
Bootstrap authenticated before elevationBlocked
Complete Linux safety bundleBlocked
Deterministic activation verificationBlocked
Interrupted-upgrade and rollback coverageBlocked

Documentation and animations use the same contract and cannot publish a command early.

Platform modes and public activation are separate facts.

linux-x64Release-gated
linux-arm64Release-gated
macosNot in public activation
windowsNot in public activation