ADL: Bridging Intent and Autonomous Software Construction with a Two-Primitive Formal Specification Language

Keijo Tuominen

April 2026 • CMHT Technology Research

Abstract. This paper presents ADL (Application Description Language), a formal specification language that encodes software domains using exactly two primitives—entities and state transitions. We evaluate it empirically in both forward construction (producing 193 passing tests) and reverse validation across three technology stacks.

Figure 1: The ADL Bidirectional Validation Cycle

1. Introduction

The standard model of software development requires human developers to translate intent into code—a process that is inherently lossy. ADL provides a formal intermediate layer to close this gap.

2. ADL Specification Language

ADL models a software domain using exactly two constructs: Entity and Transition. An Entity represents a persisted domain object, while a Transition encodes the behavioral contract.

Figure 2: The 6-Gate Autonomous Elaboration Pipeline

4. The 6-Gate Pipeline Architecture

The ADL pipeline is a 6-gate sequential chain. No natural language passes between gates after Gate 1, ensuring a strictly formal process.

Pass	Group	Focus Area
1	Core	Models, Schemas, Database Init
2	Routes	API Endpoints, Business Logic
3	Infra	Auth, Background Jobs, Migrations
4	Tests	Integration & Unit Test Suites

6. Bidirectional Validation: Three-Stack Proof

ADL bidirectionality was proven across three distinct technology stacks: Node.js/Express, Python/FastAPI, and Flutter/Dart.