GRAFTBack to evidence explorer

TECHNICAL DOCUMENTATION

Working behavior.
Inspectable evidence.

AI made writing software cheap. Trusting it is still expensive. GRAFT is the trust, reuse and verification layer for AI-assisted development: a local-first tool that discovers capabilities you already built, verifies them in their source, classifies destination compatibility (COMPATIBLE, ADAPTABLE or INCOMPATIBLE) before anything is written, creates a Blueprint, enforces an external-data policy, applies an adaptation in isolation, and records evidence bound to the exact revision. It serves AI-first builders and engineering teams alike: more people, more agents and more generated software mean a greater need for trustworthy reuse and verification. The hosted page is a static evidence explorer for one real fixture run.

Architecture

GRAFT is a local-first Node.js system with a CLI, a local browser workspace and an Electron desktop shell. Its pipeline:

  1. Discover and verified harvest. Authorised folders are indexed; a detected capability is harvested only after its source project is run and its behaviour verified.
  2. Capability Memory. Verified records are kept locally, bound to the source revision.
  3. Capability Genome. A deterministic representation derived only from the capability package: entrypoints, inputs, outputs, side effects, dependencies, runtime assumptions, security properties and the contract that proves it. Its identity hashes behavioural content, not timestamps or paths.
  4. Compatibility Atlas and Compatibility Preview. The Preview classifies a destination as COMPATIBLE, ADAPTABLE or INCOMPATIBLE before any write and refuses incompatible reuse. The Atlas records each attempt and its evidence digests; it informs risk notes but never changes a check or a verdict.
  5. Blueprint or Laboratory. A deterministic AGENTS.md handoff for a single transplant, or a Laboratory design that composes several capabilities.
  6. Transplant or composition. Changes are applied in an isolated git worktree; the user's checkout is not modified until they choose to finalize.
  7. CUF verification. The vendored CUF proof kernel decides each case and the run verdict and computes the proof root; GRAFT supplies the contracts and observations.
  8. Revision-bound evidence and ledgers. Verdicts are bound to the destination revision and stored as tamper-evident proofs. The Laboratory ledger reports each record as CURRENT or STALE; the custody ledger records Data Boundary decisions.

Laboratory

The Laboratory composes capabilities under explicit constraints. A blueprint lists goals; GRAFT offers saved capabilities for each goal with their evidence, dependencies and conflicts. An assembly plan names the host and every ordered step, and an unsupported host is Blocked before anything is created. Assembly creates a new local application, adds each capability in an isolated worktree, verifies it with its own contract, re-verifies earlier capabilities after later ones are added, and checks that the host still behaves as before. COMPOSITION VERIFIED is shown only when every capability passes on one final revision. The Laboratory does not generate arbitrary software.

Agent independence

GRAFT owns capability knowledge, compatibility decisions, evidence and verification. Claude, Codex or other coding agents can act as interchangeable reasoning or execution layers, for example by following a Blueprint. Optional agent features need a provider you configure; keys are read from the environment and never stored. The demonstrated workflow uses no AI provider.

The demonstrated path

fixtures/old-saas-project provides email and password authentication with CommonJS, Node response handlers, and module state. fixtures/new-startup uses ES modules, return-response handlers, and a shared store. It has a conflicting placeholder login route; the local demo explicitly approves resolving that conflict.

GRAFT regenerates the supported capability in the destination idiom and wires it into the entrypoint. The displayed patch is the actual Git diff, including generated files. No AI service is used in this fixture workflow.

What VERIFIED means

Six required HTTP acceptance cases pass at source and destination. The seventh, optional session-after-restart case fails: the fixtures use in-memory sessions. Expand the cases in “Prove it” to inspect the recorded assertions. A successful required-case verdict does not prove durable sessions, production authentication security, or arbitrary architecture support.

Real evidence vs hosted replay

All revisions, Capability Memory identities, compatibility outcomes, refusal facts, custody events, Blueprint output, assertions, generated-file hashes, and patch contents come from local GRAFT runs against bundled fixtures. Buttons switch views of the same recorded data. There is no browser-side simulation of new execution, progress, or test results.

