# 260614 — Shard spectrum synthesis (one capability model across the full dive set)

Date: 2026-06-14 · **revised 2026-06-14 (v3)**

## What this is

A **synthesis** (no new external research) that reads every studied system *across* the
others and distills them into a single comparative model feeding the **shard adapter
contract** and the **federation track** (`SHARD-WP-0002`).

**v3** extends the model to the **SHARD-WP-0003 engine batch** (Federated Wiki, Wikibase/
Wikidata, the git-forge wikis Gitea/GitLab/GitHub, TiddlyWiki, ikiwiki, Salesforce Quip,
MojoMojo, Oddmuse, UseModWiki) — ~23 systems in all. Per-shard spectra grow from thirteen to
**fourteen** (adds **provenance granularity**), and a **new coordination-layer axis** is
introduced: the **federation-model taxonomy**.

Centerpieces:
- **The shard family matrix** — every candidate backend × {substrate, attach mode(s),
  addressing, structure, history, merge, query, →Markdown, opacity}, with Xanadu/ZigZag as
  ideal anchors and Federated Wiki as the federation-model anchor. v3 adds the flat-file
  floor (Oddmuse/UseModWiki), git-IS-store (forge wikis/ikiwiki), TiddlyWiki, MojoMojo
  (direct-DB), Quip (external-API/HTML), and Wikibase (typed-graph far-end).
- **The fourteen capability spectra** — the claim that the adapter contract should model
  *positions on spectra*, each anchored at both ends by a real system, with federation ops
  degrading by position. v3 adds **provenance granularity** (14th: per-shard → per-page →
  per-edit → per-statement/value), and refines merge-model (+fork/journal-replay,
  +coexist-with-rank), attachment-mode (+git-IS-store, +container, +direct-DB,
  +REST/file-store-hybrid, +external-API payload-format facet), native-query (+SPARQL/RDF
  far-end, +filter mid), history (+DB-version-rows, +partial/truncated), structure
  (+typed-graph, +inline-embedded objects), content-opacity (+proprietary-lossy-exportable),
  write-granularity (+story-item, +section-anchor).
- **The federation-model taxonomy (§2.5, new)** — federation itself is plural: fork+journal
  (Federated Wiki), VCS-replication+ping (ikiwiki), query-time graph join (Wikibase SPARQL
  `SERVICE`), feed aggregation, activity streams, engine-mirror (Wiki.js). A
  selectable/composable coordination-layer axis feeding **T1–T6**.
- **UC-44–UC-82 → workplan task mapping** (T1–T6 + T11–T16).

## Contents

| Path | Role |
|------|------|
| `findings.md` | Family matrix, the fourteen spectra, the federation-model taxonomy, cross-cutting through-lines, UC→task fold-in, recommendations/decisions, escalated open questions |

## Status

Synthesis v3 complete. No new use cases (consolidation only). Feeds `SHARD-WP-0002`:
**T1–T6** federation-model taxonomy (selectable/composable federation); **T11** reframed
around the **fourteen spectra** (incl. provenance granularity + expanded attachment modes +
external-API payload-format facet); T12 page-model breadth (prose + typed/computed records +
**inline-embedded objects** + **typed-graph statements** + non-Markdown assets +
query-defined + multi-placement/DAG identity); T13 history (DB-rows + partial-flat-file =
supplement; completeness metadata; **journal-shaped** coordination journal); T14 **full
attachment taxonomy** (git-IS-store / container / direct-DB / REST-file-hybrid +
source-of-truth per binding); T15 lossy + **not-Markdown** (graph/HTML); T16 (addressing
incl. statement GUID + **opaque stable identity**, identity≠placement, derived index,
**graph query / federated SERVICE**). UC coverage extended UC-34–UC-67 → **UC-34–UC-82**.

**New through-lines (v3):** federation is plural (the federation-model taxonomy); provenance
has a granularity spectrum (down to per-statement, Wikibase rank/references); git is both the
home store and the home journal (forge wikis make git *the* store, resolving the engine-
mirror write-race); the flat-file floor (Oddmuse/UseModWiki, Wikipedia's MediaWiki Phase I)
is the field's common root and the minimal capability profile; the page model must also carry
typed-graph statements and inline-embedded objects.
**Carried from v2:** CRDT changes the merge math; identity ≠ placement; metadata can be
computed; content opacity is per-item; the attach surface is not always the native store; the
block-graph-on-files sweet spot (Logseq `id::`).
**Carried from v1:** files-canonical/index-derived; fine-grained addressing is adoptable;
transclusion=clone=embed=reference is one primitive; structure/history federate iff in-text;
attach mode is per-binding; the platform can enforce no-silent-mutation.