Three distinct phases. Different team structures, different funding profiles, different operating conditions. The one-person claim applies only to Phase 2.
The MZN portfolio was developed across three clearly separated phases. Each phase has a different team structure, funding profile, operating condition, and relationship to the one-person claim. The one-person claim applies only to the defined solo build phase — Phase 2. The other two phases are context, not claim.
The transition begins when team-based building ends and the founder starts operating entirely alone through AI chat collaboration, with no human co-builder, contractor, or collaborator. The transition is binary, not gradual: the moment a team member contributes to a build artifact, that artifact belongs to Phase 1 context, not Phase 2 claim.
The transition begins when human team members, formal partners, external execution resources, or institutional infrastructure are introduced for implementation, launch, or scale. As of May 2026, this transition is in its early stage — the founder has relocated outside Iran, but the solo-build claim covers the assets formed during Phase 2 only.
The review must distinguish between solo-built outputs (included), team-built outputs (excluded), and contextual elements that explain the case but are not part of the one-person claim. Every category below is explicitly assigned. Boundary clarity is the prerequisite for any honest evaluation.
| Category | Examples | Status |
|---|---|---|
| LLM Architecture | ZOE AI stack, Multi-Brain, DCA, UIOP, OFRP, Suprompt, Tokenizer System | Solo-built |
| Security Protocols | Protocol sets, behavioral defense layers, GPU Sentinel metrics and detection logic | Solo-built |
| Foundational Theory | BioCode and its patent-claim structure (10+ claims) | Solo-built |
| Patent Specifications | HDTP (12+ claims), BioCode (10+), Tokenizer (6+) — SHA-256 verified, blockchain timestamped | Solo-built |
| Technical Documentation | 3,000+ pages in English (L2), architecture notes, specifications, summaries | Solo-built |
| Web Infrastructure | 22+ pages on mzncompany.com, interface design, image creation, server-level deployment decisions | Solo-built |
| Strategic Documents | Partnership proposals, comparative analyses, evaluation materials, evaluator-grade frameworks | Solo-built |
| Operational Management | Festival applications, correspondence, accounts, publishing, coordination tasks | Solo-built |
| Architectural Convergence Records | Timestamped records of independent concepts that later showed similarity to features shipped industry-wide. Framed as validation, not IP claim. | Solo-documented |
| Category | Reason for Exclusion | Status |
|---|---|---|
| Mazzaneh live platform & user base | Built in Phase 1 with a 27-person team. Context only. | Excluded |
| Phase 1 team contributions | Not solo-built by definition. | Excluded |
| Future team activity | Belongs to Phase 3, not the solo build phase. | Excluded |
| Future institutional or VC funding | Not part of the current solo-build claim. | Excluded |
| Future legal filing via outside counsel | Requires non-solo execution resources. | Excluded |
| Future PR or formal launch campaigns | Post-solo execution layer. | Excluded |
| Category | Role in Review | Status |
|---|---|---|
| Mazzaneh as a live product | Shows prior ability to conceive and ship at scale — predates the solo phase. | Context only |
| Pre-Phase-2 entrepreneurial history | Provides founder background and execution track record. | Context only |
| Festival and award recognition | Shows external interest and quality signals — based on earlier outputs. | Context only |
| Institutional correspondence | Supports narrative of external interest and blocked access. | Context only |
This section is definitional, not defensive. It explains why the solo phase was intentionally kept separate rather than blended into a broader and less evaluable company story. The boundary exists so reviewers can evaluate one specific question cleanly: what did one human plus AI collaboration actually produce, under these constraints, in this window?
The solo phase was intentionally bounded so reviewers can evaluate what one human plus AI collaboration actually produced, without mixing team-built and solo-built outputs. If team contributions blended with solo work, the review question would become unanswerable.
If human contributors entered the build phase, the one-person claim would become structurally ambiguous. The bounded solo phase prevents that ambiguity. The boundary is not a marketing choice; it is a definitional requirement for the claim to be falsifiable.
The case concerns not just what was built, but whether deep AI conversation alone can function as a one-person build methodology under real constraints. The methodology itself is part of the claim — future founders facing similar conditions need to know whether this path produced reproducible value.
Some constraints were imposed by external reality (sanctions, regional conflict, no local ecosystem). Others were deliberately retained in order to preserve the clean boundary of the solo-build claim (no API, no agents, no contractors). Both kinds of constraint are part of the test.
The one-person claim concerns asset formation, not perpetual solo operation. This distinction is essential: if “one-person” were defined as “must remain solo forever,” the category would be meaningless. The relevant question is whether the core body of work was created during a bounded solo phase. Everything that follows belongs to the scale phase by definition.
The solo phase covers the creation of frameworks, protocols, theories, documents, structure, and initial system logic. These assets exist before any future launch team exists. The one-person claim is about creation and formation, not about never requiring help afterward.
Legal formalization, patent prosecution, lab work, productization, launch, market entry, growth, and institutional partnerships may require teams, lawyers, engineers, operators, and capital. Needing execution resources after asset formation does not invalidate the fact that the assets were originally formed during a solo build phase.
An architect may design a building alone while its construction later requires hundreds of people. The need for builders does not make the architectural design less solitary in origin. The architectural drawings exist before the first foundation is poured; the team executes the drawings; the credit for the architecture stays with the architect, even after the building is full of people who did not exist at the design stage.
In this case, Phase 2 corresponds to the design and asset-formation phase; Phase 3 corresponds to execution, implementation, and scaling. The IP exists before the team exists. The future team's role is execution, not original creation. The timeline can be independently tested through SHA-256 hashes, blockchain timestamps, and provenance records produced during Phase 2.
Before any asset-level evaluation, an evaluator should answer these five questions about boundary clarity and claim structure. If the boundaries are not clear, the asset-level review will produce noise. If the boundaries are clear, the asset-level review can proceed cleanly.
If these five questions resolve cleanly, the next-stage asset map can use the following structure to categorize all Phase 2 assets:
Top-level categorization across the 8 documented domains: AI Architecture, Security Protocols, Theory, Tokenizer, Infrastructure, Commerce, Documentation, and Architectural Convergence.
Each pillar contains specific modules: e.g., AI Architecture contains ZOE, Multi-Brain, DCA, UIOP, OFRP, Suprompt as distinct modules.
Documented architectural specifications with patent-grade detail: HDTP (12+ claims), BioCode (10+ claims), Tokenizer System (6+ claims).
Original technical contributions where prior art search shows no equivalent: e.g., Hourglass Data Teleportation Protocol, BioCode theoretical framework.
Conceptual work that grounds the architecture: BioCode theory, evaluator frameworks, cross-model evaluation methodology.
Approximately 40% of the portfolio is held in Restricted (~25%) and Reserved (~15%) layers. Available under coordinated correspondence and partnership-tier engagement, not as public artifacts.
Each asset is classified by maturity: Live (in production) · Production-Ready (deployable) · Specification (architectural design) · Theory (conceptual) · Invention (novel concept) · Security (protocol layer) · Evidence (proof artifact).
This is a structural foundation file. It is intended to be loaded before asset-level or valuation-level analysis so that category boundaries are clear before content review begins. It exists to establish boundaries, not to make value claims.
A multi-stage evaluation framework places this document at Stage 02. Each stage builds on the previous; this stage establishes boundaries that all later stages depend on.
Boundary clarity is the prerequisite for honest evaluation.
Before asset-level review — this is the floor.
The phase distinction is not a marketing choice. It is a definitional requirement. The claim is bounded so it can be evaluated honestly — including the possibility of an honest negative verdict.