Skip to content
Guide

How the record works

Every change ChangeFabric makes leaves one record. A buyer, a team lead and an engineer need different depths of the same fact, so the record shows it at each.

Record

One fact, four depths

This change was governed.

The same fact, read at four altitudes.

  1. L0Buyer

    This AI change had an owner, a reviewer and a record.

  2. L1Business owner

    Ticket #418, asked by Finance operations. Plan accepted by the billing owner.

  3. L2Team lead

    PR #212: governance check passed with 0 violations, unit tests passed. $0.72 of a $5.00 budget.

  4. L3Engineer

    claude-sonnet-5 · 3 model calls · tokens and latency per call · secrets redacted

Shown with demo data, not a customer's record.

Decisions

Where a person decides

The points ChangeFabric will not cross on its own.

  • Frame

    Accept or reject the plan

    An agent drafts the plan; a person accepts it, or rejects it with a reason and a remedy.

  • Limits

    Set the ceiling

    A person sets what each automation may spend and run. With no ceiling, it does not run.

  • Weave

    Merge the pull request

    The change merges through your own review and branch rules, never around them.

  • Rejections

    Decide on ChangeFabric's own rejections

    When ChangeFabric rejects its own plan, it waits for a person unless the project says otherwise.

Start

Getting started

Four steps, done with our team during a design-partner engagement.

  1. 1

    Connect GitHub

    Install the ChangeFabric GitHub App on the repositories you choose.

  2. 2

    Write the rules

    Capture one project's rules as Frame control records.

  3. 3

    Set a ceiling

    Choose the model and the spend and run limits for one automation.

  4. 4

    Run one change

    Take one ticket from plan to pull request, then read its Trace record.

Engineering

For the engineers

What exists today. We will add to this list when something ships, not before.

  • GitHub App

    Issues in, pull requests and checks out, with only the permissions it needs.

  • API keys

    Your own scripts and tools reach ChangeFabric with keys you create and revoke in the app.

  • Run records

    Every model call with its model, tokens, cost and latency, kept in full with secrets removed.

Access

Request access

ChangeFabric is in a closed beta with a small group of design partners. Tell us where AI work already runs in your business.

  • A person on our team reads every request.
  • The first conversation is about the one workflow you name, not a generic demo.
  • If it fits, we scope a design-partner engagement and price it with you.

So the first call is about your work, not a generic demo.