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?
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.
Different reviewers should enter from the page closest to their role and then converge toward evidence, phase boundaries, and diligence logic.
The architecture supports provisional evaluation. It does not claim every product is complete, every IP claim is legally finalized, or valuation is certified.
All routes should eventually return to claim boundaries, evidence hierarchy, independent review, and NDA/restricted materials where needed.
These pages are shared anchors across several reviewer paths.
| Page | Role | Use 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 |
The purpose is not to hide complexity. It is to sequence complexity so the strongest evidence and most relevant context appear first.
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
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
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
For AI infrastructure, LLM company anatomy, technical architecture, optimization, security, and evaluation.
/llmframework/llm/huai/zoe/tokenizer/gpu/hdtp/isbp/evaluateDiligence Q&A
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
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
For readers who start with doubt. The path should invite objection, not suppress it.
/challenge/evaluate/qa/42-challenges/depth/rank1/analyseDiligence Q&A
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
For research, AGI, biology, philosophy, and long-term foundational-theory review.
/biocode/biocodeai/biology/philosophy/depth/ip/phase-3
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
For Web Summit, Slush, TechCrunch, WSA, media, event reviewers, or founder visibility.
/pitch/festivals/recognition-gap/mazzaneh/phase-1/phase-3/partnership/mohammad
For essays, public writing, theories, and media-thought leadership. Future /blogs should aggregate these pages.
/blog01/blog02future /blogs
The landing page should help the reader choose a path before exposing the full asset surface.
| Order | Section | Purpose |
|---|---|---|
| 1 | Hero | High-impact positioning and entry. |
| 2 | Choose Your Review Path | Routes reviewer by role before they get overwhelmed. |
| 3 | Reader’s Guide | Explains public site / pitch deck / evidence-layer logic. |
| 4 | Read by Phase / Phase Boundary | Separates Phase 1, Phase 2, and Phase 3. |
| 5 | Ecosystem | Shows the system view before deep asset review. |
| 6 | Mazzaneh | Product-first entry and Phase 1 market context. |
| 7 | Zoyan | Wearable / assistant / consumer-AI extension. |
| 8 | BioCode | Foundational theory and long-term research layer. |
| 9 | LLM Framework | AI/LLM strategic architecture flagship. |
| 10 | HUAI | LLM company anatomy and capability baseline. |
| 11 | IP Portfolio | IP/value/asset layer with public/restricted guardrails. |
| 12 | Independent Review / 12-Skill Package | Connects the live deck to review protocols, Q&A, and proof prioritization. |
| 13 | Recognition Gap | Explains why recognition systems lag behind the output. |
| 14 | Meet Mohammad / OPU | Founder context and one-person-unicorn framing. |
| 15 | Partnership | Phase 3 entry and selective partner route. |
| 16 | Footer | Final routing, disclaimers, and key links. |
These rules prevent duplicate routes, broken expectations, and overclaiming.
Reviewers should not be asked to read everything first. They should be given the correct first door, then the correct evidence path.
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?”