Validator plugins

Runtime injection

Engine buckets

SIGMA plugin types map to runtime buckets:

Plugin type	Bucket
`SIGMA_SKILL`	Skill-plugin list
`SIGMA_API`	API-plugin list
`SIGMA_SKILL_AND_API`	Both lists

Each entry carries the plugin body (Markdown) plus id, name, and quality signals.

Audit prompt wrapping

During verdict construction the backend builds:

xml

<validator_analysis_plugins>
  …policy preamble…
  <validator_skill_plugin name="…">…body…</validator_skill_plugin>
  <validator_api_plugin name="…">…body…</validator_api_plugin>
</validator_analysis_plugins>

The preamble tells the master model that plugins are extra hypotheses, not a veto.

Submission surface matrix

Submission product type	Skill XML	API XML
`SKILL`	yes	no
`API`	yes	yes
`SKILL_API`	yes	yes

Pure SKILL uploads never receive API-plugin XML—author API plugins for API-shaped work.

Telemetry

The combined-type plugin (SIGMA_SKILL_AND_API) may appear in both lists in memory but usage counters dedupe by plugin id so double-counting does not occur.

Caching

Active plugins are cached briefly per validator (on the order of a minute). After slot changes, expect at most one cache window before audits always see the new layout.

Validators in the game client

Validators manage plugins and slots from the in-game plugin manager (pricing, create, assign, publish). Conflicting surfaces return structured errors the UI can display.

Operators

Operator-facing usage logs record each injection: auditor, submission, round, phase, plugin type, product type, verdict.