coulomb/shard-wiki
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
shard-wiki/research/README.md

22 lines
1.4 KiB
Markdown
Raw Normal View History

Reorganize documentation into canonical repository layout Adopt CoulombSocial/HelixForge/MarkiTect documentation structure: - research/260608-yawex-prior-art/ — yawex exploration and sources - demand/ — inbound NetKingdom integration requirements - spec/ — PRD, TSD, UseCaseCatalog, ArchitectureBlueprint scaffolds - docs/ — stakeholder documentation and repository-layout guide - wiki/, issues/, history/ — scaffolded directories Add SCOPE.md and AGENTS.md. Update workplan paths and README.
2026-06-08 13:55:27 +02:00
# research/
Exploration results for the problem and solution space.
Each exploration uses a `yymmdd-` prefix on the markdown file or subdirectory
when multiple files or sources are involved. Findings here inform `spec/` and
`SCOPE.md`; they do not directly authorize implementation until promoted.
## Active Explorations
| Date | Path | Summary |
|------|------|---------|
Add c2 wiki origins research (Ward Cunningham, terms, use cases) Explores WikiWikiWeb beginnings: design principles, social conventions, navigation vocabulary, and documented use cases. Federation explicitly deferred to a later research track.
2026-06-08 14:05:59 +02:00
| 2026-06-08 | `260608-yawex-prior-art/` | yawex 0.7.4 Perl wiki prior art; federation design seeds |
research: federation concepts for unified information spaces Document Federated Wiki mechanics (fork, journal, inverted browser model), Caulfield lifecycle concepts, and comparison with git-backed wikis, ActivityPub/XWiki, Xanadu patterns, and yawex REMOTE/VIRTUAL. Map findings to shard-wiki INTENT without equating fedwiki to orchestration.
2026-06-08 14:43:13 +02:00
| 2026-06-08 | `260608-c2-wiki-origins/` | Ward Cunningham & WikiWikiWeb origins; terms and use cases |
| 2026-06-08 | `260608-federation-concepts/` | Federated Wiki, git/ActivityPub/Xanadu federation models |
research: Project Xanadu deep dive (EDL/reference-not-copy, transclusion, addressing); UC-44/45/46 Xanadu studied as conceptual ancestor, not a candidate shard. Yield: reference-not-copy EDL/xanadoc validates projection+overlay+union; content-identity bidirectional transclusion; portable span-address (tumbler) problem logged as adapter-contract architecture for SHARD-WP-0002. Recorded design-bug boundaries: reject single-global-docuverse, single-canonical-instance, baked-in economic policy. Added UC-44/45/46; enriched UC-24/27/29/32. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 01:24:45 +02:00
| 2026-06-08 | `260608-wikiengines-overview/` | Wiki engine landscape survey (Perplexity-assisted) |
| 2026-06-13 | `260613-xwiki-deep-dive/` | XWiki impl, extension interfaces, ecosystem; UC-38/39 |
| 2026-06-13 | `260613-twiki-deep-dive/` | TWiki impl, plugin API, ecosystem; UC-40/41 |
| 2026-06-13 | `260613-foswiki-deep-dive/` | Foswiki store abstraction, extension API; UC-42/43 |
research: ZigZag/zzstructure deep dive (information space as orthogonal dimensions); UC-47/48/49 Evaluated modelling a wiki information space as a zzstructure: a page is a cell at the intersection of many co-equal dimensions (namespace tree, created-from genealogy, version, shard, equivalence, links). Recommendation: adopt zzstructure as a navigation/visualization/indexing LENS (a derived dimensional projection over the union), not as the storage substrate — Git and sovereign shards stay canonical, and the many-to-many link graph does not fit the one-neighbour-per-dimension rank rule. Clone <-> transclusion convergence with the Xanadu dive. Added UC-47/48/49; enriched UC-05/22/26/29; dimensional projection layer + genealogy-edges-in-journal logged as architecture for SHARD-WP-0002. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 02:14:04 +02:00
| 2026-06-14 | `260614-xanadu-deep-dive/` | Project Xanadu — EDL/reference-not-copy, transclusion, addressing; UC-44/45/46 |
research: Roam Research deep dive (block-graph DataScript DB, transclusion, datalog, Roam Depot extension API); UC-50/51/52 The modern bookend to the Xanadu/ZigZag dives: where those are unbuilt ideals, Roam shipped fine-grained addressing (:block/uid), live transclusion (block embeds), bidirectional links, and a queryable structured space (DataScript datoms + Datalog). Studied as a candidate DB-backed/API-attached shard (XWiki family) and as a concrete engine-hosts-adapter surface (Roam Depot onload/onunload over window.roamAlphaAPI). Added UC-50 (attach block-graph DB shard, block<->page mapping), UC-51 (adopt native span IDs as portable span addresses), UC-52 (delegate derived views to a shard's native query engine); enriched UC-32/34/35/38. Boundary: Roam is one candidate shard mapped into the Markdown-first page model, not a substrate and not the federation layer. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 11:36:50 +02:00
| 2026-06-14 | `260614-zigzag-deep-dive/` | ZigZag/zzstructure — information space as orthogonal dimensions; UC-47/48/49 |
| 2026-06-14 | `260614-roam-deep-dive/` | Roam Research — block-graph DataScript DB, transclusion, datalog, Roam Depot extension API; UC-50/51/52 |
Reference in a new issue Copy permalink