Instant by Falcra
The Instant Manifesto
Instant is a way of building world-class enterprise software in days with the AI-Driven Development Lifecycle: everyone in one room, from business experts to managers to the technical team, and an AI driving the lifecycle. These are the values it rests on, and the principles that follow from them.
Published by Falcra. The Instant Manifesto was written by Drew Salem, founder of Falcra.
The Instant Framework (theinstantframework.com) by Falcra (falcratechnologies.com)
The Instant Framework is published in three parts: the Manifesto (values and principles), the Guide (what Instant is, its roles, stages and gates) and the Practices (how its decisions, foundations, assurance and AI rules work in detail).
Values and principles
A short manifesto states what Instant values. Ten principles sit beneath it. When a situation isn't covered by a rule, they decide it.
The Instant Manifesto
Published by Falcra.
We are building software with the AI-Driven Development Lifecycle, and helping others do the same. Through this work we have come to value:
- Everyone in one room over handoffs between teams
- Reacting to working software over reviewing documents about it
- Decisions made on the spot by their owners over decisions waiting for the next meeting
- Business-led over developer-led
- Evidence that it works over reading every line of code
- Verified facts over confident guesses
What comes after "over" still matters. We value what comes before it more.
The principles
Everyone in the room
Every stakeholder is present for every Blitz session they are needed in. For Frame and Specify, that is everyone. If one group is missing, the debate stalls and the old delays come back, because someone has to go away and ask.
Debate is essential
Requirements are debated openly, in the room, so disagreements come out now rather than after the build.
Instant feedback loops
People react to working software, not to documents. A screen in front of you tells you things a specification never will.
Decisions are made by the people who own them, on the spot
The person who owns a decision makes it in the room, and it is recorded with who decided and when. Nothing waits for a meeting next week. A disagreement settled on the spot costs minutes. The same disagreement found after the build costs far more.
Build only what was asked
The AI builds what was asked for and nothing more. Anything it thinks would help is listed as a suggestion for your experts to accept or reject, never built quietly. Practices, chapter 3 explains why this matters.
The business owns the requirements
Your experts decide what the software does and shows. The technical team and the AI serve those decisions; they don't replace them.
Evidence, not reading
Nobody can read everything an AI writes. So humans give their attention where it matters, automation covers the rest, and every control is proven to work. Practices, chapter 3 explains how.
A guess is never a fact
The AI says how it knows each thing: seen it working, read it in the code, or assumed. Anything assumed stays labelled as an assumption until someone confirms it, and it never becomes a requirement on its own. This is one of the standing rules in Practices, chapter 4, which apply to every stage.
Record everything
Every session is recorded and transcribed, and the transcripts are given to the AI build tool. Decisions, approvals and changes leave a trail. When someone asks later why something is the way it is, the answer exists.
Your standards win
Where your rules conflict with Instant's defaults, yours apply. That covers security, privacy, data handling and change control.