Nishi FamilyCompare › Librarian and Data Trust

Nishi vs the Field

Librarian and Data Trust — mechanically measured, liar-killed, sovereign.

Nishi vs DataHub and OpenMetadata and Collibra and Atlan

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.

Feature matrix

CapabilityNishiDataHubOpenMetadataCollibraAtlanNotes
Content-addressed dataset identity (CID)BestNoNoNoNoThe datum IS its sha256 (nxc1-...); catalogs use mutable URNs pointing at external stores
Tamper-evident append-only storeBestNoNoNoNoHistory is sacred, additive segs; catalogs are metadata over mutable warehouses
Dataset lineage graph (producer/consumer)YesBestBestBestBestLive getdents walk of organ producer/consumer edges; the incumbents lead depth (parsed SQL, runtime capture)
Trace-to-god silicon-up genesis lineageBestNoNoNoNoEvery artifact traces parent-by-parent to ORIGIN (hardware); no data catalog traces below the warehouse
Cryptographically-signed provenance (C2PA-class)BestNoNoPartNoNXPC1 ed25519 credential binding CID+source+date; catalogs store mutable metadata, not signed credentials
Deny-by-default provenance verificationBestNoNoNoNoVerify returns 1 ONLY if framing intact AND sig verifies AND entity==CID; tamper/rebind/wrong-key all reject (gate 9/9)
Content dedup and cross-topic flagsYesYesYesYesYesFull-doc fingerprint dedup + two-topics-same-source flags
Freshness / staleness reviewYesPartPartYesYesMoving/static/constant state machine; Collibra/Atlan have richer freshness SLAs
No-new-TSV migration governance (live guard)BestNoNoPartPartLive RED on any unlisted new .tsv (10 violations now); catalogs assume clean data already lands in the warehouse
Schema drift detectionYesYesYesBestBestDetects drift kinds; the incumbents enforce contracts and alert downstream owners
Store compaction and retentionYesYesYesPartYesss_compact reclaims superseded segs; enterprise catalogs have policy-driven lifecycle
Ed25519 signatures on recordsYesNoNoYesNoSovereign signature primitive; Collibra signs via enterprise PKI integrations
Library ingest and inverted indexYesBestBestBestBestBM25 over the library; incumbents have elastic-scale discovery search
Format-sprawl audit instrumentBestNoNoNoNoMechanically classifies every file native-vs-legacy; catalogs profile schemas, not on-disk format sovereignty
Applied subject classification of the whole libraryNoBestBestBestBestThe Dewey-decimal for our data: shelf/facet organs EXIST but the corpus is NOT classified/browsable; incumbents auto-classify + glossary
Running freshness management (scheduled review+re-mine)NoBestBestBestBestnx_research_freshness+shelf_life exist but are NOT scheduled/running; incumbents have freshness SLAs + quality monitors
Librarian auto-reviews ingested material + RACI handoffYesPartYesPartYesORCH-R1 gated: librarian reviewed 1326 docs, flagged 239 not-up-to-scruff, wrote R=librarian/C=researcher handoff to seg-store; remaining = auto-TRIGGER from the researcher bank + MCP API
Cross-team RACI orchestration engine (call/resolve/dispatch)BestPartYesPartPartORCH-R3 gated 13/13 + PROVEN LIVE: nx_orchestrate organize run -> resolved RACI from nishi_raci.tsv (A=librarian) -> dispatched -> librarian workstream RAN (1329 reviewed); denies unknown activities. No data catalog dispatches teams by RACI
MCP orchestration APIs (call API -> team -> workstream)NoYesYesPartPartThe keystone for autonomy: no standard MCP API that engages a team to run a workstream; incumbents ship agentic active-metadata
Column/field-level lineageNoBestBestBestBestOur top data-trust gap; DataHub/Collibra trace column-to-column
Data-contract enforcement at ingestNoYesPartBestPartDetect exists (drift) but not enforce-at-the-door; contracts are the 2025/26 frontier
Catalog discovery UI surfaceNoBestBestBestBestNo live /librarian browse page yet; the incumbents ARE catalog UIs
Universal library foundationing (CID+sign+god-trace)BestNoNoNoNoEvery library doc content-addressed + ed25519-signed + traced to god; 1314/1314 foundationed GREEN (resumable OOM-safe); no data catalog signs AND silicon-traces every ingested doc
coverage 739/1000EXCEEDS 9PRESENT 8ABSENT 6
Honest verdict. Nishi has broad, sovereign search-engine presence — a real organ behind every core ranking and crawl axis, built bits-up in one language. It is not yet a scale or neural-ranking rival: the majors lead on index size (billions to trillions vs a Common-Crawl-seeded slice) and trained rerankers. Nishi's genuine exceeds are structural — owning the whole stack, neutrality by construction, and a zero-JS integer-deterministic result page. The climb is a bigger index and a trained reranker.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/librarian.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.