The builder's harness

Work you can
hand over.

Faber is the harness engineering work runs through — control packages, estimates, submittals, and the software behind them — with the decisions visible, the evidence attached, and a record of why.

Read the user guide See how it works
Runs on your machine Evidence before done Built for real jobs
A calmer build loop

You stay in the loop.
The harness carries the load.

An agent that is fast and unaccountable is a liability on work that leaves the building. Faber keeps the scope, the decision, and the proof attached to each other.

01

A home for the work

Projects, sessions, tickets, and the next decision stay together instead of scattering across chats and folders.

02

Nothing closes on a claim

An agent saying it finished is a claim. An independent check against the acceptance criteria is a result.

03

Drawings that stay drawings

Sheets are editable object models, not pictures. The PDF is what you send; the model is what you revise.

04

A memory of why

Decisions and hard-won lessons stay close to the next piece of work, so the same ground is not relearned.

The working agreement

From a request to something you can defend.

Scope, action, and verification stay connected, so an agent can move quickly without the work becoming opaque — and so a result can be handed to someone who was not in the room.

Explore the technical notes ->
  1. 01
    Frame the work

    Turn a request into a clear outcome, with the forks surfaced as decisions rather than assumptions.

  2. 02
    Build in context

    Keep the project, its decisions, and the relevant history close to the work being done.

  3. 03
    Verify before done

    Check the result against the criteria that were agreed before it started, and leave the trail.

Start here

Learn the rhythm
of working with Faber.

Open documentation