Git based markdown wiki orchestrator
Find a file
tegwick 0473c3f043 spec: extract use cases from wiki-engines landscape research (UC-34–UC-37)
Mine the one research dir not yet promoted (260608-wikiengines-overview) into
the catalog. Adds four heterogeneous-backend attachment scenarios the other
research didn't surface:

- UC-34 attach structured/semantic shard without lossy flattening (SMW, XWiki)
- UC-35 attach shard with coarse write granularity (TiddlyWiki single-file)
- UC-36 supply git-addressable history to internal-history engine (Confluence)
- UC-37 attach static export as read-only backup shard (MediaWiki dump)

Adds a `wikiengines` source token + traceability column and a wikiengines
mapping subsection. The scan mostly reinforced existing UCs and the L0→L4
ladder; its main yield is adapter-contract constraints tracked in SHARD-WP-0002.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-13 18:39:30 +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: write up wiki-engines landscape scan; send IAM demand to netkingdom 2026-06-13 18:18:45 +02:00
spec spec: extract use cases from wiki-engines landscape research (UC-34–UC-37) 2026-06-13 18:39:30 +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 chore: State Hub sync for SHARD-WP-0002 workstream and tasks 2026-06-08 14:55:25 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-08 14:55:18 +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 spec: promote federation UCs; add SHARD-WP-0002 architecture workplan 2026-06-08 14:55:13 +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)