Software ecosystem

Governed operations, interpretable intelligence, and accountable coordination.

The Hidden Canopy LLC portfolio is not a single dashboard. Each layer has a distinct role, a distinct authority boundary, and a reason to remain separate.

Core boundary

RegOS owns authority. IDA owns interpretation. AI may analyze, challenge, explain, escalate, and recommend. Human or governed review remains the attributable action boundary.

Operational body

Hidden Canopy

Hidden Canopy is the applied operational surface. It brings governance into real workflows instead of leaving compliance as a report added after the fact.

Community and operator surfaces Discord-native workflows, moderator-first operations, trust and reputation pathways, and public-facing community experiences.
Regulated operational workflows Events, evidence, cultivation, vendors, identity, review, and accountability paths.
Physical grounding Device identity, camera and network context, observed state, verified state, and authorized state.
Constitutional substrate

RegOS

RegOS is the constitutional substrate and governed operational runtime. Its job is to make lawful purpose, authority, evidence, trust, attribution, safety safeguards, and post-event reconstruction structural properties of computation.

Lawful purpose and authority Actions remain attributable to actors, jurisdictions, declared purposes, applicable rules, and review paths.
Evidence and memory Immutable operational records, evidence provenance, verifiable decision chains, and resistance to quiet erasure.
Governed visibility Live event legibility, regulatory topology, device continuity, tenant isolation, and independent review.
Visit RegOS →
Plural interpretive intelligence

IDA Family

The IDA family is an internal separation-of-powers experiment: distinct student bodies carry legitimate pressures such as coherence, evidence sufficiency, safety, diagnostic separation, memory, trajectory, movement, repair, exposure control, urgency, and equilibrium.

IDA Coherence without flattening.
JUDGE, SENTINEL, PRISM, ECHO Legitimacy, protection, diagnostic clarity, and memory.
ATLAS, VECTOR, FORGE, SHADE, PULSE, ORBIT Trajectory, action, repair, exposure control, live signal, and equilibrium.
Supporting layers

The complete portfolio map.

The public website should give visitors an understandable map while keeping private runtime details and protected workflows behind their proper boundaries.

Deliberation

Convergence

The family-state process that preserves tensions and produces a coherent downstream packet.

Public voice

GH

The spokesperson for converged family state: many minds deliberate, one voice speaks.

Native training

IDA-TRAIN-V2

The governed training, evaluation, and promotion workspace for the IDA family. Its native C++/CUDA trainer turns curated operational history into auditable model bodies while keeping family-specific runtime recipes, evidence, and promotion decisions distinct — raw logs are never treated as truth. Low-precision and selective-compute research informs its efficiency path across hardware generations.

Open Hugging Face research profile →
Execution integrity

BraidSeal

Continuity, integrity, and signed execution lineage for governed systems — so what ran, in what state, under whose authority, can be verified after the fact.

Device identity

Device DNA

Persistent physical and device identity that keeps hardware grounded across time, movement, and reconfiguration — a device is recognized, not merely observed.

Evaluation

Open World Harness

Controlled, long-horizon evaluation under partial information, with ground truth held by the evaluator — evidence for how systems behave as conditions change between decision and consequence.

Developer cockpit

Ask_IDA

A local collaboration surface for reviewing IDA's reasoning, requesting explicit-consent learning, and applying reviewed code changes with full traceability.

Explore Ask_IDA →
Community surface

Greg Community Assistant

Community governance, cultivation, vendor, reputation, and economy workflows across Discord and other operator and community surfaces — a surface, not a shadow authority.

See how Greg operates →
Physical discovery

Camera-Location

Discovery and location evidence for cameras, network gear, and edge devices — visibility on a network is never treated as authorization.

View GitHub repository →
Physical context

Device and network grounding

Infrastructure context that distinguishes declared, observed, verified, and authorized state.

Explore the architecture

Start with the public overviews.

These pages give each documented system a stable public address without collapsing the authority boundaries between them.