Research lineage / 2026

Before the engine, there was a question.

Can a retrieved answer remain independently auditable all the way back to named, unaltered source material? Hyphae began by testing that question in a research system. The current product answers it at the data-engine layer.

Published
2026-05-28
Artifact
Historical preprint
Current product
Autonomous data engine

Then → now

The research principle survived. The system boundary changed.

The preprint and the current engine share a demand for evidence, but they are not the same architecture, implementation, product, or benchmark surface.

THEN / PREPRINT

Verbatim quotation over a hash-chained journal

A historical cognitive substrate composed byte-identical quotations and traced them back to stored fragments.

fragment → quotation → source
NOW / ENGINE

Portable result proofs over durable local state

A standalone Rust engine binds an exact query and complete result to a snapshot witness and caller-pinned anchor.

query → result → witness → anchor

Durable thesis

Provenance should be a property of the result—not a story told after the fact.

  1. 01Name the evidence

    A result should identify the exact state needed to examine it.

  2. 02Cross the boundary

    Verification should not depend on trusting the process that served the answer.

  3. 03State what is not proven

    Integrity evidence does not replace identity, authorization, or anchor custody.

Primary artifact

Read the original preprint.

The bundled PDF is preserved unchanged from the historical Hyphae v2 repository and is licensed CC BY 4.0.

Download the paper
Title
Hash-Chained Verbatim Quotation: A Verifiable Provenance Layer for Grounded Retrieval
Author
Mario Gutiérrez · Celiums Solutions LLC
SHA-256
57441c8ed4e2a00d45684fc85c02bc00dbe6cf6c9bc2d5e88f5b0e236dcd2e89
Boundary
Research lineage; not the current engine specification or performance evidence.