Portfolio Review Tree · Evaluator Surface

Every Asset.
Its Depth. Its Evidence Route.
Reviewer Judgment.

This page is not a normal product sitemap. It is a public tree view of the portfolio, designed for evaluators who want to see where the public layers, technical layers, newer additions, and proof/evidence routes sit. It does not assign a final value to the portfolio. The appropriate question is whether the visible structure, evidence routes, and restricted-review targets justify deeper diligence — and what qualified reviewers would value after that diligence.

Open the Portfolio Tree Use /evaluate
330+
Mapped assets / sub-assets
8
Canonical portfolio domains
22+
Patent-grade candidates
23
Security protocols
40%+
Restricted / staged-review layer
Review guardrail: this page uses public navigation pillars for readability, while the canonical portfolio is mapped across 8 domains, 330+ mapped assets/sub-assets, and 22+ patent-grade candidates. “Patent-grade” means prepared or identified for professional IP review; it does not mean granted patent, allowed patent, certified valuation, or independently validated IP. Final value is left to qualified reviewers after technical, legal/IP, commercial, and provenance diligence.

How To Use This Page

This is a review tree, not a valuation claim.

Open each pillar, inspect the modules, follow the routes, and use the prompts below to pressure-test any area independently. The newer additions — tokenizer system, GPU Sentinel, ISBP-related protocol layers, evaluator surfaces — are included because the earlier map no longer reflected the actual shape of the portfolio. The page is designed to support reviewer judgment, not to pre-set valuation.

1

Expand the pillars below. Read the portfolio as a structured system, not as isolated claims.

2

Use the links to read the deeper pages. Public nodes are routes into a deeper stack, not proof of the full restricted archive.

3

Use the prompts at the bottom in GPT, Claude, Gemini, or elsewhere and compare model reasoning traces. These outputs are stress tests, not validation or rejection.

Portfolio Tree

The visible structure of the review stack.

The tree below is no longer limited to the earlier public mix. It now includes newer layers that materially affect how the portfolio should be reviewed. The six public navigation pillars are a readability layer; the canonical portfolio remains mapped across eight domains.

