generated from coulomb/repo-seed
tegwick
0473c3f043
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>
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 Hub–registered tasks
docs/ stakeholder documentation
wiki/ collaborative knowledge (wiki UI when connected)
issues/ ticket mirrors
history/ archived material (yymmdd-prefixed)