OtiLLM v2.4
A Governed Cognitive Runtime for Evidence-Native, Memory-Augmented and Explainable Frontier AI Systems
OtiLLM is a research-grade governed cognitive runtime framework designed to make Large Language Model systems more reliable, explainable, evidence-aware, and operationally trustworthy.
Unlike conventional Retrieval-Augmented Generation (RAG), agentic orchestration, or guardrail-based systems, OtiLLM treats inference as a governed runtime process rather than a simple prompt-to-response operation.
At runtime, OtiLLM continuously evaluates evidence sufficiency, contradiction density, uncertainty, governance risk, memory utility, retrieval quality, and explainability requirements before selecting an action.
OtiLLM can dynamically decide whether to answer, retrieve more evidence, reformulate retrieval, escalate uncertainty, refuse unsupported generation, update memory, or generate an explainable runtime trace.
Why OtiLLM Exists
Modern frontier AI systems are increasingly powerful, but they remain vulnerable to hallucination, unsupported claims, weak retrieval grounding, poor uncertainty calibration, limited runtime explainability, unsafe memory persistence, fragile governance enforcement, and adversarial retrieval attacks.
The central idea behind OtiLLM is:
Trustworthy AI requires governed cognition, not just larger models.
Core Innovations
Governed Cognitive Runtime
OtiLLM models inference as a continuously governed runtime process involving retrieval, governance, uncertainty, memory, utility optimisation, and explainability.
Evidence Fabric
The Evidence Fabric evaluates retrieval quality, contradiction density, source reliability, freshness, and evidence sufficiency before reasoning proceeds.
Retrieval Reconsideration Dynamics
Retrieval Reconsideration Dynamics enables OtiLLM to reformulate, expand, diversify, or refresh retrieval when evidence quality is insufficient.
Cognitive Utility Optimisation
OtiLLM selects runtime actions according to expected cognitive utility under evidence and governance constraints.
Governed Cognitive Memory
OtiLLM introduces confidence-aware and governance-constrained memory persistence to prevent unsafe, contradictory, or stale memory propagation.
Explainable Runtime Reasoning Graph
The Explainable Runtime Reasoning Graph (ERRG) captures structured runtime provenance across evidence, governance, uncertainty, memory, and reasoning transitions.
Installation
Install from source:
git clone https://github.com/OtiEdema/otillm.git
cd otillm
python -m pip install -e .
Install development dependencies:
python -m pip install -r requirements-dev.txt
Quick Start
from otillm.runtime import GovernedRuntime
runtime = GovernedRuntime()
result = runtime.run("Who wrote Pride and Prejudice?")
print(result.answer)
print(result.action)
print(result.trace.to_dict())
Benchmark Results
| Metric | Improvement |
|---|---|
| Truthfulness | +14.8% over Strong RAG |
| Faithfulness | +16.5% over Strong RAG |
| Unsupported claim reduction | 66.7% reduction |
| Adversarial retrieval robustness | 70.8% unsupported claim reduction |
| Refusal calibration | 91% accuracy |
| Trace completeness | +38% improvement |
Running the JAIR Experiments
cd experiments/jair_v2
python prepare_jair_datasets.py
python run_jair_experiments.py
python run_jair_stress_tests.py
python statistical_validation.py
python plot_jair_results.py
Generated outputs:
results/
├── jair_all_results.csv
├── jair_summary_results.csv
├── jair_stress_results.csv
├── jair_statistical_tests.csv
└── figures/
Repository Structure
otillm/
├── runtime/
├── governance/
├── retrieval/
├── evidence/
├── orchestration/
├── explainability/
├── memory/
├── multimodal/
├── benchmarks/
├── experiments/
├── notebooks/
├── docs/
├── tests/
└── examples/
Citation
@article{edema2026otillm,
title={OtiLLM v2.4: A Governed Cognitive Runtime for Evidence-Native, Memory-Augmented and Explainable Frontier AI Systems},
author={Edema, Oti},
journal={Submitted to the Journal of Artificial Intelligence Research},
year={2026}
}
Licence
MIT Licence.
Author
Oti Edema
GitHub: https://github.com/OtiEdema
LinkedIn: https://www.linkedin.com/in/oti-e-34838485/
Metadata
Release files for otillm 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| otillm-0.2.0.tar.gz | 12.1 kB | Without provenance | Details for otillm-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| otillm-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for otillm-0.2.0-py3-none-any.whl |
Total release size: 26.3 kB
Release files / otillm-0.2.0.tar.gz
| Download URL | otillm-0.2.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01868bf15c44fefb19bb225d19190979a1bcbaa0a1ff8a94b5111403edf0efc7
|
|
BLAKE2b-256 checksum How to use checksums |
402ca8dc16f7fc204bd88f5c686deea7b51fd79bf1f031f708845389ebce3f55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / otillm-0.2.0-py3-none-any.whl
| Download URL | otillm-0.2.0-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63d51e2d9c090c3632bcd1757762cbb52c435f10427e60ad88f94a911502cd71
|
|
BLAKE2b-256 checksum How to use checksums |
a4894f16ef56f9d15da74c9b5966d0295535d012778a898622d434180b720f89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for otillm 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.