shard-wiki/registry/capabilities/capability.wiki.shard-orchestration.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance
capability.wiki.shard-orchestration	Wiki Shard Orchestration	Present a union of pages across heterogeneous wiki-shaped shards while preserving each shard's provenance, capabilities, and history.	shard-wiki	draft	helix_forge	wiki federation orchestration union shard-wiki	discovery availability current target confidence rationale D5 D6 high Grounded in 84 documented use cases and a twice-reviewed whole-system architecture (CoreArchitectureBlueprint) derived from ~23 prior-art systems. current target confidence rationale A2 A5 medium InformationSpace orchestrator (attach -> resolve -> read, chorus on ambiguity) works as a Python source module; network API and incremental union are planned.	completeness reliability level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 Partial medium scope_vs_intent_and_consumer_expectations attach folder shards and read a union page with layered provenance chorus presentation of equivalent-but-divergent pages (union without erasure) incremental union maintenance and equivalence index not yet built write-through federation transports not yet built hosting or replacing the underlying wiki engines level confidence basis known_reliability_risks R1 low consumer_quality_signals early implementation; 64 tests but no production exposure	intent includes excludes assumptions use_cases Let independently stored, differently implemented wikis behave as one coherent, versionable, inspectable information space without homogenizing them. union resolution across shards (identity-keyed) chorus / designated-canonical presentation of equivalent pages lazy replication projection of remote content with freshness implementing a backend wiki engine (see capability.wiki.engine-typed-extensions) silent remote mutation canonical truth lives in shards + a git coordination journal; the union is derived shard-wiki UseCaseCatalog UC-01..UC-07, UC-26..UC-33 (information space, federation, coordination)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A5 shard-wiki/src/shard_wiki/union/ shard-wiki/src/shard_wiki/space.py orchestrator network API source module	depends_on supports capability.wiki.adapter-contract capability.wiki.page-model capability.wiki.coordination-journal capability.wiki.federation-models	documentation tests shard-wiki/spec/CoreArchitectureBlueprint.md shard-wiki/spec/FederationArchitecture.md shard-wiki/tests/test_union.py shard-wiki/tests/test_integration.py	recommended_for not_recommended_for known_limitations composing multiple Markdown/wiki stores into one provenance-preserving view replacing a single wiki engine resolution is recompute-on-read until the incremental tier lands

Wiki Shard Orchestration

shard-wiki's core capability: orchestrate wiki-shaped content across heterogeneous shards as a union of pages, preserving provenance, capabilities, and history per shard. Canonical truth stays at the edges (shards + the git coordination journal); the union is a derived, recomputable view (orchestrator, not engine).

Assessment notes

Discovery

Grounded by UseCaseCatalog.md (84 UCs) and the hardened CoreArchitectureBlueprint.md.

Availability

InformationSpace provides attach/resolve/read today (source module); a network API is the target availability step.