Read the boundary first
Security and trust states what is enforced, what is partial and what is outside the mediation path. Architecture explains the control points and contracts behind it.
Technical resources
Verified material, indexed honestly.
Documentation, architecture, specifications, λ-Safe research, invariant preservation and safe-degradation material, security boundaries, integration scope, public repositories and engineering status. Every link is either an internal route or a destination verified as public and real.
Resource centre
Find the material that matches your question.
Filter by category or search by title, topic or format. The result count is announced when it changes, and an explicit empty state appears when nothing matches.
Showing 20 of 20 resources.
- DocumentationStart here
Documentation hub
The starting point for public platform concepts, architecture, security boundaries, integration scope and evaluation guidance.
- Documentation
Platform overview
What NiGeNje governs, the eight control capabilities and the ten-stage governance lifecycle, with maturity stated per capability.
- DocumentationScope
Technical specifications and public scope
Which specifications, contracts and schemas are published, which are provided under engagement and which do not exist publicly.
- DocumentationLimited
API and integration information
What is publicly documented about integration: registered mediation, permit verification and adapter boundaries. No public HTTP API contract is published.
- DocumentationInvariants
λ-Safe and invariant preservation
How λ-Safe formalizes supported contracts, compiles supported invariants, verifies admissible transitions, records the checked/not-checked boundary and refuses what it cannot decide.
- Documentation
λ-Safe product and stated limits
Product responsibilities, maturity, the supported numeric fragment, the checked/not-checked boundary and the explicit limit that λ-Safe verifies rather than enforces.
- Architecture
Architecture and lifecycle
Component responsibilities, dependency boundaries and the control points between declared intent and reviewable evidence.
- Architecture
Security boundary diagram
An original diagram of actor, intent, admission, permit, mediation, execution, observation and evidence, with λ-Safe invariant constraints, the degraded-mode research path and the enforced / not-yet-enforced boundary marked.
- Security
Security and trust
Ten security properties stated against the evidence, invariant preservation and degradation failure modes, the explicit NARG limitation, what is not claimed and a buyer evaluation checklist.
- Security
Security evaluation checklist
Direct questions to put to any vendor claiming a runtime control boundary, including invariant preservation and degradation recovery, with the evidence each answer should require.
- SecurityInvariants
Invariant preservation and safe degradation
Availability is not conformance: the conditions that must always hold, λ-Safe's verification role and the three degradation failure modes a healthy-looking system can hide.
- Research
λ-Safe research context
The research question behind λ-Safe, invariant-preserving degradation constructs, what the paper reports, how figures are attributed and how research maps to the product.
- ResearchPaper
λ-Safe research record
The published λ-safe research record on Zenodo: DOI 10.5281/zenodo.17067644, describing invariant-preserving degradation constructs at a conceptual level. The reported 3–5% overhead is attributed to the paper, not independently benchmarked here.
- ResearchSimulation
Safe-degradation simulation
A labelled, deterministic local simulation of the published degradation model: operating assumption violation, an admissible reduced mode, and recovery only after fresh verification. Not live telemetry or production enforcement.
- Code & repositories
λ-Safe Core source
The open-source compiler for a deliberately bounded class of hard invariants, with refusal of unsupported mandatory clauses (Apache-2.0). Internal mechanisms are not published.
- Code & repositories
Public engineering profile
Public GitHub profile for NiGeNje engineering work. Platform repositories are private and are deliberately not linked from this site.
- Status & releases
Status and readiness
Honest public integration state: what is configured, what is not, and why the page is not live control-plane telemetry.
- Status & releases
Registry maturity summary
Product and platform maturity read from the engineering registers: implemented, demonstrable, integrated, in progress. Integrated means verified in a bounded local chain, not production qualified.
- Status & releases
Product maturity register
The public product registry, including maturity labels, evidence notes and stated limitations for each product surface.
- Documentation
Design-partner evaluation path
The six-stage adoption narrative from discovery to deployment planning, with an explicit statement of what is not promised.
Verified destinations
Only public destinations are linked.
External links are limited to the public engineering profile, the open-source λ-Safe Core repository, the published Zenodo research record and the public LinkedIn profile. Platform repositories are private and are not linked, and no placeholder or guessed URL appears on this site.
Link policy
Internal links resolve to real routes on this site. External links open in a new tab and leave NiGeNje’s control; verify version, licence and currency at the destination. A link existing here is not an endorsement of any third-party claim.
How to use this material
Start with the boundary, not the brochure.
Check the maturity label
Every product surface carries a maturity label with an evidence note and a stated limitation. “Integrated” means verified in a bounded local chain, never production qualified.
Then ask for evidence
Use the evaluation checklist and the status page to separate a design target from a tested control. Where evidence does not exist, the site should say so.
Engagement
Need material that is not published?
Operator documentation, integration contracts and evaluation evidence are provided under engagement. No public API contract is invented to fill a gap on this site.