generated from coulomb/repo-seed
tegwick
4231daf94f
A second substrate validating the contract beyond plain folders: a git-IS-store shard reading Markdown from a git repo. Keys are tracked *.md paths; read returns a Page whose source_rev is the per-path last-commit sha (so an edit to one page never drifts another); profile is git-IS-store / substrate=git / history=git-native / addressing=path, validated against the §6.5 implication rules. Passes the conformance read path with honest absence of unclaimed verbs. Zero new deps (git CLI via subprocess). No core changes. 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)