GRAFTTHE TRUST, REUSE AND VERIFICATION LAYER FOR AI-ASSISTED DEVELOPMENT
Find it. Fit it.
Prove it.
AI made writing software cheap. Trusting it is still expensive.
GRAFT finds capabilities you have already built, determines whether they fit another project, and verifies the resulting behavior with evidence bound to the exact revision. It can refuse unsafe reuse, and its evidence expires when the code changes.
Try Interactive DemoWHY GRAFT EXISTS
Generation has outrun verification.
In the 2025 Stack Overflow Developer Survey, 84% of developers use or plan to use AI tools, yet more distrust the accuracy of AI output (46%) than trust it (33%); 66% cite “AI solutions that are almost right, but not quite”. To reuse a capability across real repositories, someone still has to establish what it actually does, whether its evidence is trustworthy, whether it fits the destination, what must change, and whether it still works afterwards. GRAFT turns that into a verifiable engineering process.
One market, two entry points. AI-first builders can now create substantial software quickly with coding agents; GRAFT gives that workflow memory, compatibility analysis, deterministic refusal, provenance and verification. Professional developers and engineering teams have the same problem at scale: years of working implementations are rebuilt across repositories. GRAFT turns that accumulated work into reusable, evidence-backed capabilities.
GRAFT is not another coding agent. Agents create or modify software. GRAFT is complementary infrastructure: it decides whether existing capabilities can safely fit elsewhere and produces revision-bound evidence that they work. The agent can change; the knowledge, decisions and evidence stay with GRAFT.
Deterministic refusal
Most AI tooling optimizes for completing the requested action. GRAFT returns COMPATIBLE, ADAPTABLE or INCOMPATIBLE before anything is written, and refuses reuse when compatibility or evidence requirements cannot be met. Apply stays disabled; the destination is untouched.
Evidence that expires
A green checkmark is not permanent evidence. Every verdict is bound to one revision: CURRENT at that revision, STALE after the next commit, until the capability is verified again. Change the code and GRAFT demands new proof.
Verified in the source first
Before GRAFT remembers a capability, it runs it where it came from and shows why it detected it, file by file. Only required cases decide a verdict; optional witnesses are reported separately.
HOW GRAFT 0.6 WORKS
What actually works today
Find it
GRAFT indexes only the folders you authorise, shows why it detected a capability, file by file, and runs the source to verify it before remembering it locally. The demo harvests hosted sign-in at 13 of 13 required cases.
Fit it
Before anything is written, the destination is COMPATIBLE, ADAPTABLE or INCOMPATIBLE. Incompatible reuse is refused and Apply stays disabled. Several saved capabilities can be composed into one application under dependency and conflict checks.
Prove it
Changes are applied in an isolated worktree and checked with each capability's own contract. The verdict is bound to the exact revision: CURRENT at that revision, STALE after the next commit, until it is verified again.
Under the hood
Discover & verified harvest → Capability Memory → Capability Genome → Compatibility Atlas & Preview → Blueprint / Laboratory → Transplant / composition → CUF verification → Revision-bound evidence & Assembly Ledger
Capability Memory & Genome
The local record of each verified capability, bound to its source revision, and a deterministic model of what it does: entrypoints, inputs, outputs, dependencies, security properties and the contract that proves it.
Compatibility Atlas
A local, evidence-bound record of every transplant attempt and outcome. It informs risk notes; it never overrides a compatibility check or a verdict.
Blueprint & Laboratory
A deterministic AGENTS.md handoff any compatible coding agent can follow, and the Laboratory, which plans and assembles an application from saved capabilities. COMPOSITION VERIFIED appears only when every capability passes on one final revision.
CUF verification
The vendored CUF proof kernel decides each case and the run verdict and computes the proof root. Required behaviour is reported separately from optional witnesses.
Tamper-evident proofs
Proof files are checked by digest (Intact or Mismatch), exportable and verifiable offline. They are revision-bound and tamper-evident, not signatures.
Data Boundary & custody
Before any optional agent operation, data classes and an ALLOW or DENY decision are recorded. Custody keeps metadata and fingerprints, never raw prompts or secrets.
INTERACTIVE EVIDENCE EXPLORER
One capability. An inspectable path.
Real GRAFT evidence · hosted presentation / replay. Exploring these views does not execute code or run a new verification.
Loading and checking recorded evidence…
BUSINESS MODEL
Local tool today. Shared, governed capability registry next.
Implemented and tested
A $49 one-time desktop licence service: Stripe Checkout or a Stripe Payment Link with Managed Payments (Stripe as merchant of record), signed webhooks, and server-side purchase verification before any licence is issued. The Stripe setup is test mode and the hosted purchase flow is not live yet. No revenue or customers are claimed.
Proposed: Free & Pro
Free local reuse and verification for individual developers; a paid Pro tier for professional workflow features. Not built yet; pricing is a proposal.
Proposed: Team & Enterprise
Recurring per-seat Team plans and annual Enterprise contracts for shared verified-capability registries, policy, audit retention, access control and managed deployment. Not built yet.
YOUR REPOSITORIES STAY LOCAL
Built to work on your machine.
GRAFT performs repository-sensitive discovery, adaptation and verification on your machine. This hosted experience uses safe sample projects so the workflow can be explored without uploading private source code.
Beta limits: supported capability kinds and hosts are listed in the documentation; optional agent features need your own configured provider; the macOS build is ad-hoc signed and not notarized.
Security / Local-First Design ↗Continue with GRAFT
Watch the GRAFT 0.6 live demo (4:32) ↗
View source on GitHub ↗ · Technical Documentation ↗ · Download recorded evidence ↧
GRAFT 0.6.0 Galuxium judge build · macOS Apple Silicon · 167,317,360 bytes · ad-hoc signed, not notarized.