generated from coulomb/repo-seed
tegwick
60e1aa661c
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>
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)