coulomb/shard-wiki
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
shard-wiki/spec
History
tegwick cdcf4b09aa adr: ADR-0001 engine activation via feature-control (OpenFeature, availability-only) 
Records the accepted decision: shard-wiki's native engine uses feature-control via
OpenFeature for per-shard extension activation (availability only, never authz),
provider-pluggable with a LocalProvider standalone default (mirrors the identity
ladder), at the engine layer, consuming the mature feature-control.evaluate slice.
Adds spec/adr/ series + README; hub decision abf7830f recorded.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 23:48:49 +02:00
..
adr adr: ADR-0001 engine activation via feature-control (OpenFeature, availability-only) 2026-06-15 23:48:49 +02:00
ArchitectureBlueprint.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
CoreArchitectureBlueprint.md spec(SHARD-WP-0013 T6): wire-up + close-out 2026-06-15 23:02:15 +02:00
FederationArchitecture.md spec(SHARD-WP-0002): FederationArchitecture.md — federation design (T1-T10, T17) 2026-06-15 02:24:11 +02:00
FederationRequirements.md spec(SHARD-WP-0001): yawex-derived federation requirements (ADR-01..06); workplan done 2026-06-15 02:19:43 +02:00
ProductRequirementsDocument.md spec: promote federation UCs; add SHARD-WP-0002 architecture workplan 2026-06-08 14:55:13 +02:00
README.md adr: ADR-0001 engine activation via feature-control (OpenFeature, availability-only) 2026-06-15 23:48:49 +02:00
TechnicalSpecificationDocument.md spec(SHARD-WP-0002): adapter contract (TSD §A, T11-T16+T18); workplan done 2026-06-15 02:25:50 +02:00
UseCaseCatalog.md spec(SHARD-WP-0013 T2): engine-facing capability structure layer over the UC catalog 2026-06-15 22:16:06 +02:00
WikiEngineCoreArchitecture.md spec(SHARD-WP-0013 T5): WikiEngineCoreArchitecture.md — small core + typed extensions 2026-06-15 22:54:40 +02:00

README.md

spec/

Specification files that guide and guardrail implementation.

Background on document types: InfoTechPrimers on coulomb.social.

File Status Role
CoreArchitectureBlueprint.md draft for review Whole-system architecture — layers, abstractions, load-bearing decisions (synthesised from all research)
FederationArchitecture.md draft for review federation design — what the union does: T1–T10 decision records + the federation-model taxonomy (SHARD-WP-0002)
WikiEngineCoreArchitecture.md draft for review the native headless, API-first wiki engine — small page-store kernel + typed-extension framework, as a canonical-mode shard backend (SHARD-WP-0013)
adr/ living Architecture Decision Records (ADR-0001: engine activation via feature-control)
FederationRequirements.md draft for review yawex-derived union/federation design notes — resolution, namespace, derived views, provenance, overlay, links (ADR-01…06; SHARD-WP-0001)
ProductRequirementsDocument.md draft scaffold What the product must deliver
TechnicalSpecificationDocument.md draft + §A How the system is built; §A = the normative shard adapter contract (T11–T16, T18; SHARD-WP-0002)
UseCaseCatalog.md draft 84 use cases promoted from c2 + yawex + ~23-system research
ArchitectureBlueprint.md draft Access, history, and identity sub-blueprint (the L0–L4 authorization ladder; referenced by CoreArchitectureBlueprint §9)

Promote material from research/ and reviewed items from demand/ into spec before treating it as implementation authority.