Canonical routing model · May 2026

MZN should not be read linearly. It should be routed by reviewer role.

This master architecture defines how evaluators, media, investors, technical reviewers, skeptics, and partners should enter the MZN case without being forced through one fixed reading order.

Central question: can the documented, incomplete but interconnected MZN asset/IP stack survive independent diligence as a serious strategic-value candidate — and can the Phase 2 one-person AI-native formation path be proven through evidence?

Core principle

One site. Multiple valid entry points.

MZN is a live pitch deck, product map, IP/portfolio map, evidence-routing system, one-person-unicorn case, Phase 1 execution record, Phase 2 solo asset-formation record, and Phase 3 partner/legal/commercial entry map.

Do not force

No single linear reading path

Different reviewers should enter from the page closest to their role and then converge toward evidence, phase boundaries, and diligence logic.

Do not overclaim

Review-ready, not certified

The architecture supports provisional evaluation. It does not claim every product is complete, every IP claim is legally finalized, or valuation is certified.

Do connect

Every path returns to diligence

All routes should eventually return to claim boundaries, evidence hierarchy, independent review, and NDA/restricted materials where needed.

Landing copy: “You do not need to read everything at once. Choose the path closest to your role. Each path eventually returns to the same question: can the documented asset stack and one-person formation path survive independent review?”
Canonical entry pages

The pages that define how the case should be read.

These pages are shared anchors across several reviewer paths.

PageRoleUse when...Next pages
/pitch Compact structured evaluation entry, not merely an investor deck. The reader needs a short overview before deeper review. /analyse/phase-2/value-map/evaluate
/analyse How to read the public site. A reviewer misunderstands the site as a normal startup website or judges polish before substance. /mzn-stage2-claim-boundary/depth/value-map
/mzn-stage2-claim-boundary Phase and claim boundary foundation. Phase 1, Phase 2, and Phase 3 claims are being mixed. /phase-1/phase-2/phase-3
/evaluate Independent evaluation protocol. The question is how to evaluate without relying on founder persuasion. /challenge/qaDiligence Q&A
/depth Weight, not count. The portfolio is reduced to “330+ assets is just volume.” /value-map/ip
/value-map Portfolio cartography / value map. The reviewer needs to see how assets, layers, proof paths, and reserved materials relate. /ip/depthCompression Map
/ip IP/portfolio baseline and value-orientation layer. The discussion turns to assets, value, public vs restricted layers, and IP route. /value-map/phase-3Diligence Q&A
Role-based review paths

Choose the path closest to the reviewer’s role.

The purpose is not to hide complexity. It is to sequence complexity so the strongest evidence and most relevant context appear first.

Path A

Quick Orientation

For someone with 5–10 minutes who needs to understand the case before going deeper.

/pitch/analyse/mzn-stage2-claim-boundary/depth/value-map/evaluate/opu-skills

Path B

Product / Startup Reviewer

For TechCrunch, VC, accelerator, product, or market-entry reviewers. Start with Mazzaneh.

/mazzaneh/phase-1/ourincome/mazstory/board/pulino/radar/begir/analytic/mazstyle/zoyan/phase-3/partnership

Path C

Business Model / Commercial Reviewer

For revenue logic, buyer logic, monetization, sales, and Phase 1 commercial evidence.

/mazzaneh/ourincome/board/radar/analytic/ip/value-map/phase-3/partnershipSkills 2/6/8

Path D

AI / Technical / LLM Reviewer

For AI infrastructure, LLM company anatomy, technical architecture, optimization, security, and evaluation.

/llmframework/llm/huai/zoe/tokenizer/gpu/hdtp/isbp/evaluateDiligence Q&A

Path E

IP / Valuation / Legal Reviewer

For patentability, disclosure risk, value framing, public/restricted layers, and legal readiness.

/ip/value-map/mzn-stage2-claim-boundary/depth/phase-3/evaluateDiligence Q&ACompression MapSkill 12

Path F

One-Person Unicorn Reviewer

For one-person-unicorn / Linas-style analysis: role compression, solo boundaries, constraint-to-output ratio.

