Document 1 of 3 · Procedural layer

How should MZN be read before it is judged?

This page calibrates the evaluation method. MZN should not be read as a normal single-product startup page, a linear website, or a self-certification claim.

1/3
Trio position
6
Stages
2
Core tests
Open this layer → Evidence Room
START
Method
Scale
Novelty
Value
Proof
Procedural Layer

First, calibrate the evaluator’s lens.

MZN is not evaluated correctly by default single-product instincts. This page defines the reading order before any asset, flaw, ranking, or one-person claim is judged.

1
Procedural

Evaluation Order

You are here. This layer explains how the portfolio should be read.

/start
2
Architectural

Evidence Graph

Shows whether MZN is coherent or scattered, and how the layers converge into Zoyan.

/evidence-graph
3
Defensive

Hard Questions

Answers the strongest objections conservatively after the method and map are understood.

/hardquestion

Principle: read method before architecture, and architecture before objections. If the sequence is reversed, the case can look defensive, scattered, or overlarge before the evaluator has the correct frame.

Six-stage evaluation order

The one-person question comes last, not first.

Before asking whether Phase 2 could be a one-person-unicorn candidate, first establish the scale, resources required to evaluate it, novelty, market value, and reconstruction cost.

1

Scale

What is the size and breadth of the asset architecture?

2

Evaluation Resources

What kind of panel, expertise, and evidence access are required?

3

Novelty

Does the case represent a new category or only a familiar startup pattern?

4

Market Value

Could the eligible architecture plausibly carry strategic value after diligence?

5

Reconstruction Cost

What would it cost to recreate the same portfolio, time, evidence, and architecture?

6

One-Person Question

Only after scale is understood: can the eligible Phase 2 formation path be proven solo?

How to weigh weaknesses

Flaws should be measured, not inflated.

A serious review does not ignore defects. It asks whether a defect is local, systemic, proportional to the case, and what remains after it is removed.

Principle 1

Proportionality

Is the flaw consistent with a one-person, multi-domain, constraint-heavy formation path?

Principle 2

Containment

Is the defect local to one file or claim, or does it weaken the whole architecture?

Principle 3

Scale-Proportion

After removing weak pieces, does a serious, coherent, review-worthy asset architecture remain?

Final principle: maximum pressure on both sides of the scale. Judge the assets by the strongest standards; find the weaknesses with the hardest challenges; then weigh both.

Next Step

Continue to the architecture layer.

After the method is clear, the next document shows whether the portfolio is coherent or scattered.

Open Evidence GraphOpen Hard Questions