Reference

Scope: exhaustive lookup. These pages answer what are the options? They do not explain when to reach for one. For that, start from a journey: Get started, Declare what to check, Add tracevals to CI, or How the judge decides.

CLIrun, calibrate, fill, capture, prepare, check, release, and list: every argument, flag, and default.

ConfigurationEvery manni.config.yaml key under tracevals, including the ones with no CLI flag.

GradersEvery kind: the ai, human, and command families, and the seven deterministic ones with their options and failure messages.

Evals schemaThe metadata.evals frontmatter block, field by field, across both published versions.

Reports & exit codesThe pretty, JSON, and markdown report shapes, the exit-code contract, and the history file.

TracesSupported trace formats, what is read out of them, and how the session store is found.

APIEverything the tracevals namespace exports, grouped by what it is for, with the intended entry points marked.

GlossaryTrace, artifact, eval, grader, plan, finding, outcome, consensus, zone, and sidechain.

Reading these pages

• Defaults are the resolved values. Every knob flows through the config file, which fills in every default before anything reads it. A CLI flag overrides the resolved config instead of bypassing it, so the default shown for a flag is the config default it would replace.
• Unknown configuration keys are errors. The schema rejects additional properties at every level below tracevals:, so a typo fails loudly instead of being ignored.
• Deterministic grader options are validated before grading. A malformed eval produces an error outcome naming the offending option, never a silent pass.
• Connection settings are not on these pages. Which endpoint, key variable, or command reaches a model is declared once for the whole family, in the top-level providers: map. It has its own reference, and tracevals.provider only names which entry in it to use.