CMS POLICY WORKSPACE
Generation Configuration
Adjust rule-generation instructions, examples, and policy-specific requirements.
- 01 Configure
- 02 Validate
- 03 Activate
GENERATION SETTINGS
Instructions and evidence contracts
Loading saved configuration…
Loading configuration…
Prompt instructions
Edit interpretation guidance in a draft. Saving does not change the active version.
Non-editable system and compiler constraints
Source text remains untrusted data. The language schema, exact-source checks, parser, compiler, evaluator, and spending limits remain enforced in code.
Changes from active configuration
Worked rule examples
Illustrative requirements and expected Rule IR, not actual CMS-backed quotations.
Edit draft example
Source-bound requirement overrides
Operator hypotheses layered over a saved revision. Original snapshots and frozen requirements stay unchanged.
Frozen original
Original requirement-selection JSON
Exact saved source passages
Proposed override
Use only source-supported fields and exact quotes from this revision. Unsupported logic remains unresolved.
Test configuration before activation
Configuration validation and saved-artifact checks are free. They do not predict whether a changed prompt will generate better rules.
Effective request preview (no provider call)
Optional one-policy candidate
This explicit action may incur LLM charges for one new generation, with up to three provider attempts under existing daily budgets. It reuses frozen requirement data and creates a separate candidate experiment.
Preview the assembled request to inspect the token reservation and configured cost estimate before requesting a candidate.
Version history
Activation and rollback apply to future independent runs. Existing runs keep their pinned configuration and saved results.