Hub → public surfaces
The Hub provides API and control-plane context for approved work, public projections, and source receipts. It is not the local execution engine.
Read the company boundary →Technology · ecosystem map
The full map for technical readers.
The Hidden Canopy portfolio is a set of related systems with different owners, evidence tiers, and release boundaries. This map explains the relationships without turning a public diagram into an undocumented runtime dependency graph.
Relationship map
A governed spine with independent surfaces.
Each relationship below names the semantic connection: coordinates, interprets, executes, authors, evaluates, observes, or publishes evidence. It does not imply shared binaries, shared data, or shared authority.
RegOS → governed state
RegOS supplies the authority substrate: purpose, permissions, evidence, transitions, attribution, and safeguards.
Explore RegOS →IDA → questions and claims
The IDA family supports interpretation, challenge, memory, query, review, and recommendations without silently becoming permission.
Explore IDA →Neural Foundry → local compute
Neural Foundry owns standalone native planning, model execution, memory, checkpoint, recovery, and bounded receipts.
Read the execution boundary →Cartographer → VANTA
Cartographer can author and validate spatial content. VANTA can run worlds and simulations. The handoff is optional and typed.
Read the authoring boundary →Harnesses → runtime behavior
Open World Model Harness, OMNI-Q, Ghost Teacher, and TraceGlass investigate behavior, routes, failure, and evidence while keeping host truth distinct.
Browse research software →HAVEN · BUNDLE · Camera-Location
Local-first tools keep household, financial, and discovery context close to the person using them. Optional Hub paths do not erase local custody.
Browse local products →Library → evidence
Research, source receipts, author pages, release records, and Showcase entries make claims inspectable without presenting every artifact as the same kind of proof.
Open the library →Open Canopy → portability
Open Canopy records which software carries an explicit public commitment and which boundaries remain under review or held out.
Read the program →Boundary ledger
What the map refuses to imply.
01
Not every arrow is an API. Some are product relationships, documentation links, or evidence associations.
02
Not every product is a Hub feature. Local-first paths must remain useful without login, network, or hosted authority.
03
Not every source is Open Canopy. Release status, licensing, and portability are reviewed dimensions.
04
Not every experiment is a result. Simulation, source, unit, hardware, benchmark, and promotion evidence remain separate.
05
Not every adjacent system is public. Protected work stays generic or absent from this map.
How to use this map
Start with the role, then check the evidence.
Use Products for what people can use, Research software for what is being investigated, Showcase for observable work, Results for retained measurements, and the Open Canopy program for portability and release commitments.