Skip to content
HLNA LABS

The intelligence layer

HLNA AI

Shared infrastructure for intelligence across HLNA Labs — not a chatbot.

What
Shared intelligence and orchestration layer.
For
HLNA Labs projects, where it is useful. Not a standalone product.
Status
Status: In development

01

Why a shared layer

HLNA AI is the shared intelligence and orchestration layer across the HLNA ecosystem.

Rather than embedding an isolated chatbot into every product, HLNA AI is intended to provide common capabilities for reasoning, retrieval, agents, persistent context and controlled tool use.

Each project still owns its data, its rules and its interface. What it does not have to do is build and maintain its own model integrations, agent framework, retrieval pipeline and safety controls. Those are solved once, carefully, and reused.

Other HLNA products can use the same layer where useful, without each project reinventing its own AI stack.

HLNA AI architecture

  1. ProjectsBrainbase · Pulse · Essio · Securii · …
  2. HLNA AIreasoning · retrieval · orchestration
    • Models
    • Agents
    • Tools
    • Brainbase
    • Project data
    • External systems
Projects call one shared layer instead of each building their own AI stack.

02

How the pieces fit

Four responsibilities, deliberately kept separate. Knowledge is not intelligence, intelligence is not permission to act, and acting is not the same as having done the job correctly.

  1. 01

    Knowledge

    Brainbase

    Structured, sourced knowledge and history — the context intelligence works with.

  2. 02

    Intelligence

    HLNA AI

    Reasoning, retrieval, agents and orchestration over that context.

  3. 03

    Controlled execution

    Relay

    Policy-bounded, audited actions when intelligence needs to do something.

  4. 04

    Verification

    Proof

    Evidence-based checks that the work was done correctly and within the rules.

Brainbase = knowledge · HLNA AI = intelligence · Relay = controlled execution · Proof = verification

03

Core capabilities

What the shared layer is being designed to provide.

  • Model abstraction

    Projects ask for a capability, not a specific vendor's model. Models can change without rewriting products.

  • Reasoning

    Multi-step problem solving over the information a project provides.

  • Agents

    Task-focused agents that can plan and carry out work within defined limits.

  • Tool calling

    Structured access to project functions and external systems.

  • Retrieval

    Finding the right knowledge — from Brainbase or project data — at the right moment.

  • Persistent context

    Context that survives beyond a single conversation or session.

  • Project-aware intelligence

    Each project brings its own data model and rules; the shared layer respects them.

  • Workflow orchestration

    Coordinating multi-step work across models, tools and agents.

  • Controlled execution

    Actions run through Relay-style controls: bounded, logged and verifiable.

  • Local and cloud models

    Designed so local models can sit alongside cloud models where that is practical.

04

Development status

HLNA AI is in development as internal infrastructure for HLNA Labs projects. It is not offered as a standalone product.

  1. 01Research
  2. 02Prototype
  3. 03In Development (current stage)
  4. 04Beta
  5. 05Live
Or, at any stage:PausedArchived

05

Personal Knowledge

Brainbase

Your personal knowledge and operating system.

Brainbase brings together information scattered across conversations, documents, projects, tasks and digital history, turning it into structured, searchable knowledge while retaining its original source and context.

Status: In development

AI Reliability

Proof / Relay

Know whether your AI actually followed the rules.

Proof evaluates AI behaviour against explicit requirements and evidence. Relay provides the controlled execution layer around AI actions, helping make autonomous work observable, constrained and verifiable.

Status: Active development