coulomb/shard-wiki
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Git based markdown wiki orchestrator
135 commits 1 branch 0 tags 790 KiB
Find a file
tegwick 46ec6f2a5f spec(SHARD-WP-0013 T2): engine-facing capability structure layer over the UC catalog 
Adds 'Capability structure for the wiki engine (reuse-surface-aligned)' to
UseCaseCatalog.md (no UC renumbered): a small always-on engine core (EC-1..EC-5),
ten typed per-shard-activatable extensions (X-OVERLAY/AUTHZ/VIEW/STRUCT/ADDR/COMP/
PROV/COLLAB/FED/ATT) each mapped to a reuse-surface capability with activation
defaults, and a conflict-mediation map turning conflicting requirements into
mechanisms. Bridges demand -> the engine typed-extension model (T5). Marks T2 done.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 22:16:06 +02:00
demand research: write up wiki-engines landscape scan; send IAM demand to netkingdom 2026-06-13 18:18:45 +02:00
docs Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
history history+workplan: round-2 blueprint review; SHARD-WP-0006 hardening II 2026-06-15 01:56:42 +02:00
issues Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
research research: SHARD-WP-0004 synthesis (the computational page model); workplan done 2026-06-15 00:12:03 +02:00
spec spec(SHARD-WP-0013 T2): engine-facing capability structure layer over the UC catalog 2026-06-15 22:16:06 +02:00
src/shard_wiki feat(space): wire write path into InformationSpace; integration (WP-0008 T6) 2026-06-15 13:46:32 +02:00
tests feat(space): wire write path into InformationSpace; integration (WP-0008 T6) 2026-06-15 13:46:32 +02:00
wiki Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
workplans spec(SHARD-WP-0013 T2): engine-facing capability structure layer over the UC catalog 2026-06-15 22:16:06 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-15 22:11:16 +02:00
.gitignore Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
AGENTS.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
CLAUDE.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
INTENT.md Establish clean starting point: workplan, access model, INTENT amendments 2026-06-08 12:23:54 +02:00
LICENSE Initial commit 2026-05-15 21:23:05 +00:00
pyproject.toml Scaffold Python project with pyproject.toml and pytest 2026-06-08 01:05:40 +02:00
README.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
SCOPE.md feat(space): wire write path into InformationSpace; integration (WP-0008 T6) 2026-06-15 13:46:32 +02:00

README.md

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)