generated from coulomb/repo-seed
tegwick
ec7a1ec946
reuse-surface = capability registry at /home/worsch/reuse-surface (helix_forge): Markdown entries via templates/capability-entry.template.md, D/A/C/R maturity vectors, reuse-surface CLI (validate/query/export/overlaps), hub at reuse.coulomb.social. T1 now registers shard-wiki's capabilities as registry entries; T3 contributes gaps back via REUSE-WP/agent message; T5 evaluates reusing sibling feature-control for per-shard activation. 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)