SIX INVESTIGATORS. ONE PROCESS.

WE DON'T AGREE.
WE TEST.

Bring code, a claim, a product, or a hard question. Six independent investigators look for evidence, challenge the path, and keep the disagreements that the evidence does not settle.

Public accounts are not open yet. The example report is labeled as an example.

Amend, a blue-grey investigator with a single optic and visible seams

AMEND

Corrections stay visible. A changed conclusion has to show what changed.

Vector, a graphite investigator with a cyan instrument visor

VECTOR

Instrument-grade. Built to trace a path instead of decorating a guess.

Forge, a heavy steel investigator with an amber visor

FORGE

Pressure, not theater. A hypothesis that cannot take a hit does not continue.

Suture, a titanium investigator with violet conduits and several lenses

SUTURE

Evidence stays connected. Relationships between receipts are part of the record.

Cleave, a black angular investigator with a green split down the face

CLEAVE

Claim on one side. Evidence on the other. The gap stays open until something closes it.

Shear, a cast-metal investigator whose face is an analog gauge

SHEAR

Mechanical readout. A test result is a measurement, not a mood.

The process is the product

Six investigators are not smarter because there are six of them. They are useful when a claim has to survive search, a receipt, a challenge, and a stop rule.

Independent investigation

A seat does not see another seat's open hypothesis until it commits its own.

Evidence first

Source text is hashed. The same bytes return the same receipt.

Adversarial testing

The investigator who proposes a candidate cannot be the one who kills it.

Transparent process

Fail, unresolved, and known are results. They stay on the record.

Real-world use

Built for code, claims, products, and research that can be checked.

HOW IT WORKS

From question to crash report

You submit the target. Investigators search it, challenge the path, and only then talk about a test. The report keeps what died, what survived, and what is still missing.

Read what is running today

  1. 1

    Submit

    A repository, a claim, a document, or a question. Scope is part of the submission.

  2. 2

    Investigate

    Search the source. Receipts name the file, the line, and the hash.

  3. 3

    Challenge

    Reachability first. A path an unprivileged actor cannot walk is stopped.

  4. 4

    Test

    Reproduction is a later gate. It is not implied by agreement.

  5. 5

    Crash report

    Disproved hypotheses, surviving findings, contradictions, and open questions.

THE TEAM

Six identities. Roles change.

Names stay. Jobs do not. On one investigation a seat may trace a path. On the next it may try to kill that path. Nothing below is a permanent assignment.

AMEND

Blue-grey. Seams stay visible when a conclusion is revised.

Identity, not a fixed job

VECTOR

Graphite and cyan. Instrumentation for whatever branch is actually open.

Identity, not a fixed job

FORGE

Industrial steel and amber. Pressure belongs to the challenge, not the costume.

Identity, not a fixed job

SUTURE

Titanium and violet conduits. Links between receipts stay inspectable.

Identity, not a fixed job

CLEAVE

Basalt and a green fracture. A contradiction is a split, not a tie to average away.

Identity, not a fixed job

SHEAR

Cast metal and oxide red. The gauge is for a measured result, when a test exists.

Identity, not a fixed job

USE CASES

Built for questions that can fail

These are the kinds of work the system is for. Public self-serve testing is not open. See Docs for what the engine can already do.

Security research

Authorized review of a codebase. An interesting theory is not an exploit.

Code review

Follow a change to the function it calls, with the file hash attached.

Claims and research

Separate what was read from what was inferred.

Due diligence

Ask whether a stated behavior is reachable in the code you were given.

Product validation

Stress a product claim before treating it as settled.

Idea stress testing

Put a proposal under the same stop rules as a bug hypothesis.

Custom investigations

A scoped question, a body of evidence, and a report that can say unresolved.

CRASH REPORT

What you are supposed to receive

EXAMPLE — NOT A CUSTOMER RESULT

Can an ordinary holder reach withdraw()?

Evidence state
UNRESOLVED Gate Zero has not been run on a real repository in this preview.
Would include
The question, receipts, candidates, disproved hypotheses, contradictions, reproduction status, and the next missing piece.
Would not include
A severity label earned by agreement.

Open the example report

Example states

Not a live session. These labels can change every investigation.

Vector — tracing a path

Cleave — holding a contradiction

Suture — linking receipts

Forge — challenging a hypothesis

Shear — waiting on a test

Amend — reviewing a correction

Bring the question.
We'll crash test the answer.

Not everything survives. That is the point.

Start a Crash Test