generated from coulomb/repo-seed
tegwick
316fdeedc2
Distill the cross-cutting adapter-contract constraints from the four engine deep dives (wiki-engines landscape, XWiki, TWiki, Foswiki) into five concrete design tasks, complementing the federation tasks (T1-T10): - T11 adapter contract: capability model & versioned interface (Foswiki::Store prior art; write-granularity as a capability dimension) - T12 page model: structured/typed payload representation (XObjects, %META%, multi-record, bodiless pages) - T13 history portability: supplement (DB-internal) vs import (open file history) - T14 adapter binding: attach path, engine-hosted vs external, backend-swap - T15 syntax translation & content fidelity (non-Markdown round-trip) Adds an adapter-contract decision-topics table, cross-links T10<->T11 on the shared capability vocabulary, and updates context/acceptance/task-order. Tasks registered in the state hub (workstream 2af4c46d). 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)