Evidence

Proof belongs in public, where it can be checked.

Lumen & Lever makes one kind of claim: an answer can be traced to the document, page and clause it came from, and a decision built on it can be checked by someone who was not in the room. This page maps that claim to public evidence, sample records and technical provenance. Two of the four records predate the August 2026 rebuild and are captioned as historical.

Four proof records.

Client work is only named with permission. Where permission does not exist, the evidence record uses a specimen, a method note, a public technical source, or a redacted acceptance pattern.

  • Board Session decision record

    A public specimen shows the questions answered, decisions made, controls agreed and next gate. It demonstrates the form of the promised output without presenting a fictional client result. The Board Session was retired as a stand-alone engagement in August 2026 and its ninety minutes now run inside the Verdict.

    Record: Board Session decision record · Live engagement: The AI Verdict

  • Proof acceptance report

    A public acceptance specimen names the job, evidence, acceptance gates, result and limitations. It shows how a Proof separates a demonstrated capability from a production decision. The Proof is no longer sold stand-alone: it is stage two of the chain, after a Verdict.

    Record: Proof acceptance report · Live engagement: The AI Verdict

  • Sourcetrace lease demonstration

    The traced-answer record exposes the question, answer, date calculation, document, page, clause, assumptions and review boundary. It is a specimen, not a client case.

    Record: Sourcetrace traced-answer demonstration · Capability: Sourcetrace

  • Sourcetrace and rtfstruct provenance

    Sourcetrace includes a structure-preserving document engine. Its public engineering lineage begins with rtfstruct, an open-source RTF parser designed around document structure, diagnostics and source preservation.

    Sources: Sourcetrace, why we built rtfstruct, source repository, archived v0.1.1 release and DOI

How to read this evidence.

A claim becomes stronger when it has a source, a method, a limit and a way to check it.

Source

Where did the answer come from?

Documents, pages, clauses, public pages, repositories or named records.

Method

What was done?

The question answered, workflow tested, structure preserved, or decision produced.

Limit

What does it not prove?

Every proof record should say what remains unproven, uncertain or dependent on context.