Git based markdown wiki orchestrator
Find a file
tegwick 9b5defa6d8 plan: add SHARD-WP-0003 (engine-dive batch) and SHARD-WP-0004 (computational-knowledge systems)
SHARD-WP-0003 — nine wiki-engine deep dives chosen against the synthesis
coverage review: high-insight (Federated Wiki, Wikibase/Wikidata,
TiddlyWiki, ikiwiki), the INTENT-named git-forge wikis (Gitea/GitLab/
GitHub), and four for breadth/lineage (Salesforce Quip, Oddmuse, MojoMojo,
UseModWiki). Each task = persist a deep-dive memo + promote/enrich the
use-case catalog + log adapter-contract notes for SHARD-WP-0002;
post-batch synthesis-v3 decision.

SHARD-WP-0004 — eight computational / interactive-knowledge systems as
design prior art for executable/computational/live page content and
one-source-many-projections: Knuth WEB/weave/tangle, Mathematica & Jupyter
notebooks, Processing/Processing.js, Strudel.cc, Squeak, Glamorous
Toolkit, Pharo. Carries the question of whether a page can be a live
computational artifact; closes with a "computational page model"
synthesis. Both workplans authored file-authoritative (no state_hub IDs;
sync will create+link workstreams and tasks).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 18:28:06 +02:00
demand research: write up wiki-engines landscape scan; send IAM demand to netkingdom 2026-06-13 18:18:45 +02:00
docs Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
history Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
issues Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
research research: Wiki.js deep dive (storage-module engine, DB<->Git Markdown, GraphQL); UC-68/69 2026-06-14 17:50:27 +02:00
spec research: Wiki.js deep dive (storage-module engine, DB<->Git Markdown, GraphQL); UC-68/69 2026-06-14 17:50:27 +02:00
src/shard_wiki Scaffold Python project with pyproject.toml and pytest 2026-06-08 01:05:40 +02:00
tests Scaffold Python project with pyproject.toml and pytest 2026-06-08 01:05:40 +02:00
wiki Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
workplans plan: add SHARD-WP-0003 (engine-dive batch) and SHARD-WP-0004 (computational-knowledge systems) 2026-06-14 18:28:06 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-14 14:02:06 +02:00
.gitignore Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
AGENTS.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
CLAUDE.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
INTENT.md Establish clean starting point: workplan, access model, INTENT amendments 2026-06-08 12:23:54 +02:00
LICENSE Initial commit 2026-05-15 21:23:05 +00:00
pyproject.toml Scaffold Python project with pyproject.toml and pytest 2026-06-08 01:05:40 +02:00
README.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
SCOPE.md plan: add SHARD-WP-0003 (engine-dive batch) and SHARD-WP-0004 (computational-knowledge systems) 2026-06-14 18:28:06 +02:00

shard-wiki

Git-based Markdown wiki orchestrator and federation layer.

shard-wiki joins heterogeneous wiki-shaped page stores (shards) into a coherent information space while preserving provenance, capabilities, and history. It is an orchestration layer, not a wiki engine.

Status

Early-stage: Python scaffold, intent and specification groundwork, active design workplan. See SCOPE.md for current maturity.

Documentation

Document Purpose
INTENT.md Aspiration and boundaries
SCOPE.md What we achieve now
AGENTS.md Agent working guide
docs/repository-layout.md How this repo organizes information

Quick start

pip install -e ".[dev]"
pytest

Layout

research/     explorations (yymmdd-prefixed)
demand/       inbound unreviewed requirements
spec/         implementation specifications
workplans/    State Hubregistered tasks
docs/         stakeholder documentation
wiki/         collaborative knowledge (wiki UI when connected)
issues/       ticket mirrors
history/      archived material (yymmdd-prefixed)