This page defines how an evaluator should enter the MZN case: from a 30-second thesis to a full NDA diligence room. It also prioritizes the few evidence artifacts that can change perception fastest.
Core position: because the IP portfolio and asset count are large, a full item-by-item review would require significant time. This document focuses on the highest-signal evidence and the primary asset clusters first. Other assets should be treated as sub-layers, derivatives, or portfolio extensions to be reviewed after the core proof chain is tested.
Important valuation boundary: the public IP/value page should be read as a diligence-orientation layer, not a sales sheet. Value bands and strategic-value logic are evaluator frames, not final asking prices or certified valuations.
The case should not be presented the same way to a journalist, Linas, an IP counsel, a technical reviewer, and a strategic partner.
These short versions are not the full proof. They are the entry points.
MZN is a phase-based AI-native company case. Phase 1 tested Mazzaneh in Iran with a real team, users, businesses, analytics, and transactions. Phase 2 was a deliberate one-person asset-formation phase. Phase 3 is the international diligence, legal, technical, and partner execution phase.
The question is not whether every asset is finished. The question is whether an incomplete but documented and interconnected portfolio can plausibly carry major strategic value under independent diligence — and whether the solo Phase 2 formation path can be proven.
Start with five proof artifacts: Phase 1 market proof, Phase 1 capital proof, Phase 2 solo timeline sample, top 20 asset maturity matrix, and patent-grade claim table. If these are credible, move to 90-minute review.
The asset surface is too broad for an initial review. The first pass should test whether the strongest evidence chain is real. If the core evidence holds, the rest of the asset portfolio can be reviewed by cluster.
These five artifacts can change an evaluator’s perception fastest because they test the hardest claims.
| # | Artifact | What it proves | Why it changes perception | Current readiness | Disclosure | Reviewer |
|---|---|---|---|---|---|---|
| 1 | Phase 1 MVP + Market Proof Bundle | Original Mazzaneh was not theory: product modules, users, sellers/businesses, analytics, transactions, and market testing existed. | Moves the case from “idea portfolio” to “founder has already operated in market.” | Available / needs reviewer bundle | Restricted / NDA | Product + data reviewer |
| 2 | Phase 1 Capital Deployment Proof | Founder personally funded the original execution, with approximate $700K capital deployment requiring financial reconstruction. | Shows risk taken, seriousness, and execution commitment before Phase 2 asset formation. | Available / needs ledger reconstruction | NDA financial | Accountant / financial reviewer |
| 3 | Phase 2 Solo Creation Timeline Sample | Sample of dated files, versions, prompts/session exports where available, subscription records, and artifact evolution. | Tests the central one-person formation claim directly. | Partially organized / provenance pack needed | NDA provenance | Independent evaluator / forensic reviewer |
| 4 | Top 20 Asset Maturity Matrix | Separates tested, demo, rebuild-ready, technical-spec, research-track, patent-candidate, and reserved assets. | Prevents the 330+ assets from feeling like an undifferentiated claim pile. | Mapped / top 20 extraction needed | Restricted | Product / strategy reviewer |
| 5 | Patent-Grade Claim Table + IP Route Map | Shows claim candidates, first dates, assets, disclosure level, likely route, and counsel-required next action. | Converts “IP claim” into an IP workstream that can be reviewed, narrowed, filed, licensed, reserved, or rejected. | Mapped at founder level / counsel pending | NDA / IP review | IP counsel / patent strategist |
The public IP page is useful because it already frames MZN as a diligence problem, not only a marketing narrative.
Public value bands should be treated as evaluator frames based on strategic questions, not final sales prices, investment terms, or certified valuations.
BioCode, HDTP, ISBP, security layers, technical details, and partner-sensitive concepts may require restricted or NDA-only review.
Public claim counts should be normalized by counsel. Portfolio-level and sub-portfolio claim counts may require professional IP reconciliation.
| IP Page Element | How to Use It | Evaluator Question | Next Evidence Step |
|---|---|---|---|
| Phase table | Anchor all claims to Phase 1, Phase 2, or Phase 3. | Which evidence belongs to which phase? | Build phase-coded evidence folders. |
| Six-question valuation framework | Use as strategic-value review lens, not final valuation. | Comparable exists? Buy/license path? Build cost? Time advantage? Risk reduction? Strategic premium? | Attach evidence to each valuation question. |
| Public/restricted/reserved distinction | Explain why not all details are public. | Is material absent or intentionally restricted? | Create disclosure map and NDA access rules. |
| Unified Brain / internal evaluation graph | Show that assets are not only listed; they are mapped against capability slots and cross-links. | Can the internal map connect HUAI baseline, asset catalog, capability slots, and review surfaces? | Provide non-public operating map sample under NDA. |
| Claim counts | Treat as founder/IP hypothesis until counsel normalizes. | Which are utility patent candidates, trade secrets, copyright/spec packages, or research paths? | Patent-grade claim table + prior-art workstream. |
Because the number of assets and IP directions is high, a complete review of every item is not realistic in the first pass. The correct method is to review primary clusters and highest-signal artifacts first, then expand into sub-assets and derivatives if the core claims hold.
The portfolio should be entered through primary clusters. Many smaller assets are sub-layers, derivatives, modules, or extensions of these trunks.
| Priority Cluster | Core Assets | Why It Comes Early | Proof Needed First | Reviewer |
|---|---|---|---|---|
| 1. AI-Commerce / Market Proof | Mazzaneh, Radar/Begir, Board, Pulino, Analytics. | Strongest product-first and TechCrunch-friendly entry; Phase 1 market data exists. | MVP proof, users/sellers/transactions, analytics, product flows, rebuild plan. | Product, data, commerce reviewer. |
| 2. AI Infrastructure / LLM Optimization | LLM Framework, Tokenizer, optimization frameworks, HUAI, ZOE mapping. | Defines technical and strategic AI-native depth beyond commerce. | Specs, benchmark seeds, claim table, comparison logic, capability slots. | AI infra / ML reviewer. |
| 3. GPU / Security | GPU Sentinel, ISBP, HDTP, security architecture, compliance logic. | Potential high-value enterprise/security path; sensitive details need controlled review. | Telemetry categories, detection logic, proof-first model, responsible disclosure map. | Security / infra expert. |
| 4. Evaluation / Governance System | Linas files, Diligence Q&A, Challenge, Evaluate, Master Map, evidence hierarchy. | Shows the founder designed review architecture, not just narrative. | Source hierarchy, claim-to-evidence map, 90-minute pack, risk register. | Lead evaluator / operator. |
| 5. Research / Future Intelligence | BioCode, Zoyan, foundational theory, human/AI interface, reserved research layers. | Potential long-term option value, but requires expert critique before commercial claims. | Research briefs, conceptual coherence, expert review path, disclosure boundary. | Research/scientific reviewer. |
This status map avoids both extremes: it does not pretend everything is independently validated, and it does not imply that evidence is absent.
| Evidence Area | Current Status | Likely Raw Artifacts | Disclosure Level | Next Action |
|---|---|---|---|---|
| Phase 1 MVP proof | Available; needs packaging into reviewer bundle. | Screenshots, app flows, module docs, demos, product materials. | Restricted | Create MVP proof bundle. |
| Phase 1 users / sellers / transactions | Available in raw/operational records; needs export and audit structure. | Analytics, database exports, seller/business records, transaction logs. | NDA | Prepare data sample + consistency checks. |
| Phase 1 capital deployment | Available but should be reconstructed into ledger format. | Transfers, invoices, contracts, expense records, bank/payment trails. | NDA financial | Create financial reconstruction table. |
| Phase 1 team/operation proof | Available; needs role classification and phase boundary notes. | Contracts, communications, task records, payroll/vendor documents. | NDA | Classify 27-person roles and output areas. |
| Phase 2 solo timeline | Partially organized; needs formal provenance package. | Dated files, drafts, metadata, subscription records, publication timestamps, session exports where available. | NDA provenance | Build month-by-month formation timeline. |
| 330+ asset index | Mapped; needs normalization, tagging, and evidence link fields. | Asset inventory, file paths, dates, categories, maturity labels. | Restricted | Add evidence link, maturity, and disclosure columns. |
| Top 20 maturity matrix | Needs extraction from full portfolio. | Top assets, maturity level, buyer path, proof status, next validation. | Restricted | Select top 20 and classify rigorously. |
| Patent-grade claim table | Mapped at founder level; counsel normalization pending. | Claim titles, specs, diagrams, first dates, disclosure levels, novelty hypotheses. | NDA IP | Prepare counsel-ready claim sheet. |
| Unified Brain / internal evaluation graph | Referenced; should be packaged as non-public reviewer sample. | Capability slots, baseline endpoints, cross-link surfaces, indexed MZN items. | NDA / restricted | Prepare sample graph and explanation. |
| Phase 3 legal-readiness plan | Mapped; requires qualified legal execution. | Risk register, legal access context, disclosure map, NDA logic, IP plan. | Review-ready | Engage counsel and professionalize data room. |
Different reviewers should not receive the same first package.
A media reviewer should not begin with IP claim tables. An IP counsel should not begin with the Substack narrative. A technical reviewer should not begin with the brand story. Compression means choosing the correct first door.
The first review should not force a final unicorn verdict.
After 90 minutes, an evaluator should not be asked to conclude: “This is worth $1B today.”
The proper decision threshold is: “Is this serious enough to justify formal independent review?”
If the top five evidence artifacts are credible, the case moves from visionary narrative to formal diligence candidate. If they are weak, the evaluator can stop early.
MZN is a phase-based AI-native founder case. Phase 1 was a real Mazzaneh MVP and market operation in Iran, funded personally and executed with a team. Phase 2 was a deliberate one-person AI-native asset-formation phase, producing a broad product/IP portfolio across multiple domains. Phase 3 is the professionalization stage: legal/IP review, technical validation, product rebuilds, pilots, partnerships, selective team formation, and commercialization. The claim is not that every asset is complete or legally finalized. The claim is that the strongest evidence chain may justify independent diligence into whether the combined, documented, interconnected portfolio can carry major strategic value, and whether the Phase 2 formation path can be proven as genuinely one-person.