What's missing
get_adcp_capabilities declares boolean flags that gate which scenarios the compliance runner executes — e.g. media_buy.supports_proposals gates media_buy_seller/proposal_finalize. The gating lives inside per-scenario YAMLs as a requires_capability: block:
```yaml
static/compliance/source/protocols/media-buy/scenarios/proposal_finalize.yaml
requires_capability:
path: media_buy.supports_proposals
equals: true
```
Today, an adopter who wants to know "if I set media_buy.supports_proposals: false, what changes about my grading?" has to grep every scenario YAML for requires_capability. There's no index.
Concrete ask
Publish a reverse index — capability flag → scenarios it gates — either:
- as a new section of
compliance-catalog.mdx, or
- as a generated table in
/compliance/{version}/index.json surfaced in docs.
Suggested shape:
| Capability flag |
Default |
When true |
When false |
media_buy.supports_proposals |
unset = true |
runs media_buy_seller/proposal_finalize (graded under sales-guaranteed) |
scenario reports capability_unsupported |
| (others) |
… |
… |
… |
Generation could be as simple as a build script that scans every static/compliance/source/protocols/**/scenarios/*.yaml for requires_capability: and emits the table — keeping it from drifting.
Why this matters
Capability flags are the main lever an adopter has to scope their compliance surface. Right now the surface area of those flags is invisible without source-diving. A reverse index makes the cost/coverage tradeoff legible.
Related
What's missing
get_adcp_capabilitiesdeclares boolean flags that gate which scenarios the compliance runner executes — e.g.media_buy.supports_proposalsgatesmedia_buy_seller/proposal_finalize. The gating lives inside per-scenario YAMLs as arequires_capability:block:```yaml
static/compliance/source/protocols/media-buy/scenarios/proposal_finalize.yaml
requires_capability:
path: media_buy.supports_proposals
equals: true
```
Today, an adopter who wants to know "if I set
media_buy.supports_proposals: false, what changes about my grading?" has to grep every scenario YAML forrequires_capability. There's no index.Concrete ask
Publish a reverse index — capability flag → scenarios it gates — either:
compliance-catalog.mdx, or/compliance/{version}/index.jsonsurfaced in docs.Suggested shape:
truefalsemedia_buy.supports_proposalstruemedia_buy_seller/proposal_finalize(graded undersales-guaranteed)capability_unsupportedGeneration could be as simple as a build script that scans every
static/compliance/source/protocols/**/scenarios/*.yamlforrequires_capability:and emits the table — keeping it from drifting.Why this matters
Capability flags are the main lever an adopter has to scope their compliance surface. Right now the surface area of those flags is invisible without source-diving. A reverse index makes the cost/coverage tradeoff legible.
Related