Catalog overview¶
The Jane Reference catalogs document every rule, module, and decision surface available in the pipeline. Each catalog provides implementation‑level details, event codes, and execution semantics for its subsystem.
Boundary Rules¶
Boundary rules define how multi‑pipeline objects are validated. They describe structural expectations, field‑level constraints, and nested boundary composition.
Normalizers¶
Normalizers transform raw input into a canonical shape before parsing. They are ordered, pure, and type‑driven, ensuring consistent structure across all pipelines.
Parsers¶
Parsers convert normalized values into typed values. They are explicit, ordered, and event‑emitting, enabling safe interpretation of strings, numbers, dates, arrays, objects, and more.
Validators¶
Validators enforce semantic constraints on parsed values. They are explicit, non‑mutating, and ordered, producing validation events that policies interpret.
Scanners¶
Scanners detect structural hazards before normalization or parsing. They are type‑driven, non‑mutating, and policy‑interpreted, providing early warnings for malformed or unsafe input.
Policies¶
Policies interpret events produced by scanners, normalizers, parsers, and validators. They determine acceptance, rejection, severity, and analysis behavior for each pipeline run.
See: Policy catalog