Convergence
The family-state process that preserves tensions and produces a coherent downstream packet.
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.
RegOS owns authority. IDA owns interpretation. AI may analyze, challenge, explain, escalate, and recommend. Human or governed review remains the attributable action boundary.
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.
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.
The public website should give visitors an understandable map while keeping private runtime details and protected workflows behind their proper boundaries.
The family-state process that preserves tensions and produces a coherent downstream packet.
The spokesperson for converged family state: many minds deliberate, one voice speaks.
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 →A public explanation and bounded Flight Deck surface for private, native training. The Hub coordinates approved metadata while data, models, checkpoints, detailed telemetry, and runtime execution remain in their proper local or private boundary.
Continuity, integrity, and signed execution lineage for governed systems — so what ran, in what state, under whose authority, can be verified after the fact.
Persistent physical and device identity that keeps hardware grounded across time, movement, and reconfiguration — a device is recognized, not merely observed.
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.
An evaluator and adaptive curriculum engine that probes a model endpoint, diagnoses failure modes, and searches the capability boundary — an evaluator, not a model trainer.
Reconstructs agent runs as decision chains — available information, inferred belief, candidate action, executed action, consequence — and identifies the earliest point where the chain broke.
A capability-aware runtime for continuous AI operation under compute, connectivity, and service degradation, designed to run without depending on any other Hidden Canopy service.
A native world, visual-simulation, and machine-learning engine built around one authoritative world state and a validated-transition execution loop.
A RegOS-derived governance runtime that evaluates identity, authority, jurisdiction, policy, and evidence before permitting consequential public-safety actions, while preserving provenance for after-the-fact reconstruction.
A local-first objective orchestration runtime that keeps personal preference models local while allowing a minimal, anonymized objective graph to travel across a bounded commerce flow.
A portable, evidence-backed trust and progress record for people moving from incarceration through a parole hearing, release, supervision, and independent life.
A local collaboration surface for reviewing IDA's reasoning, requesting explicit-consent learning, and applying reviewed code changes with full traceability.
Explore Ask_IDA →The regular user-facing, local-first command-line surface for status, public explanations, signed catalog discovery, public model downloads, and local inference.
Explore Ask IDA CLI →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 →Discovery and location evidence for cameras, network gear, and edge devices — visibility on a network is never treated as authorization.
Explore Camera-Location →A local-first, authority-gated household intelligence layer for computers, information, devices, speech, and local models. HAVEN keeps model interpretation separate from permission to act.
Explore HAVEN →Infrastructure context that distinguishes declared, observed, verified, and authorized state.
Broad, department-level research interest applying governed-evidence and authority-boundary discipline to mission-assurance and resilience domains — described at the capability level, not a claim of an award or contract.
Read the capability overview →Public GitHub repositories for local-use tools and research runtimes, kept separate from private authority and regulated workflows.
Browse the public repositories →These pages give each documented system a stable public address without collapsing the authority boundaries between them.
Separate shelves for consumer software, game-engine development, Cartographer, research, and public source receipts.
Open the public library →The plain-language contract for what a public repository or page means, and what it never silently authorizes.
Read the contract →