01 · Origin
Phase
Was the asset rooted in Phase 1 team execution, formed inside the Phase 2 solo boundary, or intended for Phase 3 validation and operationalization?
Reading model
Four axes prevent the portfolio from becoming an undifferentiated count.
Every asset should be read through the same four questions before anyone assigns technical, commercial, IP, or strategic weight.
02 · Nature
Asset Type
Product system, implementation, reference architecture, framework, protocol research, threat discovery, foundational research, or convergence layer?
03 · State
Maturity
Documented, implemented, internally tested, historically operated, independently validated, or still pending a specific review step?
04 · Access
Disclosure
Public orientation, controlled technical material, restricted/NDA internals, or independent review output?
Count boundary
330+ is the Phase 2 mapped-asset formation record. It is not 330 finished products, 330 patents, or 330 independently validated technologies. The count establishes breadth; asset-level review establishes weight.
Portfolio layers
The portfolio is broader than a single product stack.
Phase 1
Product & Market Roots
Mazzaneh: team-executed product, commerce mechanisms, seller/buyer operations, analytics, and market learning. It provides execution context, not Phase 2 solo provenance.
Open Phase 1 →Phase 2
AI-Native Formation
Tokenizer, GPU Sentinel, LLM Anatomy, LLM Framework, optimization backbones, ZOE, and the wider documented asset formation record.
Open Phase 2 →Research
Foundational / Frontier Work
BioCode, HDTP, and ISBP: different research classes with different maturity and disclosure boundaries, all traceable to Phase 2 origin.
Open Research →Phase 3
Validation & Convergence
Independent technical/legal/IP/commercial review, selective rebuilds, pilots, HUAI operationalization, Zoyan convergence, and qualified partnerships.
Open Phase 3 →Reviewer-facing families
Navigate by the question you are trying to answer.
These are navigation families, not a replacement for the underlying eight-domain asset ledger. They are designed to reduce cognitive load while keeping the full portfolio intact.
Product / Commerce
Mazzaneh Systems
Intent-first commerce, business participation, seller adoption, attention/reward mechanisms, and market analytics.
Review product roots →AI Infrastructure
Tokenizer + GPU
Implementation-level technical assets with internal testing records and deeper controlled-review material.
Open Tokenizer →LLM Architecture
Anatomy + Framework + Backbones
21-slot reference anatomy, complement framework, and optimization architectures that describe and shape LLM-company capability.
Open LLM Anatomy →Security / Trust
ZOE + ISBP
ZOE as a security/architecture umbrella, with ISBP separated as a documented threat discovery plus confidential mitigation architecture.
Open ZOE →Foundational Research
BioCode + HDTP
Human-grounded intelligence research and protocol research that can be reviewed independently of whether they later enter an integrated product.
Open Research →Human-AI Convergence
HUAI + Zoyan
HUAI has Phase 2 architectural roots; operationalization belongs to Phase 3. Zoyan is a Phase 3 human-facing convergence direction, not a retroactive Phase 1 product claim.
Open convergence route →Selected asset registry
Representative assets, each with its own review state.
Asset / System
Origin
Type
Maturity
Route
Mazzaneh
Product / market system
Phase 1
Commerce platform
Historically operated · evidence reconciliation ongoing
LLM Anatomy
Phase 2
Reference / evaluation atlas
21 slots · 529 mapped endpoints · documented reference system
LLM Complement Framework
Phase 2
Strategic architecture
Documented framework · independent use/validation separate
Optimization Backbones
Phase 2
Architecture family
DCA · UIOP · Multi-Brain · Suprompt · OFRP documented
ZOE
Phase 2
Security / architecture umbrella
Documented multi-domain architecture · mixed component maturity
ISBP
Phase 2 origin
Security threat discovery
Discovery documented · confidential mitigation exists · independent review pending
HDTP
Phase 2 origin
Protocol research
Documented protocol architecture · reserved core · validation separate
BioCode
Phase 2 origin
Foundational research
Documented research architecture · hypotheses / applications reviewed separately
HUAI
Phase 2 → 3
Capability / integration architecture
Architectural roots in Phase 2 · operationalization belongs to Phase 3
Zoyan
Phase 3
Human-facing convergence
Planned validation / integration path · not completed Phase 3 operation
Value logic
Standalone assets and integrated architecture can both matter.
Standalone review
Tokenizer, GPU Sentinel, ISBP, HDTP, BioCode, LLM architecture and other families can be tested, partnered, licensed, researched, rebuilt, or rejected on their own merits.
- Asset-specific maturity
- Asset-specific evidence
- Asset-specific IP route
- No requirement to accept the whole MZN thesis first
Integration optionality
Evidence Graph and future HUAI/Zoyan work examine whether selected validated assets become more useful when connected. Integration is a strategic option, not a condition for standalone value.
- Cross-portfolio interoperability
- Shared data / trust / intelligence layers
- Phase 3 selection and validation
- No forced all-or-nothing architecture
What to review next
Portfolio breadth is the map. Diligence decides the weight.
IP / Provenance
What may be protectable?
Review candidate claim areas, provenance, disclosure choices and the Phase 3 counsel workflow.
Open IP →One-Person Case
Who formed the eligible Phase 2 stack?
Test the bounded solo formation claim independently from technical merit or valuation.
Open OPU →Review
How should the case be challenged?
Use role-based routing, paradox-aware review, and claim → evidence → artifact → verification logic.
Open Review →