Nishi Family › Compare › Living Documentation, Wiki and Developer Portal (SOTA)

Nishi vs the Field

Living Documentation, Wiki and Developer Portal — the full field, measured, sourced.

The Nishi Atlas (nx_eco_graph cards + auto-regenerating wiki surface) vs the dev-portal / wiki / PKM / catalog field

How this is scored. This is a state-of-the-art comparison across the FULL competitor field: quantitative axes carry measured / published numbers (Nishi’s column is our own measurement, competitors are researcher-sourced), grade axes use Best / Yes / Part / No. Every axis carries a source note. No single vanity ‘coverage’ score — the honest picture is per-axis. Where Nishi is under SOTA, that is filed work with an owner, never ‘by design’ (operator law: less-than-SOTA is never design) — every sub-SOTA axis maps to a frontier rung; the only legitimate divergence from the field is a measured exceed bet that carries its number (e.g. no-float determinism). The climb is the plan.
CapabilityNishiBackstageConfluenceNotionObsidianGitBookDocusaurusSourcegraphDataHubNotes / source
Authoring and editing
WYSIWYG rich-text editorNoNoBestBestYesYesPartNoPartNishi docs are generated organs plus markdown, no visual editor (honest gap); Confluence/Notion editors are the bar
Markdown docs-as-codeYesYesPartPartYesYesBestNoNoNishi pages generated from typed source; Docusaurus/MkDocs own docs-as-code
Real-time collaborative editingNoNoYesBestPartYesNoNoNoOT/CRDT co-editing; Notion/Confluence lead; Nishi has none (honest gap)
AI-assisted authoringNoNoYesBestPartYesNoYesNoNishi has a sovereign LLM lane but it is not wired to doc authoring (honest gap); Notion AI and Cody are the bar
Templates and scaffoldingYesBestYesYesPartYesPartNoNoNishi card scaffolds plus nx_store_seed; Backstage software templates are the dev-portal bar
Structure and linking
Backlinks bidirectionalYesPartPartYesBestPartNoYesYesmemory wikilinks plus graph edges; Obsidian is the backlink bar
Knowledge dependency graphYesYesNoNoYesNoNoYesYesnx_eco_graph 16222 organs and 42088 edges; deeper than a catalog of direct deps
Transitive lineage to primitivesBestNoNoNoNoNoNoPartYesnx_eco_graph_pedigree walks roots-to-god to nx_tier and nx_syscalls; catalogs show direct edges only
Software service catalogYesBestNoPartNoNoNoPartYesAtlas cards are an organ catalog; Backstage catalog is the portal bar
Auto-generated diagramsYesPartPartNoPartNoNoPartYesnx_eco_graph_atlas family-tree SVG plus nx_eco_graph_mermaid, zero-JS, computed from the graph
Living contract - freshness and drift
Auto-generated from source of truthYesYesNoNoNoPartPartYesYescards and graph scan the real organ tree; not hand-maintained prose
Doc IS the unit - cannot driftBestNoNoNoNoNoNoNoNothe Atlas keystone: the card IS the callable runnable unit AND its documentation; no separate artifact to drift
Staleness and drift detectionPartPartYesNoNoNoNoYesYesF224 auto-ingest cadence in flight; today the graph rebuild is manual (honest partial)
Freshness and last-touched provenanceYesYesYesYesPartYesYesYesYessovereign WMS commit and reflog plus additive-store history, not a git diff
No-link-rot content-addressedBestNoNoNoNoNoPartNoPartCID-addressed store (vizsla_doc); links resolve to immutable content
Honest maturity and trust
Evidence-capped maturity gradingBestNoNoNoNoNoNoNoPartevery card shows an L0-L5 liar-killed grade (nx_maturity_board); no wiki grades its own honesty
Never-lose tamper-evident versioningYesNoYesYesPartYesPartNoPartadditive CID plane, old bytes never destroyed, ed25519 sealed; beats soft-delete history
Cryptographic provenance signedBestNoNoNoNoNoNoNoParted25519 C2PA-class signing on the store (librarian domain 9/9)
Full-text and semantic searchYesYesBestYesYesYesYesBestYesnishi_search corpus plus SGNS embeddings; competitors have more polished UIs (depth gap)
Live activity and generativity
Live runtime activity on the pageBestPartNoNoNoNoNoNoPartnx_swarm_beat/place/job light a card when its organ is running; the doc shows what executes now
RACI ownership on every nodeYesBestPartPartNoNoNoNoYescrew_capabilities plus nx_rebac; Backstage owner field is the portal bar
Generative recombination - name outcome to planPartNoNoNoNoNoNoNoNoF225/F310 atlas_recombine walks the graph for unproven-opportunity compositions; no wiki does this
Autonomous discovery of unproven opportunitiesPartNoNoNoNoNoNoNoNomaturity-gap x momentum feeder emits research-opportunity cards (F208/F225); unique direction
MCP agent-native surfaceBestNoPartPartNoPartNoPartPartevery card is readable and callable over the live MCP plane by agents today
Sovereignty and delivery
Zero third-party dependencyBestNoNoNoPartNoNoNoNoown language, compiler, TLS, store and renderer; zero React/Node/JVM/Elastic
Zero-JS deterministic pagesBestNoNoNoNoNoNoNoNoabout 5 KB static HTML, bit-reproducible; competitors are JS single-page apps
Self-hostable local-firstYesYesYesNoBestPartYesYesYesruns on your own hardware, no cloud dependency; Obsidian is the local-first bar
Plugin extension marketplaceNoBestBestYesBestPartYesYesParthonest gap: no third-party plugin ecosystem
Mobile appNoNoYesBestYesPartNoPartNohonest gap: no mobile client
Comments and discussion threadsNoPartBestBestNoYesPartYesYeshonest gap: no inline comment or discussion
WYSIWYG media embeds and widgetsNoPartYesBestYesBestYesNoParthonest gap: no rich media embed authoring
Hosted SaaS multi-tenantNoPartBestBestPartBestPartBestBesthonest gap: self-host only, no hosted offering
Change notifications and subscribeNoPartBestBestPartYesNoYesYeshonest gap: no watch or subscribe on page changes
Migration importersNoPartBestBestPartYesPartPartYeshonest gap: no Confluence or Notion importer
i18n multi-language docsNoPartYesYesPartYesBestNoParthonest gap: no multi-language doc variants
Scale and delivery - quantitative
Knowledge-graph nodes16222 organs100s-1000s entitiespage-treedb-pages1000s notesdoc-pagesdoc-pages10k-100k repos100k+ datasetsnx_eco_graph whole-tree walk (measured); catalog scale varies by org
Graph edges42088catalog-scalen/arelationslink-scalen/an/acall-graphlineage-scaledependency edges, measured whole-tree
Page weight rendered~5 KB zero-JSMB-scale SPAMB SPAMB SPAlocal app100s KB100s KBMB SPAMB SPAstatic HTML, no JS bundle
Doc surfaces unified per object521111122card equals doc plus API plus help plus history plus runnable unit (the keystone)
8 competitors39 axes4 quantitativeNishi Best on 9
Honest verdict. On the STRUCTURE of living documentation the Nishi Atlas leads the field, and on several axes it is alone: the card is documentation AND the runnable unit as one object, so the two can never drift; lineage is walked all the way to the foundational primitives (roots-to-god), not just direct dependencies; every node carries a liar-killed, evidence-capped maturity grade; the store is content-addressed, tamper-evident and cryptographically signed (no link-rot); pages are ~5 KB zero-JS and bit-reproducible on an own-stack with zero third-party dependency; and every card is readable and callable by agents over the live MCP plane, lighting up with real swarm activity. It trails, by design, on authoring UX and collaboration -- no WYSIWYG editor, no real-time co-editing, no comments, no plugin marketplace, no mobile app, no hosted multi-tenant SaaS, no migration importers (11 honest absents): this is a generated sovereign knowledge substrate, not a hand-edited wiki. The two frontier bets no competitor makes -- generative recombination (name an outcome, get a plan by shuffling cards) and autonomous discovery of unproven opportunities from maturity-gap x momentum -- are in flight (F225 / F310 / F208). Next rungs: F224 auto-ingest cadence to kill staleness, the R6 card renderer, then wire recombination + discovery.

Generated by nx_swcompare_sota from knowledge/compare/livingdocs.sota — quantitative axes measured/sourced; researcher-fed (nx_swcompare_research). Zero JS, zero trackers.