Skip to main content
Start after your first agent session and reviewed ruleset publication. Keep the approved source, complete test corpus, project ID and publication receipt.

​
Compare two versions

Invoke the fourth skill in your host:
Supply both identities explicitly. A mutable slug or a newly generated candidate is not a substitute for the older publication. If the selected interface cannot address the required immutable identity, report that limitation and use the supported REST replay path below. Do not present a partial corpus as a complete regression comparison. Expected result: one row per reviewed case for each version, with differences called out. Passing those cases establishes that corpus’s behaviour, not every possible input.

​
Inspect an existing composition

A rulebook combines member rulesets. Shared input names do not by themselves define how the members combine. Review the member identities, field definitions and composition logic together; then test the combined outcomes as well as each member’s scenarios. For this exercise, use an existing approved rulebook and synthetic case data. You need a key with access to its detail and decisions. No new authoring or model-provider call is required. Section discovery explains the separate authoring workflow for creating sections and combining them.
The REST transport is explicit here: current MCP and CLI interfaces do not expose every immutable rulebook replay selector. Do not invent a release_id argument on a tool that does not accept it.

​
Pin and replay through REST

Use the secure api_request helper from the authoring tutorial, with an ordinary key that can access the selected rulebook. Set AETHIS_RULEBOOK_ID to that existing rulebook’s ID or slug. Save a reviewed combined-cases.json array containing name, field_values and expected_outcome for every case. Invalid-input cases also include an error_fields array naming the expected errors.
Retain every request and response alongside rulebook-detail.json and the reviewed cases. Check the returned rulebook identity, version and content identity against the pinned release; inspect field_errors for each case. For deliberately invalid input, require the expected error and undetermined, not only a matching decision string. Reject missing, skipped or duplicated cases in your regression report. Repeat with the same release_id and identical inputs. Expected result: the same decisions and content identity. A changed current release should not silently change an explicitly pinned replay. If a pin is unavailable, fail visibly rather than falling back to the current release.

​
Integrate and recover

Use the Python SDK, CLI, MCP or REST for the operations each documents. The TypeScript SDK is not released. Store decision IDs, input hashes and immutable content/publication identities with the application event they explain. Check field errors before treating an outcome as terminal. Keep Aethis and provider credentials on the server or in secure host credential storage. After a failed authoring test, repair the candidate using the source and rerun the complete reviewed suite. After a host timeout, inspect the retained project’s generation status before retrying. A response lost during a test-suite replacement leaves an unknown outcome: do not automatically repeat a destructive write or recreate the project. See troubleshooting and the authoring recovery steps.