tegwick c895d33091 spec(SHARD-WP-0005 T8): tenant isolation of derived tier + history scaling
Fixes B-3/C-3. §9.1 structural per-tenant partitioning of the derived tier
(no shared cross-tenant cache; read-time filtering as defence-in-depth;
reconciles I-2+L5 per partition); new invariant I-13. §8.1 history stays
recoverable AND bounded (gc/repack, squash-compaction of churn preserving
recoverable endpoints, per-shard offload, anti-abuse hooks).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 01:41:09 +02:00
2026-05-15 21:23:05 +00: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)
Description
Git based markdown wiki orchestrator
Readme MIT-0 3 MiB
Languages
Python 89.6%
HTML 4.9%
CSS 1.9%
Perl 1.6%
Makefile 1.1%
Other 0.9%