shard-wiki/registry/capabilities/capability.wiki.engine-typed-extensions.md

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

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.wiki.engine-typed-extensions	Wiki Engine with Typed Extensions	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.	shard-wiki	draft	helix_forge	wiki engine typed-extensions feature-activation shard-wiki	discovery availability current target confidence rationale D3 D5 medium Architecture authored (shard-wiki/spec/WikiEngineCoreArchitecture.md): small page-store kernel + typed-extension framework, per-shard activation, engine-as-canonical-mode-shard, and a conflict-mediation realization are explored. Detailed extension SDK/ABI and the API protocol remain (so D3 Explored, not yet D4/D5). current target confidence rationale A0 A4 low Planned. No engine kernel or extensions exist yet; informational/planning reuse only.	completeness reliability level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C0 Absent low scope_vs_intent_and_consumer_expectations engine core and typed-extension mechanism not yet designed in detail replacing other wiki engines or mandating one implementation level confidence basis known_reliability_risks R0 low consumer_quality_signals planning-stage capability	intent includes excludes use_cases 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). 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 replacing or mandating other wiki engines (it is one shard type among many) a single canonical implementation for all wikis shard-wiki UseCaseCatalog UC-08..UC-25 and the full catalog (the engine must cover all)	current_level target_level current_artifacts consumption_modes A0 A4 shard-wiki/workplans/SHARD-WP-0013-wiki-engine-prep.md shard-wiki/spec/WikiEngineCoreArchitecture.md informational	depends_on related_to capability.wiki.adapter-contract capability.wiki.page-model capability.feature-control.evaluate capability.authorization.policy-evaluate	documentation shard-wiki/workplans/SHARD-WP-0013-wiki-engine-prep.md	recommended_for not_recommended_for known_limitations planning a composable, feature-activatable native wiki engine implementation reuse today (planning-stage) architecture authored; extension SDK/ABI + API protocol still to design; not yet built	date dimension from to rationale author 2026-06-15 discovery D2 D3 WikiEngineCoreArchitecture.md authored (kernel + typed-extension framework explored); INTENT amendment ratified. shard-wiki

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

Architecture authored: shard-wiki/spec/WikiEngineCoreArchitecture.md (small kernel + typed-extension framework; engine = canonical-mode shard). INTENT amendment ratified (2026-06-15, decision 84ffdb48). Extension SDK/ABI + API protocol are the next deliverables.

Availability

Planning-stage; informational reuse only.