OPU · Asset Substance Test

Don’t count the assets.Measure the weight.

The 330+ mapped assets and sub-assets establish scope. They do not establish value. Weight comes from technical specificity, maturity, reconstruction burden, integration relevance, standalone usefulness, falsifiability and specialist review.

330+ = scopeDepth ≠ countMixed maturityStandalone + integrated value
Depth model

Seven lenses for testing whether the portfolio has substance.

01

Problem specificity

Is the asset tied to a real technical, product, security, research or operational problem rather than only a label?

02

Architecture depth

Does it contain mechanisms, interfaces, design choices and trade-offs that can be reviewed?

03

Maturity evidence

Research, architecture, implementation, internal testing and independent validation must remain distinct.

04

Reconstruction burden

What would a competent team need to understand, reproduce or extend the work? This is a diligence question—not a public monetary estimate.

05

Standalone value

Can the asset matter independently of the broader MZN architecture?

06

Integration optionality

Does the asset gain additional value when connected to other validated systems without requiring the whole portfolio to be bundled?

07

Falsifiability

Can technical, scientific, IP or commercial review return a negative result?

Representative validation

Portfolio breadth and deep proof solve different problems.

Breadth establishes scope

A broad mapped portfolio can show the range of formation and architecture. It does not mean every item is a finished product or equal in strategic importance.

Deep review establishes weight

Selected representative assets should undergo reproducible technical, IP, scientific or commercial diligence. Strong representative validation can materially change confidence in the wider formation record.

Review rule

Portfolio breadth establishes scope. Asset-level diligence establishes weight.

Current examples

Different asset classes require different kinds of depth review.

Tokenizer / GPU Sentinel

Implementation and internal-testing claims can be checked through code, reproducible environments, benchmark design and independent replication.

Tokenizer → · GPU →

LLM architecture / ZOE

Architecture depth is tested through technical coherence, mechanism specificity, security/evaluation logic and implementation mappings.

LLM Anatomy → · ZOE →

ISBP / HDTP / BioCode

Research assets require novelty, reproducibility, scientific/technical discipline and appropriately controlled disclosure—not product metrics alone.

Research →
What depth cannot prove

Substance does not prove solo provenance or final valuation.

A portfolio can be technically strong and still fail the one-person claim. A portfolio can also be genuinely solo and still fail the strategic-value thesis. Keep the two axes separate.