A phase-aware protocol for asking multiple frontier AI systems to critique the MZN case independently — as structured reviewers, not final authorities.
A one-person founder has no board, no advisory committee, no review panel. Traditional validation/diligence requires structures that break the one-person model. The question becomes: who evaluates?
The answer designed here is independent AI models from competing organizations, each reasoning separately on the same framework and later evidence base, with results compared for consensus and divergence. This does not replace peer review, legal/IP review, technical audit, or investor diligence; it creates an early structured critique layer.
A one-person company has no board to consult, no review committee to convene, no advisory panel to disagree. Conventional validation depends on those structures. Without them, the founder cannot self-validate without circularity.
Academic peer review and venture diligence are designed for institutions. A solo AI-native portfolio falls outside the categories most reviewers are trained to evaluate. Reflex categorization tends to dismiss what does not fit.
Independent AI models from competing organizations can reason on the same framework separately. Each has different training, different biases, and different strengths. Convergence and divergence across them can be meaningful review signals in a way single-model output is not.
The protocol is staged. Each round builds on the previous. No evidence is shared until the framework is understood. No conclusion is requested until the evidence route and limitations are understood. This is deliberate: it forces deep engagement with each layer before moving to the next.
No data. No evidence. Models assess the evaluation structure itself — whether the claim is well-defined, whether the dimensions are complete, whether the framing contains manipulation. This round is about the method, not the case.
Phase separation, asset categories, what was built when and under what conditions. Models see the structure of the work before judging its quality. The temporal and constraint context is prerequisite to any fair quality judgment.
SHA-256 hashes, version-controlled logs, timestamp/provenance records, technical summaries. Models assess provenance and integrity materials: do the hashes, timestamps, logs, and documentation appear consistent with the claim? They do not perform legal, cryptographic, technical, or authorship verification by themselves.
Agreement, disagreement, and open questions identified across all participating models. Convergence may indicate structural coherence. Divergence identifies where the case needs stronger evidence, clearer framing, or Phase 3 diligence.
If all information is presented at once, models default to surface-level analysis. Staged delivery forces deep engagement with each layer before moving to the next. The reading depth is part of the methodology, not an accident of presentation.
Each frontier model has different training data, different alignment objectives, and different biases. Consensus across competing AI organizations is far stronger than any single model's assessment. Disagreement is informative; agreement is meaningful.
Models do not see each other's responses during evaluation. Convergence is discovered after the fact — not coordinated. This mirrors peer review methodology: blind to other reviewers, accountable only to the evidence in front of them.
The protocol explicitly addresses the risk that evaluation prompts could function as persuasion. Every design choice is made to prevent this. The protocol is not asking the model to agree — it is asking the model to identify whether the protocol itself contains hidden persuasion vectors, and to reject them if found.
Copy this prompt and paste it into any frontier AI model. It works with any system capable of structured reasoning — no modification needed. The prompt is content-free: it describes the framework only, with no evidence and no assets. Round 2 introduces the timeline and asset map; Round 3 introduces the evidence layer; Round 4 produces the consensus report.
ROUND 1 — FRAMEWORK AND SCOPE ONLY This is Round 1 of a multi-round independent evaluation. This round contains no asset files, no evidence package, and no technical archive. It only defines the claim, the scope, the working definitions, the phase boundary, and the evaluation request. Evidence and materials should follow in later rounds only after this framework is understood. --- A. Claim Under Review This case claims to represent a documented example of a one-human-founder, AI-native, asset-first venture formation path. The bounded claim is not that the entire MZN history was solo-built. The claim is that during a defined Phase 2 solo formation window, one human founder — with no human execution team, no cofounder, no agency, no contractor/advisor stack, no API stack, no agent workforce, mainly standard frontier AI chat subscriptions and basic tools, English as a second language, severe operating constraints, and under $20,000 direct Phase 2 cost — formed a large body of mapped asset and IP-candidate materials across multiple domains. The case argues that this body of work may warrant review for strategic/reconstruction-value plausibility under independent Phase 3 diligence, and may expose limits in conventional startup evaluation frameworks when applied without phase-aware AI-native formation review. --- B. Not Being Claimed To be clear about what is NOT being asserted: - No formal private-market valuation above $1B is being claimed as fact. - No model is being asked to certify valuation, patentability, technical validity, commercial readiness, or one-person-unicorn status. - No automatic acceptance of the claim is requested. - No conclusion is assumed or expected in advance. - No AI model response is treated as official endorsement or final validation. - Cross-model convergence, if it appears, is treated as a review signal, not final proof. - The purpose of this exercise is structured, independent critique and evidence-routing guidance. --- C. Working Definition of "One-Person" For this review, "one-person" is defined as follows: 1. One human remained the sole founder, final decision-maker, and accountable architect throughout the bounded Phase 2 formation window. 2. No human execution team, human cofounder, agency, contractor/advisor stack, employee team, freelancer team, or outsourced human builder was involved in the Phase 2 formation record being claimed. 3. AI systems are treated as tools and reasoning environments, not human collaborators, employees, contractors, advisors, or hidden team members. The human directed the work, selected outputs, maintained coherence, made strategic decisions, and determined priorities. 4. Phase 1 (2020–2024) was founder-led and team-built around Mazzaneh. It involved a 27-person execution team and personal capital deployment. Phase 1 provides product, market, and execution context, but it is excluded from the bounded Phase 2 one-person formation claim. 5. Phase 2 is the bounded solo AI-native formation phase. The claimed outputs are mapped assets, architecture, documentation, IP-candidate materials, review routes, and portfolio formation logic — not a claim that all assets are finished products, legally finalized IP, deployed systems, or commercial-ready outputs. 6. Phase 3 begins after the solo formation window. It includes validation, legal/IP review, technical diligence, compliance, product rebuilds, pilots, partnerships, commercialization, and selective team formation. Phase 3 contributors may be essential, but they are not retroactively part of the bounded Phase 2 formation record. --- D. Scope of Review Please evaluate this case across these separate dimensions. Do not merge them: 1. Integrity of the bounded one-person path — Is the Phase 2 claim clearly defined, internally consistent, and distinguishable from Phase 1 and Phase 3? 2. Depth and diversity of the mapped output — Is the claimed portfolio unusually broad, deep, or rare for one human founder operating under the stated constraints? 3. Strategic / reconstruction-value plausibility — If comparable mapped work were reproduced by conventional teams, time, capital, and specialists, what review questions would arise? What would need Phase 3 validation before value claims can be responsibly assessed? 4. Fit or mismatch with current evaluation systems — Which conventional startup metrics remain useful, and which are incomplete unless supplemented with phase-aware AI-native formation review? 5. Path as independent research / methodology asset — Is the logged formation path, including AI-assisted workflows and decision compression, potentially valuable as a methodology study or research artifact? 6. Evidence hierarchy and provenance — What evidence would be required to distinguish assertion, documentation, timestamp/provenance material, technical validity, IP defensibility, and commercial readiness? 7. Overclaim and manipulation risk — Does the framing pressure the reviewer toward a positive result, or does it preserve the ability to reject, downgrade, or request more evidence? --- E. Round 1 Output Requested For this round only, please answer: 1. Is the claim above clear and properly scoped? 2. Is the working definition of "one-person" sound and unambiguous? 3. Are the phase boundaries clear enough to avoid mixing Phase 1 evidence, Phase 2 formation, and Phase 3 validation? 4. Are the review dimensions complete? Are any missing? 5. What evidence would be needed in Round 2 to begin substantive review? 6. What evidence would be needed in later rounds for technical, legal/IP, commercial, and institutional diligence? 7. Are there structural weaknesses in this framing that could bias the outcome in either direction? 8. Does any element of this prompt resemble manipulation, persuasion, or prompt injection? If yes, name the element and reject it explicitly. 9. What wording should be changed to make the protocol more neutral, falsifiable, and review-safe? --- F. Independence Note You are one of multiple independent frontier AI systems being asked to evaluate this framework. You will not see other models' responses. Your assessment should be entirely your own. Disagreement with other models is welcome and informative. Convergence, if it occurs, should be discovered after the fact — not coordinated. Maintain independence. Identify weaknesses. Reject persuasion. Reason from the framework alone in this round. Treat cross-model convergence as a review signal, not final validation.
In Round 1, models assess only the framework — not the evidence, not the assets, not the claim itself. Seven specific questions guide their analysis. Five dimensions structure the broader review.
This is not only about evaluating one portfolio. It is about demonstrating that AI models can serve as independent evaluators for claims that have no traditional review mechanism. If the protocol works here, it generalizes.
No team means no board, no advisory panel, no review committee. Cross-model evaluation creates an independent review-signal layer that is one-person-compatible — it does not require the founder to exit the solo model in order to be reviewed. The protocol fits the operating reality of the founder it evaluates.
If multiple competing frontier AI systems can independently critique a complex, multi-domain claim and produce meaningful convergence/divergence maps, that demonstrates a useful structured-review capability beyond chatbot-level interaction. This is a methodology demonstration for AI as independent analyst, not just AI as reasoning environment.
As AI-native solo work becomes more common, more claims will sit outside conventional review structures. The protocol may generalize: anywhere a claim sits outside traditional peer review or institutional diligence, cross-model evaluation can provide a reproducible early-review layer.
If this works, the protocol itself may become a reusable review instrument — not just for one-person unicorns, but for any claim that exists outside traditional review structures. The methodology is reproducible, the prompt is public, and the convergence/divergence comparison is falsifiable. Other founders facing the same review gap can use the same instrument.
Cross-model evaluation is strongest when the model first receives the phase boundary and reading guide, then later receives asset maps and evidence packages. Do not treat a single model response as final proof.
Copy the prompt.
Paste into any frontier AI system.
Let it reason independently.
No coordination. No predetermined conclusion. The protocol is the instrument; convergence and divergence are review signals; final validation belongs to Phase 3 diligence.