/one-person-unicorn/opu/opu-skills/roles/rank1/mzn-stage2-claim-boundary/phase-2Compression MapDiligence Q&A

Path G

Skeptic / Critical Reviewer

For readers who start with doubt. The path should invite objection, not suppress it.

/challenge/evaluate/qa/42-challenges/depth/rank1/analyseDiligence Q&A

Path H

Founder / Human Context

For media and readers who need to understand the founder, constraints, pressure, and role compression.

/mohammad/aboutus/pressure/roles/recognition-gap/opu/phase-1/phase-2

Path I

BioCode / Foundational Theory

For research, AGI, biology, philosophy, and long-term foundational-theory review.

/biocode/biocodeai/biology/philosophy/depth/ip/phase-3

Path J

Partner / Investor / Strategic Buyer

For partnership, licensing, strategic investment, or selecting the first Phase 3 entry asset.

/partnership/pitch/ip/value-map/phase-3Compression MapDiligence Q&A/mazzaneh/gpu/huai/zoyan/tokenizer

Path K

Media / Festival / Event Reviewer

For Web Summit, Slush, TechCrunch, WSA, media, event reviewers, or founder visibility.

/pitch/festivals/recognition-gap/mazzaneh/phase-1/phase-3/partnership/mohammad

Path L

Blog / Public Writing

For essays, public writing, theories, and media-thought leadership. Future /blogs should aggregate these pages.

/blog01/blog02future /blogs

Recommended main landing order

Where the Review Path section belongs.

The landing page should help the reader choose a path before exposing the full asset surface.

OrderSectionPurpose
1HeroHigh-impact positioning and entry.
2Choose Your Review PathRoutes reviewer by role before they get overwhelmed.
3Reader’s GuideExplains public site / pitch deck / evidence-layer logic.
4Read by Phase / Phase BoundarySeparates Phase 1, Phase 2, and Phase 3.
5EcosystemShows the system view before deep asset review.
6MazzanehProduct-first entry and Phase 1 market context.
7ZoyanWearable / assistant / consumer-AI extension.
8BioCodeFoundational theory and long-term research layer.
9LLM FrameworkAI/LLM strategic architecture flagship.
10HUAILLM company anatomy and capability baseline.
11IP PortfolioIP/value/asset layer with public/restricted guardrails.
12Independent Review / 12-Skill PackageConnects the live deck to review protocols, Q&A, and proof prioritization.
13Recognition GapExplains why recognition systems lag behind the output.
14Meet Mohammad / OPUFounder context and one-person-unicorn framing.
15PartnershipPhase 3 entry and selective partner route.
16FooterFinal routing, disclaimers, and key links.
Canonical rules

Equivalences, exclusions, and guardrails.

These rules prevent duplicate routes, broken expectations, and overclaiming.

Equivalences

Canonical duplicates

  • /portfolio = /ip
  • /value = /value-map
  • /purest-one-person = /purest
  • /opu-skills/opu
Do not route now

Not in current architecture

  • /growth-strategy — incomplete
  • /home — old
  • /img-preview — ignore
  • /landing_final_assets — asset folder
  • /assets_ecosystem_webp_v2 — asset folder
  • /risks-fair-play — empty
  • /story and /fullstory — overlap with About Us for now
Key guardrails

How to avoid misread

  • /ourincome is Phase 1 monetization evidence, not Phase 2 valuation base.
  • /pitch is compact structured evaluation entry, not merely investor deck.
  • Patent-grade does not mean granted patent.
  • Value frames are not certified valuations or asking prices.
  • Public pages orient; NDA/restricted layers verify.

Final architecture rule

Reviewers should not be asked to read everything first. They should be given the correct first door, then the correct evidence path.

Final routing statement

MZN is not a single-page startup pitch. It is a phase-separated, multi-domain, evidence-routed portfolio case.

The right evaluation method is not linear browsing. It is role-based entry, phase-boundary checking, proof prioritization, and independent diligence.

This master architecture should be used whenever the question is: “Which page should answer this doubt?”