✦ Augur docs

Tooling

Architecture

Augur is four layers, with a hard wall between the deterministic core and the oracle.

  1. Deterministic pipeline — Lector (lexer) → Grammaticus (parser → AST) → Aestimator (tree-walking evaluator). Scope, control flow, and ritual dispatch never consult the oracle.
  2. Zone stack — PilaZonarum tracks the active zone per block, deciding whether each operation is divined, divined-hot, or computed natively.
  3. Provider layer — every backend implements a single Oraculum.divina() interface. An Aerarium (budget) wrapper enforces the call ceiling and tallies tokens; a Diarium (paranoid log) traces each call. The fake oracle makes the whole suite run offline.
  4. Native builtins — Bancus (database), affer (fetch), collection ops, and file/console I/O. These run real code in certain and delegate otherwise.
Implementation identifiers are written in Latin (the augur theme — a Roman priest who divined: Lector, Grammaticus, Aestimator, Bancus, Oraculum). The .aug keywords and all user-facing text are in English.

The evaluator is async end-to-end (every operation can await the oracle), so gather and per-request serve forks are real concurrency. The test suite uses the fake oracle exclusively, so it is deterministic, free, and never touches the network.

← PreviousProviders