.mfsig — Apex file format

Five-pillar canonical container for a σ-profile delivery: audit + chemistry + quantum + AI-feature slot + version. Free to read, free to write, free to verify. Reference-grade delivery is the paid tier.

A .mfsig.json file stores not just numbers — it stores its own history (pillar 1: reproducibility metadata), proves its own accuracy (pillar 2: SHA-256 trust hash), preserves the source bytes (pillar 5: legacy_vault), and is forward-compatible with the AI feature layer (pillar 3).

SHA-256 covers the canonical state subset: geometry, methodology, numerical results, solver call args. Timestamps and UUIDs are explicitly excluded so files round-trip across machines without hash drift.

21 CFR Part 11 ALCOA

Attributable, Legible, Contemporaneous, Original, Accurate. Every field is by construction. The SHA-256 hash makes any post-write edit detectable; the reproducibility block lets a regulator re-derive the result on demand.

Forward compatibility

The .mfsig format is forward-compatible: new pillars are added as optional fields, and any .mfsig.json signed today will verify_integrity() against future readers. The AI-feature slot (cavity-latent-vector pillar) is pre-allocated for downstream ML pipelines.