generated from coulomb/repo-seed
tegwick
54c2bf2ae5
engine/activation.py: ActivationContext (shard/tenant, no authz), pluggable ActivationProvider protocol, StaticProvider standalone default (zero-dep, global flags + per-shard scoping + per-ext config), ActivationResolver (candidate ids -> active set / activation profile), and feature_control_provider() lazy factory (returns None when feature_control_sdk absent -> degrade to static; OpenFeature- shaped when present). Availability only. 6 tests green, coverage held, pyflakes clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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)