generated from coulomb/repo-seed
c1424e8863c4de668098730159a26fa0180eb2d0
Evaluated modelling a wiki information space as a zzstructure: a page is a cell at the intersection of many co-equal dimensions (namespace tree, created-from genealogy, version, shard, equivalence, links). Recommendation: adopt zzstructure as a navigation/visualization/indexing LENS (a derived dimensional projection over the union), not as the storage substrate — Git and sovereign shards stay canonical, and the many-to-many link graph does not fit the one-neighbour-per-dimension rank rule. Clone <-> transclusion convergence with the Xanadu dive. Added UC-47/48/49; enriched UC-05/22/26/29; dimensional projection layer + genealogy-edges-in-journal logged as architecture for 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)
Languages
Python
89.6%
HTML
4.9%
CSS
1.9%
Perl
1.6%
Makefile
1.1%
Other
0.9%