No mandatory service
An embedded requirement should not inherit a remote database, cache, credentials, network, and on-call burden by default.
Origin and intent
A data engine for software that must remain itself.
Hyphae was created to make local durability, exact query behavior, and result verification available without turning every application into a distributed system.
No AI tax on structure
Exact KV and structured query should remain useful without embeddings, tokens, model drift, or a provider account.
No opaque success
A result should be complete or fail within its budget. Partial data must never masquerade as a successful answer.
No unverifiable answer
When the trust boundary requires it, a caller should be able to challenge a result offline against pinned evidence.
Design principle
Boring authority. Explicit evidence.
Durability should be quiet. Verification should be inspectable. Optional capabilities should remain optional.
The engine does not ask you to trust its confidence. It gives you the material to verify its result.
Product boundary
Clarity is a feature.
Hyphae names what it does not do so that integrations remain choices rather than hidden dependencies.
Not Mycelium or a cognitive runtime
Not Hyphae Network or Celiums Network
Not SQL, replication, or clustering
Not a hosted SaaS or control plane
Not an embedding model or LLM
Not a framework-specific data layer
