Where did the answer come from?
Documents, pages, clauses, public pages, repositories or named records.
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.
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.
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.
Record: Board Session decision record · Service: The Board Session
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.
Record: Proof acceptance report · Service: The Proof
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 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
A claim becomes stronger when it has a source, a method, a limit and a way to check it.
Documents, pages, clauses, public pages, repositories or named records.
The question answered, workflow tested, structure preserved, or decision produced.
Every proof record should say what remains unproven, uncertain or dependent on context.