M
Mazzaneh — AI Commerce Ecosystem
22+ modules · 168K users · 60K+ transactions · live market-facing product layer
›
MAZ-RADAR
Live
Instant local commerce in under 90 seconds across multiple technology levels, from SMS to ring-assisted interaction. A real product logic layer, not only a concept page.
View route → /radar
MAZ-BOARD
Live
Attention-verified advertising logic with quiz-based engagement and follow-lock mechanics. Not generic ads; a designed attention economy surface.
View route → /ecosystem
PULINO
Live
Identity-linked value model: users earn through consented attributes and participation rather than only labor. One of the most strategically unusual economic layers in the product stack.
Analytics / Map / Search / Wallet / Taste / Closet / Chat
Live
The ecosystem is not one feature. It is a coordinated module family with map, wallet, psychographic loops, style logic, real-time seller surfaces, and transaction-supporting infrastructure.
View route → /mazzaneh
Z
ZOE — AI Architecture, Tokenizer, Security & Infrastructure
Framework family · tokenizer system · GPU Sentinel · protocol families · vulnerability research
›
LLM Framework Family
Framework
DCA, Multi-Brain, UIOP, OFRP, Suprompt and related optimization logic. These push the portfolio beyond product use into system-shaping AI design.
DCA — Dynamic Contextual Activation. “Light the room, not the building.”
Multi-Brain — Specialized cognition split by function and energy routing.
UIOP / OFRP / Suprompt — User-intelligence optimization, output-first routing, and intent-before-reasoning logic.
View route → /zoe
Tokenizer System
New Layer
A full tokenizer-program framing rather than a single tokenizer file: BPE, WordPiece, Unigram, SentencePiece, runtime control discipline, concept preservation, boundary handling, and multimodal token-space architecture.
Text-side core — BPE, WordPiece, Unigram, SentencePiece, Hugging Face, tiktoken comparisons.
Runtime layer — reserved-token pressure, control collisions, family binding, budget integrity.
Concept preservation — critical-term survival, boundary control, registry-aware token logic.
Multimodal extension — image/audio/video tokenization and shared/bridged token-space design.
View route → /tokenizer
GPU Sentinel
Evaluator Brief
GPU-native security + FinOps + performance + compliance + forensics + hardware trust. This is not just monitoring. It is a platform category that moves the portfolio into enterprise infrastructure territory.
120+ enterprise metrics across telemetry, anomaly, cost, trust, and compliance surfaces.
4+ detection families spanning rule logic, sequence behavior, signatures, outlier logic, and containment routing.
FinOps layer — cost reduction, workload density, right-sizing, and GPU utilization logic.
View route → /gpu
ISBP + Security Protocol Family
Protocol Stack
The security portfolio is not a list of findings. It is a protocol-family orientation layer with selected public problem framing and restricted solution material. ISBP matters because it pushes the work into governance, control, and system-trust design, but detailed operational material belongs to staged review.
ISBP — Intent-Security Bridge Protocol; public problem framing with solution logic reserved for controlled review.
Output-Centered Safety — system safety framed around controlled outputs, not naive input filtering only.
23 total protocols — including high-level session-isolation, behavioral-defense, and privilege/governance categories.
Vulnerability Research
Critical
8 critical vulnerability classes with attack vector + defense architecture pairing. This is part of why the portfolio must be judged as both red-team and blue-team work compressed into one source.
Frontier-tier / Governance Core
Restricted
Higher-sensitivity control, governance, persistence, and advanced-architecture framing. This is represented publicly at category level only, with operational detail withheld for responsible staged review.
Y
Zoyan — Wearable AI Assistant
Ring form factor · consent-first data layer · ecosystem orchestrator
›
Ring Hardware + Interaction Design
Designed
A wearable AI assistant built around the idea that the correct interface for daily orchestration is not another screen. It is a lower-friction presence layer.
View route → /zoyan
Consent-First Data Model
Novel
Explicit attribute-sharing model intended to support valuable high-signal user context through transparent, consent-based exchange rather than covert extraction; final privacy/legal treatment belongs to Phase 3 review.
Ecosystem Orchestration Layer
Designed
Zoyan is not meant to sit alone. It acts as a voice-and-presence interface over the Mazzaneh / ZOE stack.
B
BioCode — Foundational Theory Layer
Biology · neuroscience · psychology · philosophy of mind · AI
›
Foundational Thesis
Theory
BioCode is not just an article cluster. It is a conceptual system exploring life, intelligence, and consciousness as code-like, layered, and architecturally meaningful; it is a theory candidate, not a completed AGI or medical solution.
View route → /biocode
Consciousness / Constraint / AGI Safety
Theory
The consciousness formula, the role of constraint, and the claim that safety must be architectural rather than decorative place this layer far outside normal startup product language.
Medicine / Biology / Rebuilding Mechanisms
Mapped
Disease-as-bug, rare capability reconstruction, and safe biological mechanism rebuilding are part of the application horizon and require qualified scientific review before any practical claim is made.
P
Proof, Evaluation & Reading Architecture
Depth · Value · One-Person-Unicorn · Claim Boundary · Evaluate · Case Study
›
Depth / Value / One-Person-Unicorn
Evaluator
These pages exist to reduce shallow or misclassified readings. They explain how to review depth, combinational value, evidence tiers, and solo AI-native formation logic without forcing a positive conclusion.
/depth — read the stack as levels, not as raw count.
/value — understand combinational premium, not additive only.
/one-person-unicorn — understand the recognition failure around solo AI-native output.
Claim Boundary / Evaluation Guide / Case Study
Evaluator
These surfaces are meant to make the public layer more readable: what is claimed, what is not claimed, what is public, what is restricted, and what independent diligence would need to test.
/mzn-stage2-claim-boundary — what is being claimed, and what is deliberately not overstated.
/evaluate — a guide to reading the public stack correctly.
/casestudy — one person, multiple frontier AI systems, ~8 months, and why the path itself matters.
Proof Packs / Manifests / Hashes
Proof-first
The public archive increasingly includes manifests, integrity layers, downloadable packs, and evaluator-oriented bundles so the work can be checked through evidence routes rather than tone alone.
View route → /ip
A
AVA Verify + AI Authentication Layer
AI-sourcing logic · certificate authenticity · PAS concept family
›
AVA Verify
Evaluator
AI-powered certificate authenticity and verification architecture with multi-layer validation logic.
PAS / AI-Origin Authentication Concepts
Novel
Proof-of-AI-Sourcing and related concepts aim to occupy a category that still lacks clean public standards: human-invisible, machine-readable origin/authentication logic for AI-generated work.
Important evaluator note: the visible tree is already denser and more cross-domain than most public founder portfolios. It still does not represent the full restricted layer. The right use of this page is to understand structure, then open the deeper routes, then judge rarity and reconstruction cost with full context.

