generated from coulomb/repo-seed
tegwick
2397c2c4b3
Section A had accumulated 64 of 82 UCs (every dive appended to its end), collapsing four distinct themes into one heading. Regroup the orchestration/ adapter UCs into four coherent sections and re-letter the authoring/reading sections, with UC numbers kept as stable IDs (never renumbered -- they are referenced across research/, the synthesis, and the workplans): A. Information space, federation & coordination B. Shard attachment & adapter binding C. Page model, structure & content fidelity D. Addressing, identity & query E. Knowledge work and collaboration (was B) F. Discovery and navigation (was C) G. Provenance and page metadata (was D; + UC-75 statement provenance) UC blocks moved byte-for-byte (verified: heading set and Traceability tail identical to pre-restructure); added an Organization note to Conventions. 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)