Section
General information
Core config metadata plus draft locator. Use draft id, or config id and version, to load an existing draft.
Schema
counterparty.evaluation.config.v1
Current draft
new
Current artifact
none
Section
Sources
Visual editor for generic HTTP sources, nested API methods and safe method testing.
Sources: 0
Methods: 0
Safe test mode.
Use exact
${ENV:NAME} placeholders for auth secrets. Method templates support {{inn}} substitution during test calls.
Select a source to edit its base URL, allowlist and methods.
Select a method to edit templates and run a safe test call.
Test method
Test call
The backend resolves ${ENV:NAME}, substitutes {{inn}}, applies allowed_domains and SSRF checks, and never returns secrets.
Response tree
Tree explorer
Build a structured JSON/XML tree from the current method response and add field mappings into an existing criterion.
Run a test call or send a direct response payload to build the response tree.
The tree shows exact sample paths and, for JSON arrays, wildcard path proposals.
Advanced sources JSON
Section
Criteria
Visual criterion editor with metadata, required method references, mapped fields, rule builder and separate no-data rule builder.
Criteria: 0
Fields: 0
Config-first logic.
Criterion rules, no-data behavior, explain texts and weights remain data-driven in config JSON. PHP only validates and executes the generic format.
Field mappings.
Use the response tree in Sources to append field mappings into a selected criterion. Required method references are auto-added when a new field mapping is inserted.
Select a criterion to edit metadata, fields, rules and no-data behavior.
Execution scope
Required methods
These source.method references define which API methods the evaluator must call before the criterion can be evaluated.
No required methods yet. Field mapping will auto-add them, or add them manually below.
Field mappings
Criterion fields
Fields are usually created from the response tree. You can review ids, labels, selectors, flags and remove or reorder mappings here.
No fields yet. Use the response tree in Sources to add a field mapping.
Rule builder
Rule
Build nested AND / OR / NOT groups without editing JSON manually. Move, delete and re-order conditions as needed.
Available operators: exists, missing, equals, not_equals, in, not_in, regex, gt, gte, lt, lte, count_gt, count_gte, count_lt, count_lte, date_before, date_after.
Run “Validate rule” to check the current rule structure.
No data
No data rule builder
Configure when the evaluator should return no_data instead of matched or unmatched.
For
required_fields_missing, leave the field list empty to use all fields marked required_for_decision.Run “Validate no data rule” to check the current no-data logic.
Test criterion
Mock field values
The current stage evaluates the criterion against mock field values. This is sufficient to validate rule logic before the evaluator API is implemented.
No fields to test yet. Add field mappings first.
Advanced criteria JSON
Section
Decision
Decision rules block for final policy logic. Publish stores a normalized artifact, activation makes one artifact active per config_id, and export returns the active JSON only.
Rules: 0
Section
LLM
Optional LLM settings. Leave blank to persist null in the config.
State: disabled
Section
Notifications
Optional notification settings. Keep secrets as ${ENV:NAME} placeholders only.
State: disabled
Section
Validation
Validation status is mirrored in the right panel. Server-side validation uses the shared validator and returns structured path/message pairs.
Errors: 0
Validation flow.
Use Validate to check the current in-browser config. Use Save draft to persist the editor state in PostgreSQL once the database is configured.