The platform

Press create.
The solution is live on save.

In an enterprise governance platform, a new capability is a project: a specification, a developer, a release, a regression. In Amzaa it is a wizard. The person who owns the risk configures it, and it exists the moment they hit save.

See it on your own process

Zero code

A new solution is data, not a codebase.

Everywhere else, "configurable" means a developer writes less code than usual. Here it means no code at all. A new app is a set of rows on a shared engine. There is nothing to deploy, nothing to regression-test, and nothing for the platform team to maintain afterwards.

The engine does not change when you add a solution. Only the data does.

What a new solution is

Nota new module, a new service, a new schema

Nota release, a migration, a deploy window

Justrows: an app, its fields, its stages, its rules

Resultlive on save, for the tenant that made it

What you configure, not code

Six things a developer used to do. Now a dropdown does them.

Create

The create button

A new app, from a wizard. Name it, add fields, choose types, done. No schema migration, because the schema is the graph and the graph already holds anything.

Wizards

Wizards to define governance

A workflow is stages you name and order. An approval is a gate you place. Governance is defined by the person who understands it, not translated by someone who does not.

Agents

Governed agents

An agent reads, drafts and proposes. It never writes. A human approves, the engine writes, and one switch stops every agent at once. Configured on, configured off.

Cross-app

Cross-app rules

When an issue closes, open a review in another app. When a risk crosses a threshold, create a task. One app acts on another, defined in a dropdown, with no glue code.

Calculations

Simple calculations

A field derived from other fields. An exception rate from a sample size. A residual from an inherent score and a control strength. Formulas, chosen, not written.

Risk

Risk on every record

Not a separate risk module bolted on. Every record can carry its own risk, scored from its own fields and its place in the graph. Risk is an attribute, not an afterthought.

Why it holds together

One graph underneath all of it.

The reason nine solutions behave like one is that they are not nine databases. Everything is a node or an edge. A control, a citation, a vendor, an entity, an issue: all the same shape. A relationship between them is a first-class thing, not a foreign key nobody can see.

That is why a risk knows its controls, a policy knows its regulation, and an obligation knows the evidence that discharges it. The links are the product.

Add a solution and it joins the same graph. It is related to everything already there, for free.

Nodea control, a risk, a vendor, an entity

Edgeassessed_by, breaches, rolls_up_to, discharges

Querytraverse it, do not join it

Adda new noun joins the same fabric

Forensic by construction

Every write records who, when, what, why, and whether a machine was involved.

Whoa person, resolved to a name on read, not a raw identifier

Whenstamped by the engine, so the caller cannot forge the clock

Whatthe field, the value before, the value after

Whythe workflow stage, the rule, or the approval that caused it

Machineif an agent proposed it, that is recorded, with the human who approved

Sealedan immutable chain; break a link and the platform detects it

This is not a log you enable in settings. It is how a write happens. There is no path to change a record that skips it.