The bridge between what we mean and what machines build.

AI now writes code faster than people can. What it can’t supply is the intent: what a system is for, what it promises, what it must never do, and who decided. Structured intent is the discipline of writing that down, so machines can build from it and check against it.

A real structured intent. Tap a clause to see where it came from and how each implementation keeps it.

transfer_funds.intent.yamlversion 3

goal Move money between two accounts, safely and at most once per request.

Originintended

Lifted from legacy/ledger.c:180. Ruled a promise by the ledger owner.

Evidence inTested

10,000 seeded random transfers. A formal proof is written but has not been run yet.

Quality: the tests reject 12 of 14 deliberately broken versions of the code. See the full example

Code preserves what a machine does. Structured intent preserves why it should do it.

Author it, lift it or merge it. Then lower it.

Intent can be written for a new system, recovered from existing code, or combined from several systems. Every implementation is then generated from the same intent and reports how strongly it keeps each promise.

Author, lift or merge into one structured intent, then lower it into many implementations Author For new systems Lift From existing code Merge From several systems Structured intent goal requires ensures never priority origin evidence Lower Rust Type-checked, tested Python Runtime-checked, tested Next technology Same intent, new binding Author, lift or merge into one structured intent, then lower it into many implementations Author Lift Merge Structured intent goal requires ensures never priority origin evidence Lower Rust Python Next
Three roads lead in and one leads out. The rows in color are what make an intent structured rather than just a spec: priorities, where each promise came from, and how strongly each implementation keeps it.

Why now

Each advance in programming disciplined something that had been left to chance. AI makes the next one practical, because lifting intent from code and lowering it into many technologies is finally cheap.

  1. 1960s–70s

    Structured programming

    Disciplined control

    Sequence, selection and iteration replaced tangled jumps, so a program’s flow could be reasoned about.

  2. 1980s–90s

    Object-oriented programming

    Disciplined state

    Data was bundled with the behavior allowed to change it, so systems could be organized around things.

  3. 2020s–

    Structured intent

    Disciplined purpose

    Software is organized around what it is for: its promises, its limits, and how it trades one goal against another.

Latest news

All news

Machines act. People judge.

When building is nearly free, a wrong plan costs more than ever. The valuable work moves to choosing the right questions, ranking priorities and ruling on what a system should do. Structured intent is where that judgment is kept.

Where human value moves