AppUnikSuper Intelligence
The method behind AppUnik Super Intelligencev1.0 · Specification

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
ObjectiveYour request01Purpose02Experience03Operations04Technology05Trust06Growth07Intelligence01 Understand02 Expand03 Decide04 Architect
The AppUnik System Map
Why a framework

Most projects fail on the things nobody asked for.

The request

"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.

What the framework found
42 requirements · 21 capabilities

You asked for a website. Your objective needs a complete customer acquisition system.

6
Purpose
10
Experience
5
Operations
6
Technology
5
Trust
6
Growth
4
Intelligence
4 stages

How the framework thinks, in order.

  1. 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
  2. 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
  3. 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
  4. 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
7 layers

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.

Layer 01

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.

Business modelAudienceValue propositionSuccess metrics
In the example: "Build a website for my logistics company"

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.

Ideal customers
  • Target customer segments
  • Buyer roles
  • Priority lanes
Offer and positioning
  • Value proposition
  • Service catalog
Success metrics
  • Lead and revenue targets
1 contract

Every requirement answers the same seven questions.

  1. 01
    Why it exists
    The reason, traced back to your objective. In plain words and in technical terms.
  2. 02
    What it includes
    The concrete parts that make it real.
  3. 03
    Done when
    How anyone can check it is finished.
  4. 04
    Depends on
    What must exist first. Together these form the dependency graph.
  5. 05
    Build phase
    Foundation, Launch or Scale.
  6. 06
    Effort
    S, M or L.
  7. 07
    Owner
    A person, an AI agent, software, or an outside provider.
Lead routingOperations · Enquiry handling
Why it exists

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.

What it includes
Routing rules · Owner assignment · Fallback owner
Done when
Every lead has an owner within 5 minutes
Depends on
Quote request form · CRM connection
Phase
Launch
Effort
S
Owner
Software
4 states

Know what is decided, and ask only what matters.

Known

You asked for it.

Shown as: Requested

Inferred

Clearly implied by what you said.

Shown as: Inferred

Recommended

A sensible default, chosen so you don't have to.

Shown as: Recommended

Unknown

A decision only you can make. The only thing that becomes a question.

Shown as: Decision needed

The question rule

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.

5 instruments

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

IR

How much the request implies.

discovered requirements ÷ requested requirements

1 : 20 means for every thing you asked for, the system needs twenty more.

1 : 2040 discovered for 2 requested

AppUnik Readiness Index

ARI

How 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.

55out of 100

Blind Spots

BS

Layers that carry critical work the request never mentioned.

layers with at least one critical requirement and nothing requested

Where projects usually stall, overspend or get into trouble.

3Operations, Technology, Growth

Critical Path

CP

The minimum number of steps that must happen in sequence.

length of the longest chain in the dependency graph

No amount of parallel work makes the build shorter than this.

7 stepsFrom Offer and positioning to Follow-up sequence

Decision Gate

DG

Whether an unknown deserves to interrupt you.

⁴√(impact × risk × cost of reversal × uncertainty), each scored 1 to 5

Only unknowns scoring 3.5 or higher become questions. Everything else gets a recommended default.

2 passedScores 3.9, 3.9 (threshold 3.5)
Decision Gate, worked

"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.

Purpose72Experience56Operations44Technology43Trust50Growth43Intelligence82

Worked example

Architect

A blueprint ends in a build plan.

Roadmap

The dependency graph becomes a build order.

  1. 1
    Foundation
    Must exist before anything else works.
  2. 2
    Launch
    Needed to go live with real customers.
  3. 3
    Scale
    Makes it grow, cheaper to run, or harder to break.

Operating model

Every requirement has an owner who runs it.

  • People
    Judgement, relationships, approvals.
  • AI agents
    Repetitive judgement work, with a human escalation path.
  • Software
    Deterministic work your product does itself.
  • Providers
    Bought 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.

Principles

The rules every blueprint follows.

01
Outcome before implementation

We start with what has to be true for the business. The tech stack comes after that.

02
Relevance over volume

Every requirement must belong to this request. Generic filler is left out.

03
Ask only what changes the system

Defaults are chosen for you. Only decisions that change architecture, risk or cost come back to you.

04
Everything is traceable

Every requirement shows why it exists and what it depends on, back to the objective.

05
Plain and technical

Each item is written twice: for the founder and for the engineer.

06
Nothing is overwritten

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 system

Designed by AppUnik Super Intelligence. Built by AppUnik.