The AppUnik Framework™
Every system is designed the same way: four stages, seven layers, and one contract for every requirement.
- 0
- stages
- 0
- layers
- 0
- contract fields
- 0
- instruments
Most projects fail on the things nobody asked for.
"Build a website for my logistics company"
A general AI answers the request as written. The AppUnik Framework also maps what the request implies. A general AI would start writing pages. The framework first asks what has to exist for this to actually bring in business.
You asked for a website. Your objective needs a complete customer acquisition system.
How the framework thinks, in order.
- 01
Understand
What outcome is this really for?
Restate the request as an outcome, detect the domains it touches, and write down every assumption with its evidence.
Output: Objective, domains, assumptions - 02
Expand
What must exist for that outcome to work?
Walk all seven layers. For each one, name the capabilities the system needs, then every requirement inside them, with its dependencies.
Output: Capabilities and requirements across 7 layers - 03
Decide
Which choices only a human can make?
Sort everything into known, inferred, recommended and unknown. Only the unknowns that change architecture, risk or cost become questions.
Output: Critical questions, risks - 04
Architect
In what order, and who runs it?
Turn the dependency graph into a build sequence, assign every requirement an owner, and score how ready the system is.
Output: Roadmap, operating model, readiness
Every system is mapped across the same seven layers.
People usually ask for one layer, almost always Experience. The other six are where projects stall, overspend or get into trouble. Each layer breaks down into capabilities, and each capability into requirements.
Purpose
Why should this exist, and for whom?
Every later decision traces back here. Without a clear customer, offer and success metric, the rest of the system has nothing to optimize for.
Freight buyers compare several providers at once. Without a sharp answer to who you serve and why you, the site becomes a brochure that ranks for nothing and converts no one.
- Target customer segments
- Buyer roles
- Priority lanes
- Value proposition
- Service catalog
- Lead and revenue targets
Every requirement answers the same seven questions.
- 01Why it existsThe reason, traced back to your objective. In plain words and in technical terms.
- 02What it includesThe concrete parts that make it real.
- 03Done whenHow anyone can check it is finished.
- 04Depends onWhat must exist first. Together these form the dependency graph.
- 05Build phaseFoundation, Launch or Scale.
- 06EffortS, M or L.
- 07OwnerA person, an AI agent, software, or an outside provider.
Each enquiry goes to the right salesperson by region or service, without someone sorting emails.
Rules on form fields assign an owner in the CRM with an SLA timer.
Know what is decided, and ask only what matters.
You asked for it.
Shown as: Requested
Clearly implied by what you said.
Shown as: Inferred
A sensible default, chosen so you don't have to.
Shown as: Recommended
A decision only you can make. The only thing that becomes a question.
Shown as: Decision needed
Ask only when the answer changes the system.
An unknown becomes a question only when the answer would change the architecture, carries real risk, or would be expensive to reverse later. Which database to use? The framework recommends one. Whether you will store medical records? That gets asked, every time.
Every blueprint is measured the same way.
Five instruments score every blueprint with fixed formulas, so two ideas can be compared and a plan can be checked. The values below are from the worked example.
Implication Ratio
IRHow much the request implies.
discovered requirements ÷ requested requirements1 : 20 means for every thing you asked for, the system needs twenty more.
AppUnik Readiness Index
ARIHow resolved the system is, from 0 to 100.
Σ(importance × confidence of resolved requirements) ÷ Σ(importance of all requirements)Unknowns and anything waiting on an open decision count as unresolved.
Blind Spots
BSLayers that carry critical work the request never mentioned.
layers with at least one critical requirement and nothing requestedWhere projects usually stall, overspend or get into trouble.
Critical Path
CPThe minimum number of steps that must happen in sequence.
length of the longest chain in the dependency graphNo amount of parallel work makes the build shorter than this.
Decision Gate
DGWhether an unknown deserves to interrupt you.
⁴√(impact × risk × cost of reversal × uncertainty), each scored 1 to 5Only unknowns scoring 3.5 or higher become questions. Everything else gets a recommended default.
"Which CRM does your sales team use today, if any?"
⁴√(4 × 3 × 4 × 5) = 3.94
Above 3.5, so it is asked. A question about which database to use would score near 2 and get a recommended default instead.
System Shape
Readiness on all seven layers at once. The low points show where the plan is thin.
Worked example
A blueprint ends in a build plan.
Roadmap
The dependency graph becomes a build order.
- 1FoundationMust exist before anything else works.
- 2LaunchNeeded to go live with real customers.
- 3ScaleMakes it grow, cheaper to run, or harder to break.
Operating model
Every requirement has an owner who runs it.
- PeopleJudgement, relationships, approvals.
- AI agentsRepetitive judgement work, with a human escalation path.
- SoftwareDeterministic work your product does itself.
- ProvidersBought from other companies: payments, hosting, CRM, email.
Readiness
One number for how resolved the system is.
Readiness measures how much of the architecture is resolved. Each requirement counts by its importance. Known, inferred and recommended requirements count as resolved, scaled by confidence. Unknowns and anything waiting on an open question count as unresolved.
The rules every blueprint follows.
We start with what has to be true for the business. The tech stack comes after that.
Every requirement must belong to this request. Generic filler is left out.
Defaults are chosen for you. Only decisions that change architecture, risk or cost come back to you.
Every requirement shows why it exists and what it depends on, back to the objective.
Each item is written twice: for the founder and for the engineer.
Every answer creates a new version of the blueprint, linked to the last.
Run the framework on your idea.
Type one sentence and get a full system blueprint in about a minute.
Design my systemDesigned by AppUnik Super Intelligence. Built by AppUnik.