Asset inventory
330+
Mapped assets and sub-assets formed or organized inside the Phase 2 record. The inventory can include systems, architectures, frameworks, protocols, specifications, components, research assets and review infrastructure.
Canonical definitions
Three counts. Three different meanings.
Portfolio accounting
8 domains
The underlying Phase 2 asset ledger is organized across eight portfolio domains. Public navigation families are reader aids and should not be mistaken for a new accounting taxonomy.
IP candidate surface
22+
Patent-grade candidate claims / areas identified for professional IP review. This is not a count of granted patents, allowed applications, or independently validated inventions.
Normalization rule
Legacy patent-count variants and older review-category decompositions are not used as canonical portfolio metrics. The current public baseline is 330+ mapped assets & sub-assets · 8 portfolio domains · 22+ patent-grade candidates, with legal normalization still required in Phase 3.
What “patent-grade” means here
Prepared for IP scrutiny — not pre-judged by the website.
What the label can indicate
- A defined technical or system problem.
- A documented architecture, method, protocol or candidate novelty hypothesis.
- Source files, specifications, diagrams or implementation/research artifacts.
- A first-date / version / provenance trail where available.
- A disclosure status and candidate legal route for counsel to examine.
What it does not establish
- Granted or allowed patent rights.
- Novelty, inventive step, patent eligibility or freedom to operate.
- Final human inventorship analysis where AI tools were used.
- Commercial enforceability, licensing value or certified valuation.
- Independent technical validation of the underlying technology.
Selected IP-sensitive families
Review the strongest families at the level they actually exist.
This is not a claim that every item below should become a patent. Some may ultimately fit patent, trade-secret, publication, copyright/specification, contractual know-how, or no-protection routes after counsel review.
AI Infrastructure
Tokenizer
Implemented and internally tested tokenizer/runtime architecture with multilingual, concept-preservation and multimodal work. Candidate claim areas require prior-art and counsel review.
Review Tokenizer →LLM Architecture
Optimization Backbones
DCA, UIOP, Multi-Brain, Suprompt and OFRP form a documented architecture family. Performance claims and legal novelty remain separate questions.
Review backbones →GPU Infrastructure
GPU Sentinel
Implemented/internal-tested GPU observability and security work. Deeper detection, benchmark and implementation details belong to controlled review.
Review GPU →Security Architecture
ZOE
A multi-layer security/architecture umbrella with mixed-maturity subfamilies. Legacy component/protocol counts are not treated as a single maturity or patent count.
Review ZOE →Security Research
ISBP
Documented threat discovery with a confidential mitigation architecture. The mitigation exists but is not publicly disclosed; novelty and effectiveness remain review questions.
Review ISBP →Protocol Research
HDTP
Documented protocol architecture with a reserved technical core. Strong information-theory and reconstruction claims require controlled technical review before legal conclusions.
Review HDTP →Foundational Research
BioCode
A broad foundational research architecture. Only specific technical candidates, if any, should be routed into IP work after scientific and legal decomposition; the research program itself is not one monolithic patent claim.
Review BioCode →Capability Architecture
HUAI
Phase 2 architecture/mapping roots with potential Phase 3 service, software, methodology or integration forms. IP route depends on the final professionalized implementation.
HUAI later integration →Product / Convergence
Mazzaneh + Zoyan
Phase 1 product know-how and Phase 3 convergence are important strategic context, but they should not be folded into the Phase 2 solo-IP count without asset-level provenance and scope separation.
See portfolio context →Provenance chain
Integrity records support chronology. They do not replace legal analysis.
01 · SourceFiles, specifications, diagrams, code/research artifacts, version history.
→
02 · First-date trailTimestamps, metadata, public publication records and priority chronology where available.
→
03 · IntegrityHashes / manifests on priority artifacts can help show file integrity and continuity.
→
04 · Claim tableProblem, novelty hypothesis, asset mapping, disclosure state, prior-art status.
→
05 · CounselInventorship, patentability, FTO, filing/trade-secret/publication route.
Evidence boundary
A hash or timestamp can support the existence and integrity of a particular artifact at a particular point in time. It does not by itself prove ownership, novelty, inventorship, patentability, technical correctness, or commercial value.
Disclosure governance
Protection strategy and public transparency are not the same thing.
Public
Orientation
Problem, high-level architecture, maturity, public evidence route and review boundary.
Controlled
Technical substantiation
Selected specifications, benchmark material, provenance context and deeper architecture for qualified review.
Restricted / NDA
Sensitive core
Security-sensitive mechanics, confidential mitigation, reserved protocol logic, unpublished implementation or patent-sensitive detail.
Independent
Phase 3 conclusions
Prior art, patentability, inventorship, FTO, legal route, technical validation and commercial diligence by qualified external reviewers.
Phase discipline
IP review must preserve the provenance boundary.
Phase 1
Mazzaneh was team-executed. Product, operational and market evidence can support founder execution history and historical product/IP context, but it is not part of the Phase 2 solo-formation count unless a specific Phase 2 asset is independently mapped and eligible.
Phase 2
The 330+ mapped-asset record, eight-domain ledger and 22+ patent-grade candidate baseline belong to the bounded solo AI-native formation review, subject to asset-level provenance and professional IP normalization.
Phase 3
Qualified counsel and technical reviewers perform prior-art search, claim refinement, inventorship analysis, route selection, filing/trade-secret/publication decisions, compliance review and commercialization diligence.
Value boundary
No public aggregate IP valuation is required to show that the work deserves review.
The legacy site used analytical value bands to provoke diligence. The canonical IP layer does not convert those scenarios into a valuation claim. Strategic value, if any, depends on technical substance, legal defensibility, commercial relevance, replacement difficulty, integration optionality and the results of independent review.
Correct question
Not “What number does the website assign?” but “Which candidate families survive technical, legal/IP, provenance and commercial diligence — and what value do qualified reviewers assign after that process?”