synthesis v2: extend shard spectrum to full dive set (13 spectra); re-fold into SHARD-WP-0002

Extend the cross-dive synthesis from nine systems to the full fourteen
(added Joplin, Logseq, the CRDT cohort Anytype/AFFiNE/AppFlowy, Trilium).
Spectra grown 11 -> 13: new merge-model (none/git/conflict-notes/
native-CRDT) and content-opacity (plaintext/whole-shard-E2EE/per-item),
plus identity-vs-placement emphasis (Trilium note/branch DAG), Logseq's
in-file id:: addressing sweet spot, build-your-own derived query index,
and a six-mode attachment taxonomy (file-store native/interchange-mirror,
in-engine-host, local-REST, external-API, CRDT-replica, P2P). New
through-lines: CRDT changes the merge math; identity != placement;
metadata can be computed; attach surface != native store (+ substrate
migration). UC fold-in extended UC-44-59 -> UC-44-67.

Folded into SHARD-WP-0002: T11 thirteen spectra; T12 computed metadata +
multi-placement/DAG identity; T13 CRDT-log supplement; T14 full six-mode
attachment taxonomy; T15 HTML source model; T16 identity!=placement +
derived index. Context inputs += four dives; acceptance UC-26-67. No new
tasks, no new UCs (synthesis only).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

research/260614-shard-spectrum-synthesis/README.md

@@ -1,47 +1,55 @@
-# 260614 — Shard spectrum synthesis (one capability model across nine systems)
+# 260614 — Shard spectrum synthesis (one capability model across the full dive set)
 
-Date: 2026-06-14
+Date: 2026-06-14 · **revised 2026-06-14 (v2)**
 
 ## What this is
 
-A **synthesis** (no new external research) that reads the nine studied systems *across*
-each other and distills them into a single comparative model feeding the **shard adapter
+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** (`SHARD-WP-0002`).
 
-The nine: two conceptual ancestors (**Xanadu**, **ZigZag**), four engines (**XWiki,
-TWiki, Foswiki** + the wiki-engines landscape), and three modern tools (**Roam,
-Obsidian, Notion**), against the federation/origin research.
+**v2** extends from nine systems to the full set and grows the spectra from eleven to
+**thirteen**. The systems: two conceptual ancestors (**Xanadu, ZigZag**), four engines
+(**XWiki, TWiki, Foswiki** + the wiki-engines landscape), and the modern note/PKB tools
+(**Roam, Obsidian, Notion, Joplin, Logseq, Anytype, AFFiNE, AppFlowy, Trilium**), against
+the federation/origin research.
 
 Centerpieces:
-- **The shard family matrix** — every candidate backend × {substrate, attach mode,
-  addressing, structure, history, query, transclusion, →Markdown, write granularity},
-  with Xanadu/ZigZag as the ideal anchors.
-- **The eleven capability spectra** — the claim that the adapter contract should model
-  *positions on spectra* (addressing, content identity, structure, history, query,
-  translation, attachment mode, operational envelope, access grant, write granularity,
-  content types), each anchored at both ends by a real system, with federation ops
-  degrading by position.
-- **UC-44–UC-59 → workplan task mapping**, including one genuinely new thread (T16:
-  addressing, content identity, dimensional/query navigation).
+- **The shard family matrix** — every candidate backend × {substrate, attach mode(s),
+  addressing, structure, history, **merge**, query, →Markdown, **opacity**}, with Xanadu/
+  ZigZag as the ideal anchors.
+- **The thirteen 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. v2 adds **content opacity** (12th) and **merge model**
+  (13th), plus emphasis on **identity vs placement**, and expands the attachment-mode
+  spectrum (file-store native/interchange-mirror, in-engine-host, local-REST,
+  external-API, CRDT-replica, P2P/no-central-endpoint).
+- **UC-44–UC-67 → workplan task mapping** (T11–T16).
 
 ## Contents
 
 | Path | Role |
 |------|------|
-| `findings.md` | Family matrix, the eleven spectra, cross-cutting through-lines, UC→task fold-in, recommendations/decisions, escalated open questions |
+| `findings.md` | Family matrix, the thirteen spectra, cross-cutting through-lines, UC→task fold-in, recommendations/decisions, escalated open questions |
 
 ## Status
 
-Synthesis complete. No new use cases (consolidation only). Feeds `SHARD-WP-0002`: T11
-reframed around the eleven spectra; T12 page-model breadth (prose + typed records +
-non-Markdown assets + query-defined); T13 history confirmed; T14 three-mode attachment
-taxonomy; T15 lossy-with-fidelity-report; **new T16** (addressing, content identity,
-dimensional/query navigation). UC coverage in the workplan extended UC-34–UC-43 →
-UC-34–UC-59.
+Synthesis v2 complete. No new use cases (consolidation only). Feeds `SHARD-WP-0002`: T11
+reframed around the **thirteen spectra** (incl. content-opacity + merge-model); T12
+page-model breadth (prose + typed/**computed** records + non-Markdown assets +
+query-defined + **multi-placement/DAG identity**); T13 history (incl. CRDT-log =
+supplement); T14 **full attachment-mode taxonomy** (CRDT-replica + P2P + interchange-mirror
++ local-REST added); T15 lossy-with-fidelity-report (incl. HTML); T16 (addressing, content
+identity, **identity≠placement**, derived index, dimensional/query). UC coverage extended
+UC-34–UC-59 → **UC-34–UC-67**.
 
-**Through-lines recorded:** files-canonical/index-derived is the winning architecture;
-fine-grained addressing is real and adoptable (adopt native, fingerprint otherwise);
-transclusion ⇄ clone ⇄ embed is one primitive; structure/history federate iff in text;
-attach mode is a per-binding capability-gated choice; Notion proves the platform can
-*enforce* no-silent-mutation via scoped grants.
+**New through-lines (v2):** CRDT changes the merge math (native merge — never impose git
+merge); identity ≠ placement (Trilium note/branch) is the model for multi-location/
+multi-shard pages; metadata can be computed (inherited/templated), not just stored;
+content opacity is per-item, not only whole-shard; the attach surface is not always the
+native store (Joplin sync mirror; Logseq file-vs-DB and its substrate migration); the
+block-graph-on-files sweet spot (Logseq `id::`) resolves the addressing tension.
+**Carried from v1:** files-canonical/index-derived; fine-grained addressing is adoptable;
+transclusion=clone=embed is one primitive; structure/history federate iff in-text; attach
+mode is per-binding; Notion proves the platform can enforce no-silent-mutation.
 </content>