Provenance — API Evangelist capability extension (extension.json)

• What: 322 AE-* capability ids — 16 new L1 domains with L2/L3/L4 children (298 nodes) and 24 nodes (AE-9xx) that attach under an existing Turbo EA node by extends: BC-… — plus 81 overlays that annotate existing BC-* nodes with an audience (consumer, b2b, enterprise, agent).
• Who / when: API Evangelist (Kin Lane). Drafted 2026-10-25/26 in planning/capability-extension/ (five passes); approved for production by Kin 2026-10-26. IDs are frozen in planning/capability-extension/draft/id-ledger.json; a retired id is never reused.
• Licence: CC BY-NC-SA 4.0 (house rule: artifacts CC BY-NC-SA, code Apache 2.0). Attribution: API Evangelist capability extension — https://apievangelist.com. See LICENSE-EXTENSION.md for how it coexists with the Turbo EA model.
• Evidence: every AE node carries evidence — catalog-tags (exact catalog tags with provider counts, from api-search/providers/_data/provider_bands.yml) and/or blueprint-gap (a capability the application-blueprint pilot could not place).
• Relationship to upstream: model.json in this directory (Turbo EA Capabilities by Vincent Verdet, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0) is an exact vendored copy and is never modified. This file contains BC ids and names only as references (extends, extends_name, overlays[].bc_id/bc_name). An extends node is API Evangelist work even where it renders under a BC parent. An overlay’s audience and note are API Evangelist annotations, not Turbo EA content, and are displayed as such.
• Loaded by: planning/capability-mapping/scripts/lib_capabilities.py (provenance(id) returns the attribution by id prefix) and network/scripts/build_business_capabilities.py.

How the two licences coexist

1. Separate files. The upstream file stays an exact vendored copy. Nothing in the extension is written into it, and nothing is renamed, re-parented or edited there.
2. No upstream content copied. The extension contains BC ids and BC names only as references (extends, extends_name, overlays[].bc_id/bc_name) — identifiers needed to point at a node, not descriptions or structure. All AE names and descriptions are our own text.
3. Attribution per node by ID prefix. The loader returns Turbo EA attribution for BC-* and API Evangelist attribution for AE-*. An extends node is ours even though it renders under a BC parent. An overlay’s audience and note are ours and must be shown as an API Evangelist annotation on the BC page, not as Turbo EA content.
4. Combined views. A page that shows both (e.g. a BC L1 with an AE child) credits both, each next to its own nodes. CC BY 4.0 permits this; the NC-SA terms apply only to the AE nodes and annotations. We do not relicense Turbo EA content, and the merged view as a whole is not offered under CC BY 4.0.
5. Share-alike scope. Anyone adapting the AE nodes must keep them CC BY-NC-SA; anyone using only BC nodes is under CC BY 4.0 alone.