Register shard-wiki capabilities (7 wiki.* registry entries)
Some checks failed
ci / validate-registry (push) Has been cancelled

Adds capability.wiki.{shard-orchestration, adapter-contract, page-model,
coordination-journal, overlay, federation-models, engine-typed-extensions}
with honest D/A/C/R maturity vectors, relations, and shard-wiki spec/test
evidence; updates registry/indexes/capabilities.yaml. reuse-surface validate: ok.
Source: shard-wiki SHARD-WP-0013 T1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-06-15 22:10:00 +02:00
parent b8434aafdf
commit a7c813eec8
8 changed files with 806 additions and 1 deletions

View File

@@ -0,0 +1,106 @@
---
id: capability.wiki.engine-typed-extensions
name: Wiki Engine with Typed Extensions
summary: A small-core wiki engine realizing a stringent typed-extension framework that addresses all wiki use cases and lets each shard activate only the features it needs.
owner: shard-wiki
status: draft
domain: helix_forge
tags: [wiki, engine, typed-extensions, feature-activation, shard-wiki]
maturity:
discovery:
current: D2
target: D5
confidence: medium
rationale: >
Bounded by SHARD-WP-0013 (wiki-engine prep): intent, scope, and the reconciliation
(engine as a reference canonical-mode shard backend) are defined; the architecture
(WikiEngineCoreArchitecture.md) and the typed-extension model are pending.
availability:
current: A0
target: A4
confidence: low
rationale: >
Planned. No engine kernel or extensions exist yet; informational/planning reuse only.
external_evidence:
completeness:
level: C0
name: Absent
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations: []
broken_expectations:
- engine core and typed-extension mechanism not yet designed in detail
out_of_scope_expectations:
- replacing other wiki engines or mandating one implementation
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- planning-stage capability
discovery:
intent: >
Provide shard-wiki's reference first-party shard backend: a small core + a stringent
typed-extension framework covering all collected use cases, mediating conflicting
requirements into an integrated whole, with per-shard activation (only what you need).
includes:
- a minimal engine kernel (page lifecycle, storage via the adapter contract, the typing mechanism)
- typed extensions that declare contracts and compose
- per-shard feature activation
excludes:
- replacing or mandating other wiki engines (it is one shard type among many)
- a single canonical implementation for all wikis
use_cases:
- "shard-wiki UseCaseCatalog UC-08..UC-25 and the full catalog (the engine must cover all)"
availability:
current_level: A0
target_level: A4
current_artifacts:
- "shard-wiki/workplans/SHARD-WP-0013-wiki-engine-prep.md"
target_artifacts:
- "shard-wiki/spec/WikiEngineCoreArchitecture.md"
consumption_modes:
- informational
relations:
depends_on:
- capability.wiki.adapter-contract
- capability.wiki.page-model
related_to:
- capability.feature-control.evaluate
- capability.authorization.policy-evaluate
evidence:
documentation:
- "shard-wiki/workplans/SHARD-WP-0013-wiki-engine-prep.md"
consumer_guidance:
recommended_for:
- planning a composable, feature-activatable native wiki engine
not_recommended_for:
- implementation reuse today (planning-stage)
known_limitations:
- architecture pending; gated on a narrow INTENT amendment (SHARD-WP-0013 T4)
---
# Wiki Engine with Typed Extensions
shard-wiki's planned reference first-party shard backend — a *canonical-mode shard* it
implements natively: a small core plus a stringent typed-extension framework addressing all
collected use cases, mediating conflicting requirements into a consistent whole, with per-shard
activation (activate only what you need). It is one shard type among many — not a replacement
for other engines. Per-shard activation is a candidate consumer of
`capability.feature-control.evaluate`.
## Assessment notes
### Discovery
Bounded by SHARD-WP-0013; the architecture (`WikiEngineCoreArchitecture.md`) and typed-extension
model are the next deliverables, gated on a narrow INTENT amendment.
### Availability
Planning-stage; informational reuse only.