Skip to content

Architecture

This page publishes the shape of the platform, not its internals. The rule content, tolerances, and the internal test corpus used to validate the engine are not published — see Methodology for why that boundary exists.

Why rule content stays private

The rule library and its internal test corpus are OXXON's moat. Publishing tolerances and the exact triggering conditions would let the corpus be gamed rather than trusted — a workbook could be engineered to pass the letter of a published rule while still failing the spirit of it. The category (what is tested) is public; the mechanism (exactly how) is not.

Each layer, documented

Module relationships

OXXON Audit, OXXON VERIFY, and OXXON FAST share every layer in this stack — one dependency-graph and rule-execution engine, not three separate parsers. See the FMAE vs FAST Standard comparison for how the structural-integrity and convention-compliance questions differ, and the platform overview for each product's current stage.

Run a structural audit on a real workbook now — Run a structural audit, or see the run lifecycle.

Compare Two Versions