Structure from stochasticity

1729 AI Labs

Building deterministic systems from probabilistic LLMs

We research the two problems we believe matter most in AI today — making probabilistic systems reliable, and redesigning how humans and machines collaborate.

01The Problem

LLMs are the most capable technology we've ever built. They are also fundamentally unreliable.

Large language models can generate useful work across many tasks. In production systems, the issue is not capability—it is operational reliability: consistent behavior, bounded failure modes, and traceability.

01 · Reliability

They hallucinate. They generate fiction with the same confidence they state facts. The failure mode isn’t absence of output. It’s the presence of plausible fiction.

They’re unreliable. Same prompt. Same model. Same conditions. Different output. No error code. No warning.

These are not edge cases. They are expected properties of probabilistic generation. If you want deterministic outcomes, you need a system architecture that constrains, verifies, and corrects model outputs—rather than trusting a single completion.

02 · Collaboration

Meanwhile, the way we work with them — a chat box and a blinking cursor — was never designed. It was inherited. We're using the most powerful cognitive technology ever built through an interface that asks the human to do all the work.

Two unsolved problems. We work on both.

02Thesis I: Engineering Determinism

How to get deterministic outputs from probabilistic LLMs.

What probabilistic means in practice

An LLM-based system books your flight and hands you a boarding pass. You show up at the airport. The flight doesn’t exist. The LLM didn’t fail to act — it hallucinated a completed task, with full confidence.

Ask the same system to book New York, ten times. Nine times it works. Once, you get San Francisco. No error. No warning. No way to predict when it will happen next.

This is what probabilistic means in practice. Not a theoretical concern — a structural one. The model isn’t broken. It’s working exactly as designed. It’s just not designed to be reliable.

We’ve seen this problem before.

The early internet was a lossy medium. Packets got lost, misrouted, arrived corrupted. The question was the same: how do you build reliable systems on top of an unreliable foundation?

The answer was never to make the network perfect. It was to manage imperfection — through detection, correction, retransmission, and redundancy. The component stayed lossy. The system became reliable.

LLMs are today’s lossy medium.

We take the same systems approach. Instead of waiting for a model that doesn’t hallucinate, we engineer the layers around it — pre-processing, post-processing, verification, correction loops — so the system is deterministic, even when the component isn’t.

Thesis I

Don't fix the medium. Engineer around it.

03Thesis II: The Allocation of Judgment

How should humans and LLMs actually work together?

Watch someone use an LLM. They struggle to write the right prompt. They paste in context the system should already have. They read a wall of generated text to check if it's correct. Then they edit it manually.

The human is doing all the wrong work.

Humans

Extraordinary at judgment — making decisions, choosing between options, saying yes or no.

Poor at articulating context, writing precise instructions, transferring knowledge.

LLMs

Exceptional at generating, documenting, transferring context, following instructions.

Poor at judgment.

It's a collaboration designed backwards. The current interface asks humans to do what they are worst at, and LLMs to do what they are worst at.

We build interaction models built on a simple principle: Humans should only make decisions. They choose, approve, reject, and steer. The system handles the rest: gathering context, generating options, and executing the work.

Thesis II

The right interface isn't a better chat box. It's a fundamentally different division of labor.

04Origin

Why 1729.

1729

In 1918, the mathematician G.H. Hardy visited Ramanujan in the hospital. He mentioned his taxi was numbered 1729 — a rather dull number.

Ramanujan disagreed instantly. It was the smallest number expressible as the sum of two cubes in two different ways.

He didn't compute it. He saw it.

Structure, where others saw randomness.

That's the instinct we're building around. LLMs look chaotic — probabilistic, unreliable, unpredictable. We believe there is structure in that stochasticity. Not by hoping it emerges, but by engineering systems that find it and enforce it.

These ideas weren't developed in isolation. They were battle-tested across three years of enterprise AI deployments at TrueReach.ai — where we learned what breaks, what holds, and what it actually takes to make AI systems reliable.

1729 isn't just a name. It's a thesis.

Our Journey

Mid-November 2022

Initial lab launch.

Two weeks before ChatGPT launched.

The original lab was incorporated in mid-November 2022. The founding belief was already set: models would become abundant; reliable systems built around them would remain scarce.

30 Nov 2022 ChatGPT launches Large language models reach the mainstream.

March 2023

Autonomous performance marketing product.

Deployed across three enterprises.

Autonomous performance marketing with auto-segmentation, copy and image generation.

21 Jun 2024 Claude 3.5 Sonnet launches Strong coding capability becomes faster and less expensive.

July 2024

Our first vibe-coded production application.

Seven months before “vibe coding” had a name.

An industrial IoT platform for water-treatment plants, built on our platform: all code written by AI under the supervision of one engineer — seven months before “vibe coding” had a name.

Feb 2025 Natural-language coding gets a name Karpathy coins “vibe coding.” Collins later makes it Word of the Year.

March 2025

Factory 0.4: 50% automation.

698,000 lines. Four applications. Delivered in 17 weeks.

The first enterprise validation: a four-application Azure platform spanning web, backend, customer and partner apps, with 28 web screens, 64 API endpoints and 22 database tables.

22 May 2025 Claude Sonnet 4 launches Models improve at coding and long-running agentic work.

September 2025

Factory 0.6: 70% automation.

690,000 lines. Web and mobile. Delivered in 14 weeks.

A Nuxt and .NET platform with a Flutter mobile app, 56 screens, 52 API endpoints and an Azure production architecture.

December 2025

Factory 0.8: 90% automation.

511,000 lines. Production on AWS. Delivered in 7 weeks.

A React and NestJS system with 38 screens, 47 API endpoints, 14 data models and an AWS production architecture.

5 Feb 2026 Claude Opus 4.6 launches Million-token context. Long-running agentic work becomes viable.

June 2026

The lab becomes a company.

1729 AI Labs is incorporated in the United States.

We incorporated the US company to commercialize the technology.

July 2026

Factory 1.0: 100% automation.

Brownfield software. 20,000 lines changed. Three days. No engineering team.

On a 500,000-line production system, the factory autonomously changed 20,000 lines — including the architecture and data schema, a complete UI refresh and new modules. The work took three days.

Join Us

We're looking for people who are bothered by the right problems.

If you think the chat box is the final interface, we're probably not the right place. If you think LLMs need to be perfect before they're useful, we're probably not the right place.

But if you believe reliability is an engineering problem and collaboration is a design problem — and both are solvable — we'd like to hear from you.

founders@1729labs.ai →