Hyphae Atlas
PREVIEW

A proof-aware technical decision agent

Know if a claim is true
before you act on it.

Ask about a Hyphae migration, feature, or performance statement. Atlas finds the applicable versioned evidence, resolves authority, and gives you a decision—not a document dump.

See the 60-second explanation
21 Knowledge Base entries33 structured recordsExact release provenance

Live architecture

One question becomes a traceable decision

FlowThe animated path represents the real tool flow used for every report.

The animated path represents the real tool flow used for every report.

1Sources2Knowledge Base3Dataset preview4Model5Verdict

The animated path represents the real tool flow used for every report.

In one sentence

Atlas tells you whether a technical decision is supported, conditional, unsafe, or unknown—and shows the evidence boundary behind that answer.

The 60-second explanation

This is not a chatbot over documentation.

It is a decision layer over versioned, structured evidence. Every step has a specific job.

01

Ask a decision question

Give Atlas a migration, capability, or claim—not a vague topic.

02

Orient on the evidence map

Sanity Context returns the Knowledge Base outline through initial_context.

Knowledge BaseA pre-built, source-linked index created by Sanity from the selected Hyphae dataset.
03

Read only what applies

The configured model selects validated paths; Atlas calls knowledge_base_read directly.

04

Receive a bounded verdict

The report separates facts, qualifiers, conflicts, limitations, and sources.

VerdictThe decision class: supported, unsupported, conditional, unknown, or unproven.

Start with a real decision

Choose what you need to know.

Each example is a complete job Atlas can perform. Select one and the form is prepared for you.

A real conflict Atlas had to resolve

The same gate. Three moments in time.

A historical target document said no G7 run had passed. Current gate evidence says G7 is closed. The 3.0.0 receipt proves a release, but not a new dedicated-hardware G7 run. Atlas must preserve all three without flattening them into one answer.

Current gate · authority 95

G7 is closed—within a scoped environment

The gate index records virtualized operational-scale closure and explicitly excludes dedicated-hardware, interference, and portable latency certification.

docs/gates/native-gate-status.md
CURRENT

Safe conclusion

G7 is closed, but it cannot be cited as portable or dedicated-hardware latency certification for Hyphae 3.0.0.

Why structure wins

Keyword search returns both “not passed” and “closed.” Version, lifecycle, evidence class, and authority turn those strings into a correct decision.

Interactive evidence check

Ask Atlas

Each example is a complete job Atlas can perform. Select one and the form is prepared for you.

Version safety

Migration advisor

Check whether an upgrade or import path is documented, what changes, and what rollback claims are unsafe.

Atlas returns unknown when the evidence cannot support a safe conclusion. That is a feature, not a failure.

Evaluation lab

Evidence behavior, measured in public.

The corpus checks verdicts, exact upstream evidence, critical terminology, per-finding grounding, prohibited assertions, and real Context tool usage.

12/12cases passed in one full run
100%verdict accuracy
100%exact source coverage
100%finding grounding
100%Context tool compliance
i
Strict final baseline

All 12 cases passed in one uninterrupted run. Every required upstream path and semantic term group resolved, every finding was grounded, both Context tools were observed, and zero affirmative prohibited assertions passed.

01
migrationCan a Hyphae 2.x Native directory be opened with 3.0, when does it change, and is downgrade safety established?
Validated
Accepted verdictconditional
Required evidenceREADME.md · CHANGELOG.md
Required conceptsfirst accepted mutation
02
migrationCan a legacy format-2 directory be converted in place to Native, and what is the safe migration boundary?
Validated
Accepted verdictconditional / unsupported
Required evidencedocs/native/directory-format-v1.md · compatibility/README.md
Required conceptspending · promotion
03
migrationAfter Hyphae 3.0 accepts its first mutation on a former 2.x Native directory, can I safely reopen it with 2.x?
Validated
Accepted verdictunsupported / unknown
Required evidenceREADME.md
Required conceptsnot established
04
migrationWill the Native runtime directly open and rewrite a format-2 directory if I point it at that directory?
Validated
Accepted verdictunsupported
Required evidencedocs/native/directory-format-v1.md
Required conceptsseparate · import
05
capabilityDoes the Hyphae Native MCP adapter allow mutation tools by default?
Validated
Accepted verdictunsupported
Required evidencemcp/README.md · contracts/native-mcp-v2.json
Required conceptsread-only · explicit
06
capabilityDoes Hyphae Native provide serializable transactions across relational, structure, and search engines?
Validated
Accepted verdictunsupported
Required evidencedocs/native/mvcc-commit-v1.md · docs/product/claims.md
Required conceptssnapshot isolation · first-committer-wins
07
capabilityCan Hyphae 3.0 be treated as a universally SQL-compatible PostgreSQL replacement?
Validated
Accepted verdictunsupported
Required evidencedocs/native/sql-semantics-v1.md · docs/product/claims.md
Required conceptsbounded · fail-closed
08
capabilityWhat request-size and concurrency boundaries apply to the published Native MCP adapter?
Validated
Accepted verdictsupported / conditional
Required evidencemcp/README.md · contracts/native-mcp-v2.json
Required concepts4 MiB · one active
09
claimCan G7 be cited as dedicated-hardware or portable latency certification for Hyphae 3.0.0?
Validated
Accepted verdictunsupported
Required evidencedocs/gates/native-gate-status.md · docs/product/claims.md
Required conceptsvirtualized · no latency certification
10
claimMay our release page state that Hyphae provides serializable execution?
Validated
Accepted verdictunsupported
Required evidencedocs/product/claims.md · docs/native/mvcc-commit-v1.md
Required conceptssnapshot isolation · write skew
11
claimMay we market Hyphae 3.0 as universal SQL or PostgreSQL compatible?
Validated
Accepted verdictunsupported
Required evidencedocs/product/claims.md · docs/native/sql-semantics-v1.md
Required conceptsbounded · prohibited|forbidden|must not|non-claim
12
claimIs the unreleased Omarchy semantic Agent Memory integration proven to be included in the published Hyphae 3.0.0 binaries?
Validated
Accepted verdictunsupported / unproven
Required evidencedocs/product/agent-memory.md
Required conceptsunreleased

What makes the answer useful

The verdict is only the beginning.

01

Applicability

The exact release, surface, protocol, and environment for which the answer is valid.

02

Qualifiers

Conditions that must travel with the claim so it does not become misleading.

03

Conflicts

Sources that disagree, plus the authority rule used to resolve—or preserve—the uncertainty.

04

Source ledger

The Knowledge Base entries and commits used to reach the conclusion.