The metadata core

The system that
describes your systems.

Everything on Emeron — every entity, service, workflow, rule, interface and report — exists first as versioned metadata. The running software is generated from it. That single decision is where speed, governance and ownership all come from.

What the core captures

Six kinds of definition.
One source of truth.

01

Entities & data

People, businesses, permits, assets — your domain modelled once, with field-level classification built into the definition.

02

Services

Forms, documents, fees and eligibility — the whole citizen- or customer-facing surface of a service, as data.

03

Workflow

Stages, roles, routing, SLAs and escalation — the back office, described rather than programmed.

04

Rules

Fee formulas, validations and policy logic in the governed expression language — testable, reviewable, versioned.

05

Interfaces

Screens, portals and APIs — generated consistently for web, mobile, kiosk and machine-to-machine.

06

Reports

Governed reporting definitions on the same core — a report can never show what a role cannot see.

Versioned like code

Reviewed. Diffed.
Rolled back. Owned.

Every change to a definition is a version — who changed it, what changed, why. Releases are promotions between environments, rollback is a revert, and an auditor can read the history of a rule the way a developer reads git.

  • AI drafts into the same versioned store — proposals, not production. See the AI engine.
  • Definitions are readable and exportable — the anti-lock-in property. What you can read, you can own.
  • Regeneration is the upgrade path — platform improves, your definitions recompile, nothing is rewritten.
The pipeline

Definition in.
Governed system out.

Define

Analysts — and AI drafts — describe the service in Admin Studio.

Validate

Definitions checked for completeness, conflicts and policy compliance.

Compile

The AST · QL · EL engine admits only governed queries and expressions.

Deploy

Promotion between environments — releases as governed events.

Run

The runtime kernel executes it — one write path, fail-closed.

The catalogue

Every definition,
one governed catalogue.

Touch the layers — everything an application is, captured as versioned, reviewable, regenerable metadata.

Read a real definition.

In a technical walkthrough we open the metadata of a real service — and your architects judge for themselves whether it’s something they could own.