Skip to main content
These records separate proposal generation, evaluation, acceptance, and independently verified outcomes. Persisted names remain snake_case in both languages. Rules are relative Markdown files. Each needs a title, an Applies to: ... line, and behavioral guidance. A proposal records a change set against a specific accepted base revision; a null change deletes a file. Ordinary fresh executions receive accepted rules, while candidates are visible during authoring and explicit trials. Task completion in an execution report describes runtime execution; use an independent verifier for business success. A reported rationale is agent-authored evidence, not proof of improvement. Rule is a runtime class; most result records are interfaces returned by Reflect, not constructors. RuleProposal.changes maps paths to rule records or null deletions. Internal record builders are not package exports.

On this page

EvaluationOutcome, ExecutionReport, FailureNotice, ProposalOutcome, Rule, RuleProposal, TrialArm, TrialCase, ValidationVerdict.

Example

Constructing a rule does not publish it. Agent-authored filesystem changes become proposals; independent validation decides acceptance.

EvaluationOutcome

Source declaration

Fields and properties

ExecutionReport

Source declaration

Fields and properties

FailureNotice

Supporting contract used by the API below; it is not a separate package export. Source declaration

Fields and properties

ProposalOutcome

Source declaration

Fields and properties

Rule

Persisted records keep Python’s schema-v1 field names. Host options use camelCase. Source declaration

Constructor

Fields and properties

Methods

Static method on Rule.

RuleProposal

Source declaration

Fields and properties

TrialArm

Source declaration

Fields and properties

TrialCase

Source declaration

Fields and properties

ValidationVerdict

Source declaration

Fields and properties


Signatures and fields are generated from the SDK source. See the import index for available entry points.