Rules & Policies

Define What Governs the Domain

A domain is not defined only by the things that exist.

It is also defined by what those things are allowed to do.

Rules and policies express the logic that governs behavior.

Make Business Logic Explicit

A rule may determine when an operation is permitted.

A policy may determine who can perform it.

A constraint may determine what conditions must be satisfied.

A calculation may determine an outcome.

An obligation may determine what must happen.

These concepts are often buried inside application code.

HexaKernel brings them into the formal domain specification.

Rules Become Part of the Domain

When rules are explicit, they can be:

Understood.

Reviewed.

Validated.

Tested.

Versioned.

Generated.

Executed.

This creates a direct connection between business intent and system behavior.

Governance Without Ambiguity

Policies can also describe how authority operates within the domain.

Roles, permissions, conditions and constraints can be expressed as part of the model rather than reconstructed independently by every application or agent.

This is particularly important in domains where correctness, compliance and traceability matter.

From Hidden Logic to Explicit Knowledge

The objective is not to add more rules.

It is to stop hiding the rules that already exist.

Make business logic explicit, and it becomes something humans and machines can understand, verify and execute.