coulomb/shard-wiki
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Git based markdown wiki orchestrator
26 commits 1 branch 0 tags 790 KiB
Find a file
tegwick f0be5799aa research: Obsidian deep dive (file-over-app vaults, plugin API, ecosystem-popularity signal); UC-53/54/55/56 
The most INTENT-aligned tool yet and the file-backed counterpart to Roam:
file-over-app vaults (plain .md folders, files canonical, MetadataCache a
derived index), in-file git-diffable addressing/structure (^block-id,
wikilink embeds, YAML frontmatter), and a plugin API (Plugin onload/onunload
over App.vault/metadataCache/workspace) that doubles as an adapter host —
so a vault is dual-attachable (file-store direct or in-app plugin). Mined
the plugin download rankings as demand evidence per the research brief:
#1 is drawings (Excalidraw, non-Markdown content), query-as-DB
(Dataview/Tasks) is top-tier but an add-on, Git is top-7 (bolt-on history),
Remotely Save shows sync-to-anywhere demand. Added UC-53 (attach local
vault w/ live concurrent native editor), UC-54 (query-defined dynamic
page), UC-55 (non-Markdown content types), UC-56 (outbound publish of a
projection); enriched UC-15/28/34/36/40/51/52. Boundary: a vault is one
file-backed candidate shard, not the federation layer and not a file-sync
target.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 12:51:22 +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: Obsidian deep dive (file-over-app vaults, plugin API, ecosystem-popularity signal); UC-53/54/55/56 2026-06-14 12:51:22 +02:00
spec research: Obsidian deep dive (file-over-app vaults, plugin API, ecosystem-popularity signal); UC-53/54/55/56 2026-06-14 12:51:22 +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 spec(SHARD-WP-0002): fold adapter-contract constraints into T11-T15 2026-06-13 23:35:09 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-14 02:15:13 +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: Obsidian deep dive (file-over-app vaults, plugin API, ecosystem-popularity signal); UC-53/54/55/56 2026-06-14 12:51:22 +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)