Pick the confidence level
Modes
Axiom has two canonical modes. Select one deliberately; removed and legacy names are not accepted.
| Mode | Use it when | Status |
|---|---|---|
basic | The default single-level matcher for local durable service or direct in-memory use. | Supported; qualification active |
multilevel | The recursive hierarchy matcher for local durable service or direct in-memory use. | Available; resource qualification currently fails at startup |
Both modes use the same SQLite-backed Durable and thread-safe local Service path. basic is the default; choose multilevel explicitly when you need the recursive hierarchy. Neither mode is deployment-qualified. The latest constrained run fails Basic recovery and Multilevel startup—see current alpha status.
basic
The single-level path maintains one z-system and its matching state. It is the best mode for learning the API, writing integration tests, and establishing a baseline for experiments.
matcher = Matcher(n=100, mode="basic")multilevel
The multilevel path recursively derives hierarchy levels and maintains level-specific state. Its public name is now canonical: use mode="multilevel", not a compatibility alias.
matcher = Matcher(n=100, mode="multilevel")For larger graphs, the hierarchy uses decreasing thresholds and phase schedules. The implementation validates shared graph identity, level ordering, deferred deletions, and the cross-level invariant before exposing refreshed state.
Do not over-read the research claim. Axiom exposes the multilevel engine for implementation and evaluation. The complete ABB+26 asymptotic guarantee is not claimed until the remaining paper-faithful coloring and end-to-end validation work is complete.
What is deliberately unsupported
Only the two documented constructor modes are accepted. Invalid mode names fail clearly so configuration mistakes are visible immediately; there is no forwarding constructor or wrapper API.