generated from coulomb/repo-seed
tegwick
fae3cbde8b
Cross-dive synthesis (research/260614-shard-spectrum-synthesis/) reading the two Nelson conceptual systems, four engines, and three modern tools across each other: a shard family matrix and eleven capability spectra (addressing, content identity, structure, history, native query, translation, attachment mode, operational envelope, access grant, write granularity, content types) — positions anchored at both ends by a real system, federation ops degrading by position. Through-lines: files-canonical/index-derived wins; fine-grained addressing is adoptable; transclusion=clone=embed is one primitive; structure/history federate iff in-text; attach mode is a per-binding choice; Notion proves the platform can enforce no-silent-mutation. Folded into SHARD-WP-0002: T11 reframed around the eleven spectra; T12 page model stretched four ways (prose + typed records + non-Markdown assets + query-defined); T13 adds Notion supplement; T14 rewritten as the three-mode attachment taxonomy (file-store / in-engine-host / external-API); T15 adds lossy-with-fidelity-report; new T16 (addressing, content identity, dimensional/query navigation). UC coverage UC-34-43 -> UC-34-59. Workplan now 16 tasks. No new UCs (synthesis only). 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)