Explicit authority
The component that executes an action should not decide whether it is authorised. Authority is established independently, scoped to the action, and verified again at the boundary.
About NiGeNje
Systems that keep their promises when conditions change.
NiGeNje is an intent- and invariant-governed control platform for autonomous and distributed systems. It separates what a system intends to do, what it is authorised to do, what it actually executes and what can subsequently be verified.
Engineering direction
Capability is not authority.
Autonomous and distributed systems can now propose and take actions faster than the governance around them can keep up. Intent lives in prompts and tickets, authorisation lives in each service’s own logic, and the outcome is inferred from a successful response. When those boundaries are implicit, capability quietly becomes permission.
NiGeNje explores a different arrangement: make intent explicit and versioned, compile supported safety obligations into checkable artifacts, decide admission independently of the executor, mediate registered actions at runtime, observe what actually happened and keep the evidence linked and reviewable.
The platform is pre-product. Kernel capabilities are implemented and verified in a bounded local demonstration chain; end-to-end platform integration and qualification are progressing. Kernel capabilities implemented. End-to-end platform integration and qualification are progressing. The site labels each capability by its evidence rather than by its ambition.
Operating principles
Three rules that decide what appears on this site.
These principles are not slogans. They are the reason the platform documentation states limitations as prominently as capabilities.
Evidence over assertion
A successful response is a claim, not proof of outcome. Observation and reconciliation come before conformance, and a record that cannot be inspected is not accountability.
Honest boundaries
What is not enforced is documented as clearly as what is. Unknown outcomes stay unknown, partial capabilities are labelled partial, and unverified claims do not appear on this site.
Focus areas
Where the engineering effort goes.
Autonomous agent governance
Constrain what an agent may do, not only what it can do: declared intent, compiled invariants, independent admission and mediated tool actions.
Distributed system coordination
Coordinate action across services while representing partial failure, divergence and unknown outcomes explicitly rather than collapsing them into success.
Change assurance
Admit change only within declared invariants, refuse a candidate that breaks the commit invariant, and keep the change lifecycle reviewable.
Evidence and conformance
Observe what actually happened, reconcile it against the required postcondition, and evaluate conformance from records rather than from a status flag.
Verified links
Read the public record.
NiGeNje publishes limited, verified destinations: the public GitHub profile, the open-source λ-Safe Core repository, the published research record and the public LinkedIn profile. Platform repositories are private and are not linked.
What this page does not claim
This page does not publish team size, funding, customer names or a company history. Where those facts are not established, the site does not invent them. Commercial discussions are handled through the contact route, not through unverifiable claims here.
Work with NiGeNje
Start with the invariant that must not be broken.
The design-partner programme is the primary route for a technical evaluation. It is staged, non-production and explicit about what it does not promise.