Methodology

How Saxum turns requirements into controlled software

Our method separates authoritative requirements, deterministic implementation, customer facts and external acceptance.

01

Source

Start with official portals, specifications, contract instructions and regulator guidance. Record the review date and relevant operational requirement.

02

Model

Translate only mechanical requirements into deterministic checks. Unresolved judgement, customer facts and official decisions remain explicit human actions.

03

Prove

Run example kits, adversarial tests, migration checks, browser audits, signed-sample checks and capability-preservation gates.

04

Correct

Publish material corrections, invalidate stale automation approvals and retain the difference between previous and current behavior.

AI boundary: AI may explain or draft, but it does not waive deterministic findings, invent missing facts, approve releases or certify official submissions.