Runtime Capability Authority ADR: [Module/Capability Name]¶
1. Capability Inventory¶
Governance must always begin with the capability inventory. Separate the Protocol/Standard from the Implementation.
Capability A: The Protocol / Specification¶
- Protocol: [e.g., DUADP Protocol, OSSA Specification]
- Purpose: [What the specification defines]
- Protocol Authority: [e.g., Bluefly Product, Open Standards Body]
Capability B: The Implementation¶
- Implementation: [e.g., Drupal Module, Node CLI]
- Purpose: [How it implements the protocol for a specific runtime]
- Implementation Authority: [e.g., Drupal Contrib, NPM Package]
2. Authority Evaluation Order¶
Evaluate authorities in order, then record the stopping point.
Order of Evaluation: Business Capability → Open Standards → Existing Protocols → Drupal Core → Drupal CMS → Drupal Contrib → Composer Ecosystem → NPM Ecosystem → OSSA → Bluefly Extension → Bluefly Product
Stopped at: [Authoritative layer] Reason: [Why it stops here]
3. Capability Comparison Matrix¶
Split "uses" from "owns". A capability using a core API does not own it.
| Feature / Capability | Current Implementation | Candidate Ecosystem Primitive | Owner | Gap (Delta Taxonomy) |
|---|---|---|---|---|
| [e.g., Async Queue] | [e.g., Drupal Queue API] | [e.g., Drupal Queue API] | [e.g., Drupal Core] | NONE (Uses existing) |
| [e.g., Registry Serialization] | [e.g., Custom JSON] | [e.g., Core JSON:API] | [e.g., Drupal Core] | CONFIG |
| [e.g., Protocol Handler] | [e.g., Custom Logic] | ✗ | [e.g., Bluefly IP] | PRODUCT |
Delta Taxonomy: PRODUCT (keep/evolve IP), EXTENSION (upstream/package), CONFIG (use recipes/core), NONE (adopt ecosystem).
4. Current Assessment¶
- Protocol Authority: [e.g., DUADP Specification (Bluefly Product)]
- Reference Implementation: [e.g., Drupal Contrib]
- Other Planned Implementations: [e.g., CLI, SDKs, NPM]
- Confidence: [HIGH/MEDIUM/LOW]
- Reason: [Explanation of the delta]
5. Enhancement Backlog (The Engineering Plan)¶
What ultimately reduces custom code.
Move to Core / Config (NONE / CONFIG) * [e.g., Queue execution] * [e.g., JSON:API serialization]
Move to Contrib (EXTENSION) * [e.g., ECA integrations] * [e.g., Tool API bindings]
Retain as Product / Upstream NPM (PRODUCT) * [e.g., Federation algorithm, NPM base libraries]
6. Governance Outcome & Evidence Gates¶
Target Outcome: [e.g., Candidate Package / Differentiate]
Evidence Checklist: - [x] Capability inventoried (Protocol vs Implementation) - [x] Authority identified - [x] Remaining delta defined granularly - [ ] Enhancement plan drafted - [ ] Implementation validated - [ ] Receipt