Creation, screening, and marketplace

Lifecycle (plugin manager)

CREATE (SBYTE fee for SIGMA) → SCREENING → pending | approved | rejected
        → slot assignment → audit injection → usage → periodic performance score

Each save may retain version history. Marketplace purchases give the buyer a copy linked to the original listing.

Screening

Typical order:

1. Fast pattern checks for obvious injection or abuse.
2. LLM review (hosted model via OpenRouter-class routing) with a JSON outcome: status, score, reasons, risk flags.
3. Truncation or malformed output → reject.
4. Risk flags in the model output → reject even if status looked “ok.”

Non-SIGMA plugin families (for example some social “voice” plugins) can have extra pattern rules; those do not change SIGMA screening directly.

SBYTE creation fee

For SIGMA-type plugins:

1. Sync the validator’s SBYTE balance.
2. Price from catalog USD base and live SBYTE rate (early-adopter discounts if enabled).
3. On-chain transfer to the treasury; record the payment.
4. Decrement ledger balance off-chain after confirmation.

Creation fees go to treasury, not to other validators.

Marketplace (validators)

• Must be approved and published with a listing price.
• Purchase moves SBYTE with a platform fee; seller receives the remainder; buyer gets a copy of the plugin.
• Often one purchase per plugin type per buyer until they delete their copy—follow in-game errors.

Performance score

An automated scoring job (about daily) can assign a 0–1000 quality score from recent behavior signals. Bands are coarse (poor → excellent). Operators may override scores.

Governance weight bonus

Plugin creators can earn a small extra governance weight (capped) from adoption and quality—blending new plugin metrics with legacy audit stats where they still exist.

Legacy augmentation

Older skill assignment paths may still run a separate augmentation step. Do not mix that telemetry with new plugin usage counts.

Support

Failures in loading plugins, screening, or scoring should surface to operator logs for triage.