Files

tegwick 25a714efa7 research: Jupyter Notebooks deep dive; UC-84 (SHARD-WP-0004 T3)

.ipynb JSON cells + embedded computed outputs with fragile execution
provenance; derived output stored inside the source. Non-Markdown/lossy;
kernel = capability, default = present snapshot + static render.
Enriches UC-54/55/59/35; links UC-32/83/79. Marks T3 done.

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

2026-06-14 23:08:13 +02:00

3.5 KiB

Raw Blame History

SCOPE

One-Liner

Git-based Markdown wiki orchestrator and federation layer — early-stage scaffold with intent, research, and specification groundwork; domain model not yet implemented.

Mode Of Operation

Close the gap between this file and INTENT.md by exploring the problem space (research/), reviewing inbound demand (demand/), refining specifications (spec/), and implementing through registered workplans (workplans/). Learnings update both SCOPE and INTENT where necessary.

Current Status

Layer	State
Code	Python package scaffold (`src/shard_wiki/`, smoke tests only)
Intent	`INTENT.md` established; authorization-in-core amendments drafted
Research	yawex prior art; c2 origins; federation concepts; wikiengines overview (`research/260608-/`); XWiki/TWiki/Foswiki deep dives (`research/260613-/`); Xanadu + ZigZag + Roam + Obsidian + Notion + Joplin + Logseq + local-first workspaces (Anytype/AFFiNE/AppFlowy) + Trilium + Wiki.js + Federated Wiki + Wikibase + git-forge wikis + TiddlyWiki + ikiwiki + Quip + MojoMojo + Oddmuse + UseModWiki deep dives & shard-spectrum synthesis (`research/260614-*/`)
Demand	NetKingdom integration asks captured, not yet negotiated
Spec	Architecture blueprint drafted; UseCaseCatalog 84 UCs from research; PRD/TSD scaffolds
Work	`SHARD-WP-0001` active (6 tasks); `SHARD-WP-0002` active (16 tasks: T1–T10 federation + T11–T16 adapter contract); `SHARD-WP-0003` done (9 engine dives complete); `SHARD-WP-0004` active (8 computational-knowledge dives: T1 literate programming, T3 Jupyter done)

In Scope (today)

Establishing repository documentation structure and specification groundwork.
Federation design informed by yawex prior art (page resolution, namespaces, derived views, provenance, overlays).
Authorization model design (delegated authentication, core authorization).
Shard adapter contract and wiki page model (to be specified, then implemented).
Git-backed coordination journal for information spaces.
State Hub workplan registration and consistency sync.

Out Of Scope (today)

A standalone wiki engine UI or rendering pipeline.
Authentication, credential storage, or user directory implementation.
Hard-coded editorial, sync, or conflict-resolution policy.
Generic file mirroring independent of wiki-page semantics.
Production deployment, multi-tenant operations, or enterprise IAM rollout.

Boundary Rule

shard-wiki orchestrates wiki-shaped content across heterogeneous shards. It provides mechanisms (federation, projection, overlay, patching, reconciliation); policy (canonical source, conflict preference, access rules) remains explicit and configurable. Identity comes from pluggable providers; authorization decisions live in core.

Current Planning

Design work is tracked in workplans/SHARD-WP-0001-yawex-requirements.md (yawex-derived resolution, namespaces, overlays) and workplans/SHARD-WP-0002-federation-architecture.md (federation architecture, decisions, tradeoffs). Research continues under workplans/SHARD-WP-0003-engine-dives-batch.md (remaining new-insight wiki engines + git-forge wikis + classic engines) and workplans/SHARD-WP-0004-computational-knowledge-systems.md (literate programming, computational notebooks, live-coding REPLs, image-based/moldable environments — the executable/computational page-model thread). Specification outputs land in spec/. Inbound integration asks remain in demand/ until reviewed and promoted into spec or workplans.

3.5 KiB Raw Blame History Unescape Escape