Git based markdown wiki orchestrator
Find a file
tegwick b9bb1f7d10 feat(engine): capability profile derived from active extensions (WP-0014 T4, E-5)
engine/profile.py: engine_base_profile() (kernel-only c2-minimum profile),
ProfileContribution (an extension's ON_PROFILE contribution: axis raises + verbs),
derive_profile() folds active extensions' contributions onto the base in deterministic
order then validate() — so configuration->capability is one chain and composition can
never yield an impossible profile (encrypted+native-query rejected). 5 tests green,
96 total, pyflakes clean. Marks T4 done.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-16 00:27:11 +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(SHARD-WP-0013 T3): reuse-surface gap proposals + consumptions; derived-views registered 2026-06-15 22:28:29 +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 adr: ADR-0001 engine activation via feature-control (OpenFeature, availability-only) 2026-06-15 23:48:49 +02:00
src/shard_wiki feat(engine): capability profile derived from active extensions (WP-0014 T4, E-5) 2026-06-16 00:27:11 +02:00
tests feat(engine): capability profile derived from active extensions (WP-0014 T4, E-5) 2026-06-16 00:27:11 +02:00
wiki Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
workplans feat(engine): capability profile derived from active extensions (WP-0014 T4, E-5) 2026-06-16 00:27:11 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-16 00:16:54 +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 intent(SHARD-WP-0013 T4): ratify additive native engine — headless, API-first, agent-optimized 2026-06-15 22:43:46 +02:00
LICENSE Initial commit 2026-05-15 21:23:05 +00:00
pyproject.toml test: harden suite with error-path contracts + coverage floor (98%) 2026-06-16 00:05:16 +02:00
README.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
SCOPE.md spec(SHARD-WP-0013 T6): wire-up + close-out 2026-06-15 23:02:15 +02:00

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 Hubregistered tasks
docs/         stakeholder documentation
wiki/         collaborative knowledge (wiki UI when connected)
issues/       ticket mirrors
history/      archived material (yymmdd-prefixed)