Skip to content

Papers

Formal Foundry Whitepaper

Abstract

A position paper on AI-assisted formalization where proof assistants remain the deterministic checking boundary. It frames AI as an accelerator for drafting, search, and translation, while formal definitions and checked proofs provide the audit trail needed for large-scale correctness in complex intelligent systems. The emphasis is not automation alone, but a reviewable boundary where generated candidates become trustworthy artifacts only after deterministic checking.

The Formal Foundry whitepaper is the company’s older architecture argument for combining AI systems with formal methods.

Its central thesis is still useful: AI can help with the supply side of formal methods by drafting, searching, and proposing proofs or specifications, while proof assistants provide the deterministic correctness boundary. The whitepaper frames this as a response to “large-scale correctness”: as AI systems become more complex and more widely deployed, ordinary testing and review become too weak on their own.

Architecture Argument

The whitepaper and architecture page describe four major components:

  • domain formalization, where real-world logic and rules become formal definitions;
  • theorem or specification generation, where a concrete input is paired with a formal correctness target;
  • proof generation, where proofs or refutations are iteratively produced and checked;
  • translation, where formal statements and proofs are rendered back into readable language.

The modern Codex Scribe story is a more productized version of that argument. The expert still owns intent. AI helps move faster. The proof assistant checks. A read-back layer makes the checked meaning reviewable.

Good Use On The Site

Treat this as a whitepaper, not an academic publication. Its strongest role is to connect the company mission to the product pages:

  • Codex Scribe as the expert-facing formalization loop;
  • MLTTDB as an operational data layer for checked terms;
  • State Machine Studio as a workflow-modeling front end;
  • Agda Runtime, Agda web services, and compiler experiments as infrastructure for agentic proof-assistant workflows.

The page should also acknowledge that the whitepaper is an earlier formulation. The copy can preserve the thesis without making every older roadmap sentence sound like a current product claim.

Download paperOpen the source PDF

Cabinet index

Explore Formal Foundry

Search the archive

Find a page

Type to search the published content.