Skip to main content
MZNEvidence Hub
Navigate
MZN · Public Evidence Hub

Route the claim to the evidence.

MZN's public evidence is distributed by phase, claim type and disclosure level. This hub provides a canonical entry point to the evidence and provenance routes that are currently public, while keeping controlled or sensitive material inside the appropriate diligence boundary.

Evidence availability is not the same as independent validation. Public records can support review; restricted material remains a diligence target until examined by the appropriate reviewer.
01 · Public evidence routes

Start with the layer you are evaluating.

Different MZN claims require different evidence objects. The routes below separate operating history, solo formation provenance, technical/research material and evaluation methodology rather than collapsing them into one undifferentiated data room.

Phase 1

Mazzaneh operating evidence

Bounded Shiraz MVP evidence, analytics and campaign records, source families, measurement boundaries and controlled verification routes.

Open Phase 1 Evidence →
Phase 2

Formation & provenance

Review the bounded solo AI-native formation period, method, claim boundary and portfolio provenance without importing Phase 1 operating history into the Phase 2 test.

Open Phase 2 →
IP / provenance

Public provenance boundary

Inspect how public provenance, asset families and controlled IP review are separated from patent, valuation or legal conclusions.

Open IP / Provenance →
Technical

Research & system routes

Navigate public technical and research material, including architecture-level work that may require specialist review rather than conventional startup evidence.

Open Research →
OPU

Solo provenance review

Review the one-person formation case through provenance, category definition, evaluation lenses and challenge routes.

Open OPU Provenance →
Diligence

Review architecture

Use the phase-aware review hub to distinguish public support, unresolved evidence gaps, controlled material and valid negative outcomes.

Open Review Hub →
02 · Evidence model

Public, controlled and reserved are different states.

The public site is an evidence-routing layer, not a substitute for a data room or specialist diligence. The disclosure state of an object should not be confused with its evidentiary strength.

Public orientationCanonical pages explain the claim, phase, maturity and appropriate review route.
Public evidenceSelected records, analytics, campaigns, timestamps, provenance objects and other materials can be inspected directly on public evidence pages.
Controlled substantiationSource files, logs, technical/IP records and specialist materials may require identity, NDA, legal, security or diligence controls before access.
Reserved materialSecurity-sensitive, patent-sensitive or unpublished mechanisms are not treated as public proof and are not assumed absent merely because they are not disclosed publicly.
Core boundaryRestricted is not validated. Public is not automatically proven. Missing public detail is not automatically absence. Each material claim should be evaluated against the evidence object appropriate to its phase, sensitivity and review standard.
03 · Reviewer routes

Move from orientation to the correct diligence target.

For a fast company-level read, start with Review. For the Phase 1 operating record, go directly to Phase 1 Evidence. For the one-person formation test, use OPU provenance and Phase 2. For technical novelty or architecture questions, use Research and the relevant system page.

Question-driven diligence

If the answer is not reproduced here, ask for the evidence required to test it.

The portfolio is too large—and parts of it too sensitive—to reproduce every source file inside one public surface. Review should expand according to the question: one artifact, one capability family, one provenance claim, or the full relevant corpus where necessary. Absence from the public page is not evidence of absence; controlled evidence is still not independent validation.

Request a capability family

Example: Training, Security, Data Governance, Tokenizer, GPU or HUAI.

Request a maturity proof

Ask what supports “documented,” “implemented,” “internally tested” or “operating.”

Define the validation test

Independent reproduction, benchmark, legal/IP review or pilot remains a separate diligence stage.