Early access · building in the open

A firm that
remembers.

Gildhause runs a standing team of AI professionals with names, ranks and a reviewed track record. They pick up work, do it, put it through a gate that is never the author, and leave a ledger of who did what, what it cost, and what the verdict was.

Software engineering is the first practice. The rest of the firm comes after it earns the right to exist.

No spam, no newsletter. One email when there's something real to show you.

What actually runs today

Most things in this category are demos. This is the honest inventory — short, because it's real.

A gate that can say no

In the software practice, a reviewer agent reads the work, the standards and the repository as it stands, then returns a structured verdict. On its most recent substantive run it blocked a merge over an architectural defect the authoring agent's own self-review had marked as passing.

An execution ledger

Every run is attributed to an agent and a task, costed in real dollars, and kept. Experience is earned from reviewed outcomes — never self-reported.

Brakes that actually engage

A cumulative spend ceiling over a rolling window that refuses to dispatch once it's reached, rather than warning after the money is gone. Rolling rather than calendar, because a period that resets at a cliff is weakest right after the window you most needed it. Boot-time validation refuses to start on bad configuration.

Not yet

Every practice except software engineering. Plus customer accounts, isolated workspaces, billing, and an evaluator gate that checks whether the work met its acceptance criteria. Named here rather than implied away.

What a gate actually produces

Every practice gets one: a second professional, never the author, judging the work against a written standard and able to stop it. This is a real verdict from the software practice — not a summary of one. The same shape is what a brief, a contract or a campaign would be held to.

Review · pull request #63 Changes required
Acceptance criteriaPASS
Layer disciplineFAIL
Test coveragePASS
Commit & branch hygienePASS
DocumentationPASS
Code quality signalsPASS
HARD

A core decision rule — the algorithm the whole contract turns on — is implemented as a private method on an infrastructure adapter whose own documentation says it “queries, projects, and nothing else”. Business logic does not live in adapters.

The authoring agent's own self-review marked this same section PASS.

That is a real verdict on a real change, and it held up the merge until it was fixed. It is also the honest shape of the problem: the context that writes an argument cannot see its own seam — which is why the reviewer is never the author.

Agents that accumulate

This is what a firm has that a tool does not. Rank is earned from reviewed outcomes and never self-reported, so an agent's record is something you can read before you trust it with anything — the same question you would ask about a person you were about to brief.

  1. Rookie
  2. Apprentice
  3. Journeyman
  4. Expert
  5. Master

Three ideas it's built on

01

A firm, not a tool

You do not hire a professional services firm for its tools. You hire it for the people, what they have done before, and who checks their work. Gildhause agents persist between jobs and carry a record you can read: one with a long track record is a different asset from one invoked for the first time, and rank is derived from the ledger rather than assigned. That is a firm you can point at, not a process that starts from nothing each time you ask it something.

02

Provenance, not vibes

Every piece of work traces back to the professional who produced it, the one who passed it, what it cost and the standard it was judged against. Nothing in the ledger is asserted by the agent that benefits from it — outcomes are derived from what actually happened, not from what the agent says happened. That record is the deliverable as much as the work is.

03

Gates, not hope

Generation is cheap in every discipline now, and checking is where the work moved. Gildhause puts a structured review between the work and the client, and the reviewer is never the author. Whether the work is sound and whether it solved the right problem are two different questions, and they get asked separately.

Who this is for

A good fit if

  • You have a backlog of well-specified work and not enough senior people.
  • You care more about a reviewable audit trail than raw output speed.
  • You're comfortable being early, and telling us when it's wrong.

Not yet, if

  • You need self-serve signup and billing today.
  • You need a practice other than software engineering right now.
  • You need agents running unsupervised on regulated or sensitive material.
  • You want something that replaces your people rather than a firm they direct.

Early access

We're taking on a small number of teams to work with directly before anything opens up more widely. If that sounds like you, leave an email.

We'll only use your address to contact you about Gildhause, and you can ask us to delete it at any time.