Skip to main content
Authoring is invite-only private beta. Everything on this page needs an Aethis API key with authoring scopes, plus your own model-provider key for the generation steps. Request access, or start on the open evaluate tier with your first decision — no key required. The two tiers are set out on Capabilities and access.
Authoring is invite-only private beta — request access.
Simple rules? Skip this phase. If your domain fits a single section (one coherent set of criteria, one decision), go straight to Phase 3 — Rule generation. Section discovery is for multi-section domains where decomposing the legislation correctly before authoring begins matters.

What section discovery does

Complex legislation often contains multiple distinct entitlements or criteria that operate independently. Section discovery proposes how to split source text into sections — each of which becomes its own independently testable rule ruleset. For example, UK Free School Meals eligibility has three sections:
  • Section A (child eligibility gate): age 4–15, attending a state-funded school in England
  • Section B (means-tested household): qualifying benefit or income below threshold
  • Section C (universal infant): automatic entitlement for Reception–Year 2, no income test
Sections A and B come from the Education Act 1996 and the Free School Meals Regulations 2014. Section C draws additionally from the Children and Families Act 2014. The Free School Meals Regulations 2014 contribute to all three sections — different regulations to each. The outcome logic is A AND (B OR C): A is a prerequisite gate, B and C are alternative routes.

Run section discovery

Returns:
Notice that education_act_1996_s512.md appears in both Section A and Section C — different provisions of the same document apply to different sections.

Validate against your expected structure

If you know the sections you expect, validate immediately after discovery:
Returns (all match):
Returns (mismatch):

Refine if sections are wrong

If discovery merged sections that should be separate, or split a single section unnecessarily:
Feedback must reference the specific source clause or principle. Vague feedback (“split it differently”) won’t converge. Provide the section name, why it should be separate, and the clause that establishes the boundary.

After section discovery

Once sections are agreed, create one project per section and move to Phase 2 — Field vocabulary.
Returns:
Pass the same domain string on every aethis_create_ruleset call. Guidance added with aethis_add_domain_guidance applies automatically to all projects in the domain — no need to repeat cross-section principles on each ruleset individually.

Section composition

Sections compose into a rulebook at evaluation time. The outcome logic is applied across section results:
Section A is a prerequisite gate. Sections B and C are alternative routes — passing either is sufficient. This mirrors the statutory structure: the Universal Infant entitlement (C) is layered on top of the means-tested route (B), both sharing the same child eligibility gate (A). See the UK Free School Meals worked example for the full multi-section structure with source documents, test cases, and published ruleset IDs.