Evidence Room · Verification layer

After the trio, open only the evidence you need.

This page is not the entry point and not a final proof layer. It is the organized evidence-routing room for staged follow-up review after the Evaluation Trio.

Core URLs

Evidence routes

Final verdicts

Open this layer → Evidence Room

ROOM

Product

HUAI

BioCode

Phase 3

Evidence Room

Not the entry point. The verification layer.

The recommended entry is the Evaluation Trio: /start, /evidence-graph, and /hardquestion. This page opens the right evidence only after a reviewer knows what they want to verify.

Gateway

Evaluation method, orientation, and reading order.

/start /evidence-graph /hardquestion

Product / Phase 1

Mazzaneh product, market, income, and execution context.

/mazzaneh /phase-1 /ourincome /mazstory

Human-Signal Modules

Intent, attention, identity, wallet, analytics, and preference signals.

/radar /begir /board /pulino /analytic

Architecture

HUAI, LLM framework/anatomy, and AI-native capability mapping.

/huai /llm /llmframework

BioCode / Theory

Human-grounded AGI, limitation, trust, salience, and biological intelligence framing.

/biocode /biocodeai /biology /philosophy

Technical Layers

Tokenizer, GPU Sentinel, ZOE, ISBP, HDTP, and technical review candidates.

/tokenizer /gpu /zoe /isbp /hdtp

IP / Value / Legal

IP baseline, value map, weight-not-count analysis, and review boundaries.

/ip /value-map /depth /qa

One-Person Route

Separate Phase 2 solo formation, roles, skills, and OPU review path.

/one-person-unicorn /opu /opu-skills /phase-2

Phase 3 / Partnership

Zoyan, rebuild, review, pilots, partnerships, and professionalization.

/zoyan /phase-3 /partnership /phase-3-partner-path

Evidence routing

A public website is not a data room.

The Evidence Room separates what can be understood publicly from what should be reviewed through qualified, staged, and where appropriate confidential diligence. Non-public does not mean absent; it means the reviewer must use the correct evidence route.

Phase 1 · Product / execution

Mazzaneh operational evidence

Mazzaneh is the Phase 1 execution anchor, not the Phase 2 one-person proof. A qualified product review may inspect the operational record where access is possible.

Product/app/platform records and historical operating evidence
Server-side data, Google Analytics, transactions, user/business metrics, and operational records
Iran/sanctions/infrastructure caveat: some records may require controlled review rather than simple public access
Purpose: verify execution/product/market context, not count Phase 1 as solo-built Phase 2 value

Phase 2 · Solo provenance

Formation trail and authorship route

The one-person claim concerns eligible Phase 2 formation: one human directing, selecting, integrating, and governing the work without a human formation team.

Artifact sequence, timestamps, hashes, document history, and source hierarchy
Selected/raw AI conversation logs as provenance material under controlled review
No-team / no-contractor / no-advisor / no-agency / no-agent-workforce / no-API boundary evidence
Self-authored documentation is expected as a first provenance layer; it is not self-validation

Technical / IP · Controlled review

Restricted architecture and IP-sensitive materials

Some assets cannot responsibly expose their protectable or security-sensitive core in a public page. They should be treated as diligence targets, not public proof and not absence.

BioCode, HUAI, GPU Sentinel, tokenizer, ISBP, HDTP, ZOE/security, and related technical/security layers
Professional technical, IP/prior-art, security, and legal review required before strong conclusions
Patent-grade candidates do not mean granted patents, allowed claims, or certified IP
Purpose: determine novelty, substance, feasibility, protectability, and responsible disclosure boundaries

Recognition / platform signals

External signals are reasons to inspect, not verdicts

Recognition signals should be checked in context and by date. They do not replace technical, product, IP, or provenance diligence.

Crunchbase: not final validation, endorsement, certification, valuation, or proof
Under severe constraints and without conventional amplification, a sustained Top 10 / Top 5 all-category signal should be treated as a reason to inspect the underlying links, outputs, data, and documentation
Other recognitions/festivals/invitations should distinguish applied, selected, nominated, invited, or awarded status
Purpose: identify external platform visibility and review signals, not certify the case

Methodology page ≠ Evidence Room

The Paradox-Aware Review Manual classifies review errors and evaluation tensions. This Evidence Room routes artifacts and diligence paths. A methodology page should not be faulted for not being a data room; a data room should not be replaced by methodology.

Scoped outcomes

A limited review should produce a limited conclusion.

Public-only review can identify what is visible, what is unresolved, and what needs staged access. It should not convert restricted evidence, review-capacity limits, or single-pass uncertainty into a full-case verdict.

Not proven publicly

A valid public-layer conclusion. It means the public page does not establish final proof; it does not mean the underlying evidence failed.

Requires restricted diligence

Appropriate for raw logs, security/IP-sensitive assets, provenance materials, and operational records that are not suitable for full public disclosure.

Product verification needed

Appropriate for Phase 1 Mazzaneh operating records, user/business metrics, transactions, analytics, and server data.

Technical/IP uncertainty

Appropriate until qualified specialists review BioCode, HUAI, tokenizer, GPU Sentinel, ISBP, HDTP, and other reserved technical layers.

Structural refutation

Requires a load-bearing failure: for example, proven human team formation inside eligible Phase 2 assets, failed provenance trail, false operational evidence, or trivial/copy technical assets after expert review.

Documentation hygiene

Older counts, cached wording, dated platform snapshots, duplicate files, or stale-version mismatches should be corrected, but they are not structural collapse unless tied to a load-bearing claim.

Reviewer certainty must match reviewer access.

A single-pass public review may be useful as a triage layer, but it cannot become a full-case verdict for a 330+ mapped-asset, phase-separated, multi-domain portfolio. The model or reviewer’s inability to inspect the full evidence structure is a review limitation, not evidence that the structure is absent.

Evidence discipline

The broader portfolio should support second-stage verification.

Before the trio, fifty files compete for attention. After the trio, each file has a role: product evidence, architecture detail, IP review, theory, technical review, or Phase 3 diligence.

Many pages compete to be the first read.

Three documents create the entry sequence.

Evaluator may feel overwhelmed or misread the scale.

Evaluator has method, architecture map, and objections layer.

Specific files appear scattered.

Specific files become evidence for a known layer.

Next Step

Return to the Evaluation Trio.

A reviewer should enter through /start, understand coherence through /evidence-graph, pressure-test through /hardquestion, then open this room.

Start Review Evidence Graph Paradox Manual Partner Build Path