Files
shard-wiki/registry/capabilities/capability.wiki.federation-models.md
tegwick b31e9bc337 Add capability registry scaffold and seed entries from reuse-surface
Bootstrap registry/indexes/capabilities.yaml and migrate helix_forge
capability entries owned by this repository for federation publishing.
2026-06-16 01:34:23 +02:00

3.1 KiB

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.federation-models Selectable Federation-Model Taxonomy Federation as a plural, composable coordination axis (fork+journal, VCS-replication+ping, query-time graph-join, feed, activity-streams, engine-mirror) selected per space. shard-wiki draft helix_forge
wiki
federation
taxonomy
composable
shard-wiki
discovery availability
current target confidence rationale
D4 D6 high A six-model taxonomy distilled from a ~23-system synthesis, each model anchored in a real system, with capability prerequisites and per-space/per-shard composition rules.
current target confidence rationale
A0 A4 low Designed and specified (FederationArchitecture T17) but not implemented; informational reuse only today.
completeness reliability
level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C1 Sparse low scope_vs_intent_and_consumer_expectations
the model taxonomy and selection/composition rules are documented
no federation transport is implemented yet
mandating a single federation mechanism
level confidence basis known_reliability_risks
R0 low consumer_quality_signals
design-stage; no runtime evidence
intent includes excludes use_cases
Treat federation as selectable and composable rather than one mechanism, so each space picks fork+journal, VCS-replication, query-join, feed, activity-streams, or engine-mirror.
the six federation models + their capability floors
per-space selection and per-shard composition
imposing one homogeneous federation network
shard-wiki UseCaseCatalog UC-26, UC-31, UC-33, UC-71, UC-72, UC-74, UC-79
current_level target_level current_artifacts consumption_modes
A0 A4
shard-wiki/spec/FederationArchitecture.md (T17)
informational
depends_on
capability.wiki.shard-orchestration
capability.wiki.coordination-journal
documentation
shard-wiki/spec/FederationArchitecture.md
shard-wiki/research/260614-shard-spectrum-synthesis/findings.md
recommended_for not_recommended_for known_limitations
planning a federation strategy that mixes models per source
implementation reuse today (design-stage)
no transport implemented; informational planning reuse only

Selectable Federation-Model Taxonomy

Federation is plural and composable: fork+journal (Federated Wiki), VCS-replication+ping (ikiwiki), query-time graph-join (Wikibase SERVICE), feed aggregation, activity streams (ActivityPub), and engine-mirror (Wiki.js). A space selects a model and composes per shard; the default is fork+journal over git. Design-stage capability — strong for planning reuse.

Assessment notes

Discovery

FederationArchitecture T17, distilled from the shard-spectrum synthesis (v3).

Availability

Specified, not implemented — informational reuse only.