Publishing Guide

Ship rules people can trust: clear intent, safe defaults, predictable match rates, and structured version history.

Schema Reference Library Examples

Publishing Checklist

Minimum standards before releasing a rule or bundle.

1. Name is precise, outcome-oriented, and non-ambiguous.

2. Description explains when it triggers and why it matters.

3. Thresholds tested with dry-run on representative samples.

4. Version and changelog updated for every behavior change.

Make packs discoverable and safe to reuse.

🏷️

Use intent-first names like "Repertoire Drift Early" over generic labels such as "Rule 7".

🧭

Declare color/time-control/rated filters explicitly so users know where it applies.

🧾

Include creator/source metadata and whether AI contributed to initial drafting.

Recommended governance for a community rules ecosystem.

Avoid thresholds that match nearly all games unless intentionally broad and labeled as such.

No auto-enable behavior from imports; validation and dry-run remain mandatory.

Provide a simple “Report rule” workflow for incorrect behavior or misleading descriptions.

Use semantic updates and preserve backward-compatibility notes when schema evolves.

Start with starter bundles, fork one pack, tune thresholds with dry-run, then prepare a publish-ready pack with changelog and provenance.