CONCEPTS

Understand the Foundations

HexaKernel is built around a set of ideas that change where software development begins.

Instead of starting with frameworks, databases, APIs or code, the process starts with the domain.

The concepts in this section explain the foundations of that approach and how they connect.

The Domain as the Starting Point

Every software system exists to represent or operate within a domain.

That domain contains its own entities, relationships, rules, decisions, processes and behavior.

HexaKernel treats those concepts as primary.

Technology becomes the means through which the domain is implemented and executed.

This builds on a broader software principle in which domain logic is treated as central rather than being made dependent on infrastructure.

Specification as a First-Class Artifact

A domain can be understood informally through conversations, documents and existing processes.

HexaKernel takes the next step by making that knowledge explicit in a formal specification.

The specification describes what the domain means.

It can therefore become a source from which software, documentation, tests, knowledge and other artifacts are derived.

AI as a Builder

AI changes what can be generated.

But generation is not the same as understanding.

HexaKernel separates the two.

The domain remains the source of truth.

AI becomes a transformation layer that can reason over the formal specification and generate software and other artifacts from it.

This distinction is fundamental to the HexaKernel approach.

Agents Under the Kernel

AI agents can become powerful components of software systems.

But agents do not need to become the foundation of those systems.

HexaKernel places agents above a stable execution layer responsible for the domain, identity, permissions, execution context, events, observability and governance.

Agents can therefore evolve without requiring the foundation to evolve with them.

Agents change. The Kernel remains.

Domain-Driven Architecture

Complex systems benefit from organizing software around business domains rather than purely technical boundaries. Domain-driven design similarly places the domain model at the center and uses explicit boundaries to manage complexity.

HexaKernel extends this idea by making the formal domain specification a central artifact and connecting it directly to AI-driven software generation and execution.

Evolution as a First-Class Concern

Business domains change.

Rules change.

Processes change.

Relationships change.

New capabilities appear.

A system designed around a fixed implementation can make these changes expensive.

A system designed around a formal specification can treat change as domain evolution.

The specification changes first.

The software can then evolve from it.

Understand the principles before building on them.