Files

tegwick 67d851be0b history(SHARD-WP-0013 T3): reuse-surface gap proposals + consumptions; derived-views registered

Registered capability.wiki.derived-views in reuse-surface (8 wiki.* total, index 20,
validate ok, pushed d985e68). Tracked contributions note (history/260615-...): proposes
two cross-cutting gaps to reuse-surface (G1 typed-extension-framework, G2
translation-fidelity) and records consumptions (feature-control.evaluate,
authorization.policy-evaluate). Sent to the reuse-surface agent via send_message. Marks T3 done.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-15 22:28:29 +02:00

2.6 KiB

Raw Blame History

reuse-surface contributions — shard-wiki (SHARD-WP-0013 T3)

Date: 2026-06-15 · From: shard-wiki (whynot) · To: reuse-surface (helix_forge) · Tracked list of (A) capabilities shard-wiki registered, (B) gaps shard-wiki proposes the reuse surface add, and (C) capabilities shard-wiki will consume rather than rebuild. Communicated to the reuse-surface agent via state-hub send_message.

A. Registered (T1 + T3) — 8 entries

capability.wiki.{shard-orchestration, adapter-contract, page-model, coordination-journal, overlay, federation-models, engine-typed-extensions, derived-views} — committed in reuse-surface, validate ok (20 entries total).

B. Proposed gaps (cross-cutting; not shard-wiki-internal) → reuse-surface should own/define

G1 — capability.platform.typed-extension-framework (suggested) A reusable pattern: a small core + a stringent typed-extension framework where extensions declare typed contracts, compose, and are activated per context. shard-wiki's wiki engine (capability.wiki.engine-typed-extensions) is one instance, but the pattern is cross-domain (any HelixForge capability platform). Evidence: shard-wiki UseCaseCatalog "Capability structure" layer (core + 10 typed extensions + conflict-mediation map). Suggested owner: helix_forge / reuse-surface. Relation: would generalize capability.wiki.engine-typed-extensions.
G2 — capability.content.translation-fidelity (suggested) Lossless/lossy content translation with an explicit fidelity report (what round-trips cleanly vs degrades, non-mappable elements preserved as provenance). Reusable well beyond wiki (any format-bridging consumer). Evidence: shard-wiki TSD §A.6, UC-42/UC-59.

C. Consumptions (reuse, do not rebuild)

capability.feature-control.evaluate (helix_forge/feature-control) → shard-wiki's per-shard extension/feature activation (the "activate only what you need" mechanism). Already recorded as a relation on capability.wiki.engine-typed-extensions.
capability.authorization.policy-evaluate (flex-auth) → shard-wiki's X-AUTHZ policy decisions. shard-wiki owns the authz model (authz-in-core) but can reuse this evaluation engine rather than building one.
capability.statehub.{progress-log, workstream-coordinate} → already in use for coordination across this work.

Status

Gaps G1/G2 are suggestions to the reuse-surface owner (not unilateral registrations, since they are cross-cutting, not shard-wiki-internal). Consumptions are recorded for the engine architecture (T5) so it reuses rather than reinvents.

2.6 KiB Raw Blame History