AIE
Activation Integrity Engine applies deterministic state and correction logic to telecommunications activation, attach, porting and provisioning operations.
Deterministic State Engines
Same inputs. Same rules. Same state.
Deterministic State Engines (DSE) are the engine family for operational domains where state must be explicit, replayable and fail closed on contradiction.
Deterministic state.
DSE engines preserve authoritative inputs, versioned configuration, explicit time basis, fail-closed contradictions and reconstructible outputs. The Activation Integrity Engine (AIE) and the Bank / Forensic Integrity Engine (BFIE) are specialized integrity engines in the same family.
BFIE
Bank / Forensic Integrity Engine projects financial and evidentiary state without moving source-of-truth math into presentation layers.
Fail closed
Missing or contradictory required truth produces HOLD or non-action instead of confident fiction.
Replay
State can be reconstructed from authoritative inputs and versioned configuration.
Software History
How the engine evolved.
Architecture changed as the operating boundary became clearer. Earlier generations remain part of the evidence trail rather than being rewritten as if the current implementation appeared fully formed.
Execution engines were separated from decision authority.
The operating doctrine that preceded the formal DSE family treated software engines as execution bodies: follow declared logic, preserve logs, obey bounded controls and stop conditions, and leave consequential authority outside the engine. That separation became the foundation for later deterministic-state work.
DSE became a parent family with separate field engines.
The DSE codebase was seeded as a family house with AIE and BFIE kept as separate lanes rather than one universal engine. The parent standard defined the common determinism law while each field retained its own data model, state machine and implementation body.
The field engines hardened independently.
BFIE moved into a hardened Rust projection core while AIE bound telecom route and activation evidence into its deterministic state model. Standalone AIE and BFIE repositories then became the canonical homes, with DSE retaining parent copies and shared family law.
The family standard is explicit and replay-oriented.
A DSE field engine is expected to preserve deterministic configuration, fail closed on missing or contradictory required input, retain append-only or tamper-evident receipts, prevent authority leakage and remain operable without making external SaaS a critical dependency.
Current Evidence
AIE and BFIE remain explicit sibling engines under one deterministic parent standard.
Missing or contradictory required truth resolves to HOLD / non-action rather than inferred state.
Proof
Engine claims are testable.
The DSE machine authority locks replayability, explicit lane boundaries and fail-closed handling: missing or contradictory required truth produces HOLD or non-action rather than an invented result.