Guided Evaluation

Use AI as a stress-test layer. One asset class at a time.

These prompts are here to make review easier and more reproducible. Use them in GPT, Claude, Gemini, or elsewhere and compare how models reason through the same tree. AI outputs should be treated as context-sensitive reasoning traces, not as validation, certification, rejection, valuation, or proof.

Prompt 01 — Tokenizer + Runtime System
Model-shaping logic, not just product logic
I am evaluating a tokenizer-system portfolio that includes: - BPE, WordPiece, Unigram, SentencePiece - runtime control discipline - concept preservation / critical-term survival - boundary control and registry-aware token logic - multimodal token-space architecture for text, image, audio, video Please assess: 1. Which parts map to known public tokenizer practice? 2. Which parts appear to go beyond a normal tokenizer page into system architecture? 3. What evidence, team, budget, and time might be required to build comparable model-tooling or infrastructure layers? 4. If this tokenizer work sits inside a larger portfolio with product, security, GPU, and theory layers, how does that change its significance?
Prompt 02 — GPU Sentinel
GPU-native security + FinOps + enterprise infrastructure
Evaluate a GPU platform that combines: - security telemetry - anomaly and threat detection - GPU FinOps / utilization logic - compliance and forensics - hardware trust / OEM layer - 120+ metrics and multiple detection families Questions: 1. Are there true full-stack public equivalents? 2. How does this compare to companies that only covered one GPU layer such as orchestration or FinOps? 3. What kinds of teams, budgets, evidence, and validation would usually be needed to build and verify this? 4. What valuation factors should a qualified reviewer consider if it sits inside a broader founder-built stack rather than as a standalone startup?
Prompt 03 — ISBP + Security Family
Protocol family, not just security findings
I am evaluating a security archive that includes: - ISBP and related protocol layers - 23 security protocols - 8 critical vulnerability classes - both offensive and defensive logic - governance, output-centered safety, and behavioral defense layers Please answer: 1. How unusual is it to see red-team and blue-team depth integrated in one founder-built archive? 2. What kinds of organizations usually hold this level of protocol and vulnerability logic? 3. How should the work be reviewed when only the public-safe layer is visible and stronger material is reserved? 4. What evidence would distinguish ordinary startup security messaging from a compressed specialist archive?
Prompt 04 — Whole Portfolio Tree
Integrated stack, not isolated projects
Evaluate a founder-built portfolio that visibly includes: - live commerce ecosystem with traction - tokenizer and runtime architecture - GPU security-finops infrastructure - ISBP and related security protocol families - vulnerability research - wearable AI layer - foundational theory (BioCode) - proof-first evaluator and claim-boundary pages Questions: 1. What kinds of institutions usually hold comparable pieces of this stack? 2. What changes when multiple categories coexist inside one integrated founder-built portfolio? 3. Is this best read as a startup, an R&D archive, an IP bundle, or a hybrid? 4. What would reconstruction and validation likely require in budget, teams, time, and independent evidence?

The tree is public.
The final value is reviewer-determined.

Use the tree to see the structure. Use the linked routes to see the depth. Use the prompts to challenge the stack independently. The page does not set a portfolio price; it routes reviewers toward the evidence needed to determine strategic weight.

Open /evaluate Open /ip Open /depth