Skip to content
moose-tracevals

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 moose-tracevals to CI, or How the judge decides.

CLIrun, fill, and list: every argument, flag, and default.
ConfigurationEvery moose.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 human, JSON, and markdown report shapes, the exit-code contract, and the history file.

Reading these pages

Section titled “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 config schema rejects additional properties at every level, 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.