FERZ, Inc.
Determinism · Field Notes
A timeline-based comparison dashboard

Ninety years of determinism,
and the runtime where it returns.

From Turing's 1936 abstract machine to FERZ's 2026 deterministic authorization boundary, this dashboard traces how the idea of a system whose behavior is fully predictable from its rules moved through formal methods, lost ground to probabilistic AI, and now returns as the governance layer wrapping every probabilistic agent.

6
Eras · 1930s → 2026
39+6
Milestones · FERZ markers
3
Verdicts · ALLOW / DENY / ABSTAIN
01 · Interactive Timeline

Every node is a milestone. Click to inspect.

Six eras of system design plotted on a single 90-year axis. Color encodes paradigm; the red nodes are FERZ's own milestones in deterministic AI governance. Filter by era to read a single thread.
Hover or tap a node to read the milestone, its principal contributor, and its place in the deterministic arc.
02 · The Paradigm Shift

Rule-based, then probabilistic, then hybrid.

The deterministic worldview did not disappear. It migrated. What expert systems tried to do inside the model in the 1980s, runtime governance now does around the model.
1958–1989

Symbolic Determinism

Logic, production rules, expert systems. Every inference is traceable to an axiom. Fails on open-world ambiguity and combinatorial explosion.

LISP · MYCIN · Prolog · Rete
1988–2022

Probabilistic Ascendancy

Bayesian networks, SVMs, deep learning, transformers. Astonishing capability gains, no determinism: same input, different output, no proof of why.

Pearl · AlexNet · Transformer · GPT-4
2023–Present

Hybrid Authorization

Probabilistic core, deterministic boundary. The model reasons; a runtime authorization layer decides what may execute, and emits a recorded, integrity-checked Proof-Carrying Decision.

NIST RMF · EU AI Act · FERZ 5TS · PCD
03 · Side-by-Side

What changed, dimension by dimension.

The compact answer: every property that was once a property of the model is now a property of the artifact produced about the model's action.

Classical Deterministic Systems

Floyd–Hoare · TLA+ · DO-178B
  • LocusProperty of the program itself
  • EvidenceMathematical proof of correctness
  • Time horizonPre-deployment verification
  • Failure modeCompile-time / proof-time rejection
  • ScopeClosed world, fixed specification
  • Cost frontierState-space explosion
  • Governance roleEngineering discipline

FERZ Runtime Authorization

5TS · PCD · LASO(f) · DELIA
  • LocusProperty of the authorization boundary around the model
  • EvidenceProof-Carrying Decision: a recorded, integrity-checked decision artifact emitted with every authorized action
  • Time horizonEvery action, every invocation, at runtime
  • Failure modeABSTAIN: execution blocked pending an authorized human override, itself recorded as an authorization event
  • ScopeOpen-world, probabilistic agents, regulated deployment
  • Cost frontierPer-action validation before any effect executes
  • Governance roleCompliance and audit infrastructure
04 · FERZ Inheritance Map

The intellectual lineage of each FERZ engine.

FERZ did not emerge in isolation. Its architecture reflects decades of work in deterministic computing, formal verification, authorization, and safety-critical systems engineering. FERZ applies these traditions to the problem of runtime authorization for AI systems.
01 · ENGINE

LASO(f)

Semantic / language governance layer that canonicalizes intent before authorization is evaluated.

intellectual lineage → McCarthy LISP · Hoare logic · Constitutional AI
02 · ENGINE

DELIA

Deterministic constraint enforcement. Validates each candidate action against policy before any effect is permitted.

intellectual lineage → Forgy's Rete · Production rules · Model checking
03 · ENGINE

CausaCore

Causal modeling engine that traces decision lineage and explains why an authorization was granted or denied.

intellectual lineage → Pearl's do-calculus · Bayesian networks · Causality (2000)
04 · ARTIFACT

Proof-Carrying Decision

Recorded, integrity-checked evidence emitted with every authorized action. The governance artifact of record.

intellectual lineage → Necula's Proof-Carrying Code (1997) · ACID · DO-178B traceability
05 · STANDARD

The Five Tests Standard (5TS)

An action must satisfy the relevant tests: Stop (authorization before execution), Ownership (accountable principal identified), Replay (full audit reconstruction), Escalation (exception routing to human authority), and Provenance (origin of inputs established), before any effect is permitted. This is what replaces "probably compliant" with "provably compliant".

intellectual lineage → IEC 61508 SIL · Hoare pre/post-conditions · NIST AI RMF Govern function
06 · FORWARD

Forward Architecture

FERZ publishes forward-looking governance architecture, including a constitutional authority-distribution model for higher-autonomy settings: roadmap architectures, published to establish defensive prior art.

intellectual lineage → Constitutional AI · TLA+ for distributed protocols · formal-methods invariants

The timeline traces intellectual influences and engineering traditions. It does not imply direct derivation or endorsement by the cited works.