Commercial estate files
211
business portfolio source files across licensing, valuation, pitch, website, portfolio, and audit layers
Platform overview
BioAtlas is a platform overview: public proof, protected intelligence, and commercial engine families.
BioAtlas should be understood as a layered intelligence estate: a public-facing proof layer, a protected app and data-room layer, a commercial licensing layer, an investor-demo proof layer, and a family of engines spanning QTOS, Rubik, ECS, oncology, microbiome, cell-state intelligence, neuro systems, and API infrastructure.
Licensing suite files
74
asset-family images, category packaging, institutional licensing, API, SaaS, and dataset product surfaces
Platform package signals
1,123
module, package, bundle, dataset, engine, API, tier, plan, kit, and institutional access language
Buyer-market signals
702
clinic, oncology, research, biotech, pharma, institution, enterprise, investor, and acquirer context
BioAtlas public estate map
Open for exploration. Governed for responsible use.
BioAtlas is staged deliberately: public proof, research provenance, platform engines, commercial packaging, protected diligence, and reviewed access. Each layer shows enough for the right audience without exposing protected routes, data-room material, or internal app surfaces.
01Open
Public proof layer
Readable public pages, safe summaries, route maps, DOI links, and the high-level BioAtlas story.
public pagessafe summariesroute map
02Open
Research provenance
DOI-backed papers, preprints, Zenodo records, grouped research collections, and public provenance.
DOI indexpreprintsresearch collections
03Open
Platform engines
QTOS, Rubik, ECS, oncology, microbiome, cell atlas, systems biology, neuro, and infrastructure families.
engine familiesplatform overviewinvestor proof
04Open
Commercial packaging
Licensing families, dataset access, SaaS/API routes, white-label scope, and AI-rights boundaries.
asset familiesrights architecturebuyer routes
05Open
Protected diligence
Buyer review, data-room categories, staged release, provenance, IP boundaries, and technical diligence.
data-room mapbuyer reviewprotected boundaries
06Open
Reviewed access
Serious research, licensing, diligence, platform, API, and acquisition routes start with reviewed access.
access requestAdmin reviewcontrolled release
Estate layers
The public website is only one layer of the BioAtlas estate.
The platform page should show how the estate fits together before a buyer, investor, researcher, or partner asks for protected access.
Public proof layer
The public estate explains BioAtlas without exposing the protected app: platform pages, DOI records, research summaries, licensing overview, diligence pathway, safety boundary, and access request funnel.
public pagesDOI trailsafe summariesaccess funnel
Protected intelligence layer
The protected layer contains deeper app surfaces, datasets, internal maps, engines, notebooks, vault material, buyer packs, and data-room review material.
protected appdatasetsvaultdata room
Commercial packaging layer
The commercial layer translates the estate into asset families: QTOS, Rubik, oncology, ECS, microbiome, neuro, cell-state, API, SaaS, and institutional licences.
licensing suiteasset familiesbuyer routesrights
Investor-demo proof layer
The investor-demo layer should demonstrate that BioAtlas is not just content: it has structured knowledge checks, page families, evidence logic, route discipline, and reviewer-facing proof surfaces.
knowledge checkdemoreview proofinvestor logic
Engine families
BioAtlas is organised around reusable intelligence engines.
The commercial source layer shows BioAtlas as a catalogue of packages, modules, datasets, engines, APIs, product families, and institutional routes. Publicly, that becomes a map of engine families rather than a raw file dump.
QTOS / Physics-first engine family
The physics-first layer for collapse dynamics, coherence drift, multi-layer disease framing, vortex architecture, reachability windows, and constraint-aware interpretation.
Physics-firstResearchDiligence
Rubik constraint layer
The undercarriage beneath QTOS: a constraint-first layer for irreversible systems, reachable vs non-reachable transitions, failure visibility, and decision-boundary discipline.
Physics-firstSafetyDiligence
Oncology systems engine family
Oncology estate covering hallmarks, PCD logic, metabolic reprogramming, cell fate, tumour-state interpretation, subtype context, and pharma / biotech relevance.
OncologyCell AtlasDiligence
ECS systems engine family
Endocannabinoid-system intelligence across receptor maps, GPCR signalling and systems coordination, immunometabolism, ageing, hormone context, allostasis, and resilience boundaries.
Gut & MicrobiomeSystems BiologySafety
Gut–microbiome signalling axis
Gut, immune, microbiome, ECS, mitochondrial, signalling, and neuro-axis intelligence for systems-level biological interpretation.
Gut & MicrobiomeSystems BiologyResearch
Cell atlas and surface-state engine family
Cell-state, cell-fate, surfaceome, neuro-cell, miRNA, immune-cell, metabolic-state, and PCD-linked intelligence for identity and transition mapping.
Cell AtlasOncologySystems Biology
Neuroimmune and nervous-system estate
Neural regulation, neuroimmune pathways, neuroimmune systems stack, epilepsy systems framing, mood, memory, and nervous-system reprogramming research assets.
Systems BiologyCell AtlasResearch
SaaS, API, and output infrastructure
Commercial infrastructure for controlled platform access, dataset-driven review, API-style output surfaces, white-label discussion, and workflow integration.
LicensingDiligenceAccess
Enzyme Intelligence Engine
A mechanism layer beneath the BioAtlas estate
BioAtlas includes a public-safe enzyme intelligence layer covering 1,724 enzymes, 38 families, six-layer systems-state modelling, graph context, dataset architecture, and evidence provenance.
1,724 enzymes
Atlas
38 groups
Families
6 layers
Field model
Investor-demo proof layer
The investor demo should prove structure, not expose the vault.
A strong investor-demo layer shows that BioAtlas has organised knowledge, route discipline, buyer-review logic, evidence provenance, controlled access, and commercial packaging. It does not need to reveal protected datasets or private app internals to prove the estate.
Knowledge-check surfaces
Investor-demo knowledge checks can show that the platform has structured comprehension, reviewer readiness, gated education logic, and controlled buyer-facing proof.
Route discipline
Public pages explain the estate while protected routes remain separated. Serious calls to action route through reviewed access rather than internal app links.
Research provenance
The DOI and preprint trail supports public trust, external timestamping, and reviewer confidence without exposing the full data room.
Commercial audit trail
The business portfolio audit identifies package density, buyer markets, rights boundaries, valuation material, licensing suites, and commercial product families.
Safety and non-claims layer
The safety page and capability-envelope framing separate research, diligence, and publication context from diagnosis, treatment, prescribing, or autonomous intervention.
Access-request workflow
The public access funnel gives reviewers a formal path into controlled evaluation while keeping Admin Control and protected materials private.
Relevant public papers
Platform papers by engine family.
These records show BioAtlas as a platform overview rather than a single paper: QTOS, programmable operating-system logic, ECS systems, microbiome integration, cell-state intelligence, and protected investor-demo proof.
ReportQTOS / platform OS
QTOS Systems-State Framework
Early QTOS record describing the systems-state operating-model concept and platform-level architecture.
ResearchPlatformPhysics-firstDiligenceLicensing
Read DOI recordReportProgrammable OS / neuro / gut-brain-ECS
A Programmable Therapeutic Operating System for Neural, Cognitive, and Gut–Brain–ECS Reprogramming
Defines a programmable operating-system framing for neural, cognitive, gut-brain, and ECS reprogramming research.
ResearchPlatformGut & MicrobiomeSystems BiologyLicensing
Read DOI recordOpen preprintPhysics-first biology / QTOS
A Physics-First Framework for Multi-Layer Disease Dynamics
Introduces the physics-first disease-dynamics framework across layered collapse, coherence, constraints, and state transitions.
ResearchPhysics-firstPlatformDiligenceLicensing
Read DOI recordZenodo recordQTOS / safety guardrails
QTOS Capability Envelope & System Guardrails (v1.0): Formal Definition of Scope, Limits, and Non-Claims
Defines the QTOS capability envelope, limits, guardrails, non-claims, and infrastructure-grade scope.
ResearchPhysics-firstPlatformSafetyDiligenceLicensing
Read DOI recordZenodo recordRubik / constraint-first computation
Rubik vs Supercomputers: Constraint-First Computation and Governance Infrastructure
Defines Rubik as a constraint-first computation and governance layer below QTOS, focused on reachability, impossibility, and deterministic boundaries.
ResearchPhysics-firstPlatformSafetyDiligenceLicensing
Read DOI recordReportECS operating system
The Endocannabinoid System as a Systems-Regulated Operating Model: A Multidimensional Framework for Human Biology Reprogramming
Frames the ECS as a systems-regulated operating-model layer across biological coordination, state interpretation, and systems integration.
ResearchGut & MicrobiomeSystems BiologyPlatformLicensing
Read DOI recordReportECS / microbiome / systems biology
ECS–Microbiome Integration: A Multi-Domain Systems Biology Framework
Integrates ECS, microbiome, gut-immune-neuro signalling, systems biology, and systems-biology context.
ResearchGut & MicrobiomeSystems BiologyPlatformLicensing
Read DOI recordReportNeuro cells / systems integration
Neuro Cell Integration Dataset & Framework
A neuro-systems-state integration dataset and framework for neural cells, cell-state interpretation, and systems modelling.
ResearchCell AtlasSystems BiologyLicensing
Read DOI recordThese records are included for provenance, publication, and review context only. They do not create medical advice, treatment instruction, dosing guidance, autonomous decision-making, or clinical access.
Platform boundaries
Public proof is not the same as protected platform access.
The platform page should be strong enough for buyers and investors, but disciplined enough to keep internal systems, protected datasets, private vault assets, commercial terms, and administrative surfaces out of public view.
public pages are not the protected appDOI records are provenance, not clinical instructionlicensing pages are not data-room accessdiligence requests are staged and reviewedAI ingestion requires explicit rightsAPI and dataset access are separate commercial scopesinternal routes stay protectedadmin and security APIs are never public CTAs
Reviewed access
Platform review starts with the access request, not an internal route.
Reviewers can request platform evaluation, licensing review, technical diligence, investor-demo review, API discussion, SaaS discussion, or acquisition screening. The correct path is staged access through Admin Control, not public links into protected areas.
Request platform reviewPublic proof, protected platform
The platform can be evaluated publicly without exposing the protected estate.
The public platform page explains the estate, engine families, proof layer, and access pathway. Deeper technical assets, app surfaces, raw datasets, and controlled demos remain protected until review.
Public layer
What can be seen publicly
public page summaries
route map and estate map
DOI and preprint links
research collection names
safe paper summaries
licence family names
buyer lane overview
safety and non-claims boundary
access request funnel
Protected layer
What requires review
protected manuscripts
private vault assets
raw datasets and data-room extracts
buyer packs and valuation notes
pricing and commercial terms
technical architecture detail
internal app surfaces
controlled demos
AI-use or derivative-use rights
Public visibility is not a licence. Public pages do not grant access to protected material, commercial terms, AI ingestion, derivative databases, model training, redistribution, replication, or clinical use.