Git based markdown wiki orchestrator
Find a file
tegwick dbc42f05db research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77
SHARD-WP-0003 T5. The home case: a forge wiki is a separate .wiki.git repo of
Markdown -> page model, history, coordination journal map 1:1 with near-zero
adapter. git-clone universal across all three; wiki content API
capability-varying (GitLab/Gitea yes, GitHub git-only). git IS the canonical
store (not a mirror), so write-by-commit is safe -- resolves the UC-68/Q22
race for this case. UC-76 (clone .wiki.git attach), UC-77 (forge wiki API,
capability varies). Enriched UC-40/02/68/38. Marks T5 done.
Feeds SHARD-WP-0002 T14/T11.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 19:40:46 +02:00
.claude research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77 2026-06-14 19:40:46 +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 Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
issues Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
research research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77 2026-06-14 19:40:46 +02:00
spec research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77 2026-06-14 19:40:46 +02:00
src/shard_wiki Scaffold Python project with pyproject.toml and pytest 2026-06-08 01:05:40 +02:00
tests Scaffold Python project with pyproject.toml and pytest 2026-06-08 01:05:40 +02:00
wiki Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
workplans research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77 2026-06-14 19:40:46 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-14 19:31:46 +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 research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77 2026-06-14 19:40:46 +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)