Research portfolio
A typed, evidence-scoped map of the research behind NiGeNje: published records, specifications, working papers, mathematical models and open research directions. Every entry states what exists, what does not, and which links resolve publicly.
Central research question
How can computational systems evolve, act, adapt and recover while preserving the essential properties, authority and continuity that make their behaviour trustworthy?
Every entry in this portfolio is positioned against that question, and every maturity label says how far a given answer has actually progressed. The portfolio is deliberately uneven: some work is a published record, some is a specification, most is a research direction. The registry does not smooth that unevenness into a single narrative.
Published records and working papers
This list contains the published records, formal specifications, working papers and public software implementations in the registry. Research directions, models and proposals are deliberately excluded, because none of them is a public record.
The published λ-safe paper: a type-theoretic framework in which degradation is an explicit, checked transition that must preserve stated invariants rather than an unconstrained fallback.
A published beta operating-system implementation from the NiZiNG research line, recorded with a Zenodo DOI. It is a beta research artefact, not a production operating system.
A specification written for implementation: the contract surfaces and obligations a Chinje-conformant system is expected to satisfy.
A concept paper recording the motivation and framing of the Chinje research direction. It is not a peer-reviewed publication.
A formal specification of the Chinje software design: the structures, contracts and conformance conditions that implementation is stated against.
The open-core λ-safe compiler implementation: a bounded class of hard invariants is checked, with unsupported mandatory obligations refused rather than approximated.
Record discipline. The λ-Safe paper is a Zenodo record and the NiZiNG Beta OS is a Zenodo record with a verified DOI. The Chinje documents are specifications and a concept paper, not peer-reviewed publications, and no DOI is claimed for them. The λ-Safe Compiler is a public Apache-2.0 repository. Nothing on this page invents a publication record, a DOI or a date.
Disclosure boundary
This portfolio is a public research presentation, not a technical disclosure repository. It states the problem, the research direction, the capability and the evidence. It does not publish the proprietary mechanisms that constitute the intellectual property.
Withheld material is not omitted because the work is absent; it is omitted because publication requires explicit approval. Where the status of a detail is uncertain, the detail is not published. Research collaboration and technical evaluation can be discussed directly through the contact routes.
XERJ Corpus Hub
Recognition is recorded as a selection event, not as certification, partnership or validation. It concerns one engineering contribution, not the whole λ-Safe project or the wider NiGeNje platform.
A contribution from the NiGeNje λ-Safe compiler project was identified by XERJ for inclusion in its public Corpus Hub.
The selected engineering work, titled “Harden compiler assurance and solver boundaries”, covers compiler and solver assurance, production-safety improvements and associated end-to-end testing.
The contribution spans approximately 680 lines across 11 files, including the λ-Safe compiler, solver and fuzz-testing components.
This provides an external point of reference for the development of inspectable compiler and solver engineering artifacts within the NiGeNje research programme.
Why the contribution matters
Record and limits
Selection for potential corpus inclusion is not indexing, certification, approval, partnership, adoption or production validation by XERJ. It does not establish the formal correctness of λ-Safe, nor does it validate the wider NiGeNje architecture. Listing a specific contribution under Apache-2.0 does not grant permission to reproduce unrelated NiGeNje intellectual property.
Research families
Families group the work by question rather than by product. Five research-area pages render the full entries; some pages cover more than one family because the questions are read together.
Governance of distributed systems: architecture conformance, authority and obligation tracking, and the Chinje research project.
4 entries · Chinje research
Type-theoretic and contract-based methods for keeping stated invariants true while a system degrades and recovers.
4 entries · Foundational research
State models explored under the NiZiNG line of research, including the Ξ-Machine, infinite-state transitions and the k=9 representation.
4 entries · NiZiNG research
Rhythm, recurrence, phase, cadence and state-dependent pacing treated as a research framework for temporal computation.
1 entry · NiZiNG research
Decision, stability, containment, authorization and evidence research for autonomous infrastructure. Research and engineering foundations, not validated results.
12 entries · Autonomous infrastructure
The λ-Safe compiler and the wider language research stack: ChaosLang, Felt Lang, Morio, Nguna, CIR and Chaos Chain.
7 entries · Languages and compilers
Operating-system and network architecture research directions. None is presented as a production system.
2 entries · Autonomous infrastructure
Speculative hardware research into alternative computing substrates. No physical silicon exists.
1 entry · Autonomous infrastructure
Conceptual generative and creative-computation directions recorded under the NiZiNG research line. No implementation, equation or evaluation is claimed.
18 entries · NiZiNG research
The Chinje architecture-conformance project has a dedicated focus page:Chinje research
Search the portfolio
The filter runs over the complete registry. The result count is announced when it changes, every filter button is a native control, and an explicit empty state appears when nothing matches.
Showing 53 of 53 research entries.
A formal specification of the Chinje software design: the structures, contracts and conformance conditions that implementation is stated against.
A specification written for implementation: the contract surfaces and obligations a Chinje-conformant system is expected to satisfy.
A documented reference flow from specification to implementation and review, describing intended sequence rather than a shipped reference implementation.
A concept paper recording the motivation and framing of the Chinje research direction. It is not a peer-reviewed publication.
The published λ-safe paper: a type-theoretic framework in which degradation is an explicit, checked transition that must preserve stated invariants rather than an unconstrained fallback.
The compiler direction derived from λ-safe: turn supported, decidable contract obligations into checked artefacts with an explicit checked/not-checked boundary.
Research into expressing mandatory invariants and contracts so that a system's promised properties are checked rather than assumed.
Degradation framed as an explicit, reasoned transition with obligations that must remain true, and recovery as a further governed transition requiring fresh verification.
A published beta operating-system implementation from the NiZiNG research line, recorded with a Zenodo DOI. It is a beta research artefact, not a production operating system.
A mathematical model of deterministic transitions over an unbounded or continuous state space. The model is distinct from any claim of infinite physical execution.
Research into alternative computational representations, state evolution, temporal coordination and models of computational continuity. The internal formulation is not published.
Research into structured state representation and coordinated containment and recovery processes. The internal transition logic is not published.
Research into temporal coordination, recurrence, synchronization and state-dependent computational progression. The detailed temporal model is not published.
Research into adaptive decision systems that coordinate changing operational conditions while respecting explicitly defined system constraints.
Research into coordinated allocation across multiple resources while respecting declared system constraints.
Research into whether a controlled system tends back toward a safe operating region after a disturbance.
Research into the conditions under which a system remains inside a safe operating region and when corrective action is required.
Research into stating decision confidence honestly, including its calibration limits, instead of presenting a score as a checked probability.
Containment and recovery modelled on immune-system metaphors: detect pressure, quarantine, then admit only after recovery is justified.
Safe degradation as a runtime control obligation: deciding reduced modes, applying them under authority, and recovering only after fresh verification.
Authority-scoped action research: what a system is permitted to do at runtime, independent of what it can technically execute.
Research into reconciling observed state with intended state after an action, so divergence is detected rather than assumed away.
Recording a decision with the evidence and constraints that justified it, so the decision can later be examined rather than merely trusted.
Research into keeping decision, execution and outcome evidence linked and inspectable across a system's lifecycle.
Coordinating action across time: cadence, ordering and deadlines as governed concerns rather than incidental scheduling.
The open-core λ-safe compiler implementation: a bounded class of hard invariants is checked, with unsupported mandatory obligations refused rather than approximated.
A proposed language direction exploring how chaotic or uncertain system behaviour might be described and constrained. No public release or specification is claimed.
A language concept recorded as part of the founder's language research portfolio. No implementation, specification or public release is claimed.
A language concept in the programming-languages research line. Listed as a research direction; no public compiler or specification is claimed.
A language concept in the programming-languages research line. No implementation or public availability is claimed.
A compiler intermediate-representation concept within the language research line. No public specification or implementation is claimed.
A research concept in the language and compiler line. No public implementation, protocol or specification is claimed.
Operating-system and node-architecture research directions recorded as specifications and proposals. Neither is a production operating system.
Network architecture research associated with the MZiNG change-assurance line. Described as research; the product page states the public scope.
Speculative hardware research into an alternative computing substrate. No physical silicon, prototype or performance result exists.
A generative-computation research concept within the NiZiNG line, recorded as a conceptual direction. No engine, evaluation or public implementation is claimed.
A conceptual framework for situating creative computation in context. Recorded as research only; no formal definition or implementation is published.
A research label within the generative and creative computation family. No public definition, implementation or evaluation is claimed.
A research label within the generative and creative computation family. No public definition, implementation or evaluation is claimed.
A research label within the generative and creative computation family. No public definition, implementation or evaluation is claimed.
A named conceptual direction within the generative and creative computation research family. No implementation or publication is claimed.
A conceptual research label in the generative and creative computation family, recorded at research maturity.
A conceptual research label in the generative and creative computation family, recorded at research maturity.
A field-related concept in the generative computation line. Listed as research; no model, equation or implementation is claimed.
A named conceptual direction in the generative and creative computation research family. No implementation or publication is claimed.
A conceptual direction in the generative and creative computation research family. No implementation, evaluation or availability is claimed.
A conceptual cycle in the creative-computation research line. No runtime or formal process is claimed.
A conceptual kernel paired with the Rieng Cycle in the creative-computation research line. No implementation is claimed.
A concept in the field-related creative-computation research line. No formal potential function, equation or implementation is published.
A conceptual research direction in the generative and creative computation family. No implementation, data or evaluation is claimed.
A conceptual research direction in the generative and creative computation family. No implementation or publication is claimed.
A conceptual research direction in the generative and creative computation family. No implementation, evidence or evaluation is claimed.
A conceptual feedback direction in the generative and creative computation family. No controller, equation or evaluation is claimed.
How to read the labels
Research collaboration
Research correspondence, evaluation and collaboration begin with the problem you need represented: an invariant, a conformance question, a degradation path or a control decision. The portfolio is published so that the boundary can be inspected before the conversation starts.