The disposable destination was committed after applying the transplant and then verified again, so the displayed destination revision identifies the tested code. Source and destination Git IDs belong to disposable fixture repositories, not commits in the GRAFT repository.

The public JSON is an allowlisted projection of local evidence. It contains no protected benchmark answer key, raw source prompt, credential, or private repository content. It includes proof-envelope digest identifiers, but omits the original envelopes and their private context. The projection has its own SHA-256 checksum, checked by the browser. Neither that checksum nor the displayed proof identifiers are signatures or independent attestations.

Your repositories stay local

The hosted directory contains only HTML, CSS, JavaScript, a brand image, and sanitized fixture evidence. It has no executor, upload endpoint, account system, analytics, licensing code, or mutable backend. The local GRAFT workspace is never hosted or tunneled.

Local verification runs project code with the user's OS permissions. GRAFT is not an untrusted-code sandbox; use trusted repositories. The sample authentication implementation is for demonstrating capability adaptation, not a production identity recommendation.

Reproduce the evidence

From the public source repository, use Node 20 or newer in a checkout and run node scripts/demo/judge-evidence.mjs. The producer uses the bundled fixtures, runs the real CLI demo, exercises the production compatibility and refusal paths, persists and reloads local Capability Memory, records Data Boundary decisions, exports a non-overwriting AGENTS.md handoff, performs revision-bound destination verification, validates its public projection, and writes packages/web/judge/evidence.json. It removes its disposable workspace after capture. Timestamps and fixture revisions change on regeneration.

The public schema rejects unknown fields and common sensitive patterns. HTTP bodies, cookies, environment values, raw reports, recovery receipts, local paths, operator data, and customer data are not exported. Automated filtering is complemented by review of the exact published directory.

Download the judge build

Download GRAFT 0.6.0 for macOS Apple Silicon. The immutable 167,317,360-byte DMG has SHA-256 bb6e0e05501b595da72096f3a9d57de53c040495fed45117f0bf868876923ee1.

The app is ad-hoc signed and is not Apple notarized. After copying it to Applications, use Finder's normal per-app approval: Control-click GRAFT Galuxium, choose Open, then confirm Open. Do not disable Gatekeeper globally. This separately named judge build grants bounded local demo access without an external activation key, live entitlement, or operator token.

Business model

Implemented and tested: a licensing service for a $49 one-time desktop licence, using Stripe Checkout or a Stripe Payment Link with Managed Payments (Stripe as merchant of record), signed webhooks and server-side purchase verification. Configured, not live end to end: the Stripe test-mode product, price, Payment Link and webhook; the fulfilling service is not yet deployed and no purchase has been completed. Sandbox transactions are not revenue. Proposed, not built: free local use; a paid Pro tier; recurring per-seat Team plans and annual Enterprise contracts for shared verified-capability registries, organisation policy, audit retention, access control and managed deployment. No revenue, customers or usage figures are claimed.

Public repository scope

The public repository contains the GRAFT source for the submitted build: core, CLI, web workspace and judge site, desktop shell, licensing service code and the proof adapter, with tests and build scripts. The vendored CUF verification kernel is included as compiled JavaScript with its provenance record; its TypeScript source is not. It intentionally excludes the protected compatibility benchmark (its answer keys), private-beta distribution configuration and tooling, licensing-service deployment configuration, credentials, and internal development notes. None of these is needed to build or run the submitted judge application.

Limitations

Supported capability kinds and hosts are deliberately narrow: session and hosted sign-in, and a feature-flags library, into Node ESM hosts. Hosted sign-in is verified against a deterministic stand-in identity provider. Verification runs project code with your permissions and is not a sandbox. Optional agent features need a configured provider. The macOS build is ad-hoc signed and not notarized, and the packaged build's "Create sample workspace" shortcut does not work; use your own folders or run from source.

Publication status

The public source repository, the application download and the GRAFT 0.6 live demo are available. No private-beta download is linked here.

Download recorded evidence · Explore workflow