stack-ids owns canonical identity. Adapter-local identifiers were superseded after ADR-031.
02THE PROOF
Do not trust the answer.
Inspect its path.
Mnemes inherits a strict evidence vocabulary from the stack beneath it. Search receipts, route receipts, source spans, temporal state, and integrity checks can make behavior inspectable—without pretending inspection makes the answer true.
01 / RETRIEVAL UNDER PRESSURE
Meaning, exact language,
relationships, and time.
Change the archive density, choose a failure or cross-device scenario, and run the five-stage retrieval model.
Q
FTS5 / 428
DENSE / 612
GRAPH / 84
1,124 candidates → 12 current results
AGENT QUERYWITNESSED ANSWER
“What owns package identity now?”
BM25.76
dense.91
graph.64
3 older statements excludedcurrent head resolved
Interactive capability model—not a benchmark. Counts illustrate a dense archive and do not report measured performance.
Retrieve more than matching text
Lexical search preserves exact language; dense search finds meaning; graph traversal follows typed relationships.
Resolve what is true now
Current, historical, superseded, contradicted, and quarantined records remain different states.
Return the path with the answer
The receipt can disclose candidates, backend, exactness, filters, fallback, degradation, and source identity.
02 / ONE RECEIPT, OPENED
What happened
without claiming why.
A receipt can bind backend, candidates, exactness, fallback, degradation, temporal filters, and result identity. It cannot certify factual truth or permission to act.
R
execution observedA witness for the path.
Not a verdict on reality.
The receipt says which path produced a named result set under a named scope. Assertion authority, action authority, and claim truth remain separate decisions.
receipt ≠ correctness
relevance ≠ authority
memory ≠ permission
03 / EVIDENCE SCOPES
Every green light
needs a noun.
A source pass, package pass, live canary, and receipt are different kinds of evidence. “Verified” without a scope is just decorative certainty.
Current checkout
Files, commit, features, migrations, contracts, and tests inspected at one source identity.
Shipped artifact
The crate or package contains the declared assets and survives a fresh install path.
Observed runtime
A named binary and configuration exercised a named behavior in a named environment.
Recorded execution
A typed artifact records what ran, what degraded, and what output identity was observed.
04 / PUBLIC SYSTEM PULSE
Source you can open.
Freshness you can see.
Current registry and repository data is requested directly where possible. Partial failure stays partial instead of manufacturing a fully live dashboard.
public source pulseLIVE WHERE AVAILABLE · FALLBACK JUL 16, 2026
01
control plane
—registry unavailablemnemes
- downloads · unavailable
- —
- stars · unavailable
- —
- GitHub activity
- unavailable
02
agent protocol
v0.5.4snapshot Jul 16, 2026semantic-memory-mcp
- downloads · snapshot
- 167
- stars · unavailable
- —
- GitHub activity
- unavailable
03
memory engine
v0.5.11snapshot Jul 16, 2026semantic-memory
- downloads · snapshot
- 352
- stars · unavailable
- —
- GitHub activity
- unavailable
Registry and repository values are requested from public APIs in your browser. If crates.io is unavailable, versions and downloads use only the bundled snapshot observed Jul 16, 2026 and are labeled as such. Missing GitHub values remain unavailable; nothing is inferred from a different source.
05 / THE PUBLIC BOUNDARY
Source-hardened.
Not release-certified.
Safe to say
Open-source Rust crates exist; canonical SQLite state, routed server shards, temporal views, provenance, bounded MCP profiles, and optional receipts are present in current source.
Not established here
Production readiness, security certification, universal truth, autonomous permission, competitor superiority, device-owned continuous replication, or performance outside a named benchmark receipt.