×

Three Explanation Tracks

This page gathers the three explanation tracks as a structured media set.

General Track

The general track explains why heuristic safeguards are brittle and why checked artifacts matter. It starts with oversight rather than proof-assistant jargon: when a rule is important, the organization needs to know exactly what it accepted.

Developer Track

The developer track can talk about type systems, dependent types, proof assistants, and the difference between a model that predicts text and a checker that validates a formal artifact. This is the right place to explain why Agda appears throughout the stack.

Expert Track

The expert track can show how the pieces fit together:

  • Codex Scribe for expert-led formalization;
  • MLTTDB for externally editable checked data;
  • State Machine Studio for layered workflow models;
  • cubical-sm and SMLogic for state-machine and temporal logic semantics;
  • tower for implementation layers;
  • generated HTML and runtime services for practical demos.

As the media library grows, this route can become the hub for the site’s strongest explanations.

Skip to content

Interview

Three Explanation Tracks

General, developer, and expert explanations of the Formal Foundry workflow.

This page gathers the three explanation tracks as a structured media set.

General Track

The general track explains why heuristic safeguards are brittle and why checked artifacts matter. It starts with oversight rather than proof-assistant jargon: when a rule is important, the organization needs to know exactly what it accepted.

Developer Track

The developer track can talk about type systems, dependent types, proof assistants, and the difference between a model that predicts text and a checker that validates a formal artifact. This is the right place to explain why Agda appears throughout the stack.

Expert Track

The expert track can show how the pieces fit together:

  • Codex Scribe for expert-led formalization;
  • MLTTDB for externally editable checked data;
  • State Machine Studio for layered workflow models;
  • cubical-sm and SMLogic for state-machine and temporal logic semantics;
  • tower for implementation layers;
  • generated HTML and runtime services for practical demos.

As the media library grows, this route can become the hub for the site’s strongest explanations.

Book a meetingStart a scoped conversation

Cabinet index

Explore Formal Foundry

Search the archive

Find a page

Type to search the published content.