Elora's current research is grouped into a small number of engineering programmes. Together they cover how runtime behaviour is observed, how AI behaviour is learned, how governed language capabilities are taught, how decisions are constrained, and how evidence is surfaced to operators and reviewers.
Runtime Intelligence and Systems Behaviour (ERIS)
ERIS studies Elora's runtime metabolism rather than model quality. It applies bounded non-neural and statistical methods to worker state, pressure signatures, continuity posture, and degradation patterns so runtime behaviour can be interpreted without granting execution authority to the learning layer.
- Runtime pressure and degradation classification.
- Continuity and worker-health interpretation.
- Read-only predictive signals for operator visibility.
AI Behaviour Learning and Evaluation (EBLS)
EBLS is the emerging behaviour-learning domain. It is concerned with how models behave under task, profile, and policy conditions, using governed observer and model-exam evidence to classify suitability, adherence, and behavioural patterns.
- Model and profile suitability by task family.
- Governance-adherence and failure-pattern scoring.
- Evidence-linked behaviour summaries rather than opaque rankings.
Governance and Commit-Boundary Control
This programme focuses on the boundary between inference and authority. Elora treats model output as proposal, then evaluates admissibility, policy, and actor context at commit before anything consequence-bearing is allowed to proceed.
- Proposal-to-commit admissibility.
- Authority re-evaluation at commit time.
- Replayable reasoning for allow, block, and clarify outcomes.
Research Reporting, Replay, and Public Evidence
Elora is designed to collect and present deep evidence rather than only top-line scores. In 0.2.6, Elora Decisions adds a bounded decision-history layer that groups related operational events into reviewer-readable records without replacing the underlying replay evidence.
- Research dashboards and run reports.
- Governance replay and decision reconstruction.
- Structured decision stories for interventions, outcomes, cancellations, and cleanup.
- Public-safe evidence translation for demos and documentation.
Constrained-Compute Runtime Research
A central engineering question in Elora is how behaviour changes under limited compute, queue pressure, resource contention, and runtime drift. This research looks at instability, recovery, token efficiency, intervention behaviour, and runtime-governance signals under realistic operational constraints.
- Constrained-compute observer cycles.
- Intervention, recovery, and efficiency evidence.
- Runtime Governance and Inference Governor visibility.
Governed Language Learning and Additional Skills
Elora's Non-Neural Language and Symbolic Learning (NNLSL) work studies how language capabilities can be taught from governed lexical and educational evidence without making a neural model the default source of meaning or authority. The same supervised approach can support bounded skills not normally associated with inference control planes.
- Atomic lexical, sense, relationship, and construction evidence.
- Bounded deterministic language assembly and explicit learning-gap fallback.
- Training and Education pathways under policy, resource, and replay controls.
Current Research Outputs
The public site does not expose the full internal research surface, but current outputs include guided governance replay, guided research reports, research dashboard evidence, public-safe runtime governance, structured Elora Decisions, governed NNLSL milestones, technical disclosure chronology, and the ERIS/EBLS learning split.
Research Structure
Elora's research is intentionally separated into distinct domains so learning does not become authority. Runtime self-intelligence, AI behaviour learning, governance evaluation, and public evidence translation are related, but they do not collapse into a single uncontrolled decision layer.
This separation is important both technically and governance-wise: it allows richer evidence capture and deeper analysis while preserving the rule that execution authority remains at the commit boundary.
