MZN Evaluation Entry · Document 1 of 3

How should MZN be proven before it is judged?

This page is the entry point for evaluating Mohammad Rahimi’s MZN case. It does not ask a reviewer to read the whole portfolio first. It defines the proof pathway: method, architecture, pressure test, then evidence room.

Core rule: do not begin with 50 files, a valuation number, a Crunchbase signal, or the one-person-unicorn question. Begin with the evaluation order, then test architectural coherence, then pressure-test objections, then open the evidence room.

PROOF
Method
Architecture
Pressure Test
Evidence Room
Phase Boundary
Proof Pathway

What would count as proof?

The case should be proven through a sequence, not through a single dramatic claim. Each layer answers a different question.

1
Method

How should the case be read?

Define the evaluation order, phase boundaries, and proportional reading method before judging any asset or weakness.

/start
2
Architecture

Is the portfolio coherent?

Show how Phase 1 product signals, Phase 2 AI-native architecture, and Phase 3 Zoyan convergence connect.

/evidence-graph
3
Pressure Test

Can objections survive?

Answer the hardest questions around theory-only risk, phase mixing, solo provenance, Zoyan, valuation, and evidence.

/hardquestion
4
Verification

What evidence supports it?

Only after the trio, open product, IP, BioCode, HUAI, technical, Crunchbase, OPU, and Phase 3 material selectively.

/evidence-room
The Evaluation Trio

Three documents first. Everything else second.

The trio turns a large portfolio into a reviewable system: method, architecture, pressure test.

1
Procedural Layer

Evaluation Order

This page. It explains how to read the case, how to avoid misreading scale, and why the one-person question comes after asset scale and reconstruction cost.

Open /start
2
Architectural Layer

Evidence Graph

Shows why MZN is not a scattered pile of projects or theory-only writing. It maps executed Phase 1 signals and Phase 2 architecture toward Zoyan.

Open /evidence-graph
3
Defensive Layer

Hard Questions

Answers the strongest objections conservatively: Phase 1 vs Phase 2, solo formation, Zoyan readiness, IP status, value, and what would defeat the claim.

Open /hardquestion
Fast path: 15 minutes for screening. Full path: about 90 minutes. If the trio survives, the broader portfolio becomes the evidence room.
Evaluation Stages

The proof sequence has six stages.

A fair review should not jump directly to “is this a one-person unicorn?” It should first establish what is being evaluated and what scale of evidence is required.

1

Scale

What is the size, breadth, and depth of the asset architecture?

2

Review Resources

What kind of panel, expertise, evidence access, and time would proper diligence require?

3

Novelty

Is this a familiar startup pattern or a new AI-native formation category?

4

Strategic Value

Could the eligible architecture plausibly carry major value after independent diligence?

5

Reconstruction Cost

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

6

Solo Formation

Only then ask whether eligible Phase 2 formation can be proven as materially one-person.

Phase Boundaries

What is being proven — and what is not?

The proof path depends on not mixing Phase 1, Phase 2, and Phase 3.

Layer
How to read it
Phase 1: Mazzaneh execution
Product, market, MVP, team execution, users/sellers/signals, and constraint context. It is not the solo Phase 2 claim.
Phase 2: solo AI-native formation
The bounded one-person claim: AI-native asset/IP formation, architecture, documentation, and review package under constraint.
Phase 3: professionalization
Future rebuild, legal/IP/privacy review, technical validation, partners, pilots, U.S. execution path, and team scaling.
Zoyan
Architectural convergence goal and Phase 3 productization path, not a deployed-product claim in Phase 2.
Evidence Room

After the trio, open the evidence selectively.

The evidence room is not the first read. It is the second-stage verification layer.

Product

Phase 1 / Mazzaneh

Mazzaneh, modules, product history, market evidence, income model, users, sellers, and signal logic.

Open room
Architecture

HUAI / LLM / BioCode

Human-grounded AI, capability mapping, LLM anatomy, BioCode AI, biology, and architecture candidates.

Open room
OPU

Solo Formation

Phase 2 one-person route, role compression, Linas-style skills, provenance, and reconstruction logic.

Open room
Phase 3

Zoyan / Partnership

Rebuild, validation, legal review, AI lab dialogue, pilots, partnership route, and execution plan.

Open room
Next Read

Now test whether the architecture is coherent.

The next page is the Evidence Graph: it answers whether MZN is a connected architecture or a pile of unrelated projects.

Method Architecture Pressure Test Evidence Room