RuleSchema v1

Compatibility and schema reference for power users, coaches, and integrators building reusable rule packs.

Rule Object Essentials

Core fields expected by RuleSchema v1.

idStable unique identifier
nameHuman readable title
categoryblunders/opening/tactics/etc.
conditionsAND/OR nested predicates
actionstag/queue/training actions
provenancesource + authorship metadata

Comparator and Action Guidance

Keep packs portable by sticking to documented fields and comparators.

🔍

Comparators

Use stable operators such as gte, lte, eq, and in with field-compatible value types.

🎯

Actions

Prefer deterministic actions like add_tag, add_to_queue, and mark_training_candidate.

🧱

Guardrails

Avoid hidden dependencies. If a field may be missing, ensure behavior remains safe and reviewable.

Manifest Compatibility

Export/import manifests should carry enough metadata for safe migration.

1. Include manifestVersion and schemaVersion.
2. Include seedSetId, bundle list, and rule list.
3. Preserve timestamps and provenance for auditability.
4. Validate all rules before offering enable actions.

Compatibility Matrix (Preview Direction)

App 0.3.xRuleSchema v1 preview support
Import GateSchema validation + dry-run expected
ActivationUser-confirmed only