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>
This commit is contained in:
2026-06-15 23:48:49 +02:00
parent b21efe307b
commit cdcf4b09aa
3 changed files with 91 additions and 0 deletions

11
spec/adr/README.md Normal file
View File

@@ -0,0 +1,11 @@
# spec/adr/ — Architecture Decision Records
Repository-level ADRs: one decision per file, `ADR-NNNN-<slug>.md`, status
**Proposed / Accepted / Superseded**. Each records Context · Decision · Consequences ·
Alternatives. These are the standalone, numbered decision log; design-note "ADRs" embedded
inside a spec (e.g. `FederationRequirements.md` ADR-01…06) are scoped to that document and are
not part of this series.
| ADR | Status | Subject |
|-----|--------|---------|
| [ADR-0001](ADR-0001-engine-activation-via-feature-control.md) | Accepted | Engine extension activation via feature-control (OpenFeature), availability-only, LocalProvider standalone default |