Evidence

Proof belongs in public, where it can be checked.

Lumen & Lever makes three kinds of claim: board decisions can be clarified, real workflows can be proved before capital is committed, and production systems can trace every answer to source. This page maps those claims to public evidence, sample records and technical provenance.

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

    The public proof to look for is a short record of questions answered, decisions made and next steps agreed within forty-eight hours. The live service page defines the offer, price and output: written answers, ninety minutes with the board, and a one-page record of decisions.

    Source: The Board Session

  • Proof acceptance report

    The public proof to look for is an acceptance report that names the job tested, the material used, the result, the limitations and whether a Build was justified. The live Proof page defines the commercial test: one workflow, the client’s own material, two weeks, and a written result either way.

    Source: The Proof

  • Sourceline lease demonstration

    The current specimen shows a lease question answered with document, page and clause. It is not presented as a client case. It is a visible demonstration of the standard every Sourceline answer has to meet: nothing asserted without a source line behind it.

    Sources: Sourceline, lease portfolio intelligence, contract administration intelligence

  • Sourcetrace and rtfstruct provenance

    Sourcetrace is the document-structure engine under Sourceline. 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, github.com/keny369/rtfstruct

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.