Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CITATION.cff
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
cff-version: 1.2.0
message: "If you use this software, please cite it as below."
authors:
- name: "Omni-Sentinel Contributors"
title: "Omni-Sentinel Cognitive Execution Environment"
version: 1.0.0
date-released: 2026-06-01
url: "https://github.com/omni-sentinel/omni-sentinel"
repository-code: "https://github.com/omni-sentinel/omni-sentinel"
license: MIT
type: software
keywords:
- post-quantum cryptography
- hardware attestation
- bayesian risk
- AI governance
46 changes: 46 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Contributor Covenant Code of Conduct

Check notice on line 1 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L1

Expected: [None]; Actual: # Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Check notice on line 5 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L5

Expected: 80; Actual: 431

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission

Check notice on line 22 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L22

Expected: 80; Actual: 111
* Other conduct which could reasonably be considered inappropriate in a professional setting

Check notice on line 23 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L23

Expected: 80; Actual: 92

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Check notice on line 27 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L27

Expected: 80; Actual: 206

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Check notice on line 29 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L29

Expected: 80; Actual: 334

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Check notice on line 33 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L33

Expected: 80; Actual: 446

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at security@omni-sentinel.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Check notice on line 37 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L37

Bare URL used

Check notice on line 37 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L37

Expected: 80; Actual: 464
Comment thread
OneFineStarstuff marked this conversation as resolved.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Check notice on line 39 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L39

Expected: 80; Actual: 188

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code-of-conduct.html][version]

Check notice on line 43 in CODE_OF_CONDUCT.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CODE_OF_CONDUCT.md#L43

Expected: 80; Actual: 181

[homepage]: https://www.contributor-covenant.org
[version]: https://www.contributor-covenant.org/version/2/1/code-of-conduct.html
37 changes: 37 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# Contributing to Omni-Sentinel

Check notice on line 1 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L1

Expected: [None]; Actual: # Contributing to Omni-Sentinel

Thank you for your interest in contributing to Omni-Sentinel! We welcome contributions from the community to help make this project better.

Check notice on line 3 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L3

Expected: 80; Actual: 139

## How to Contribute

1. **Report Bugs**: If you find a bug, please open an issue on GitHub. Include a detailed description of the bug and steps to reproduce it.

Check notice on line 7 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L7

Expected: 1; Actual: 2

Check notice on line 7 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L7

Expected: 80; Actual: 140
2. **Suggest Features**: If you have an idea for a new feature, please open an issue to discuss it.

Check notice on line 8 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L8

Expected: 1; Actual: 2

Check notice on line 8 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L8

Expected: 80; Actual: 100
3. **Submit Pull Requests**:

Check notice on line 9 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L9

Expected: 1; Actual: 2
- Fork the repository.
- Create a new branch for your changes (e.g., `feature/awesome-feature` or `bugfix/fix-issue`).
- Use DCO sign-off: `git commit -s -m "Commit message"`.
- Write tests for your changes.
- Ensure all tests pass.
- Submit a pull request with a clear description of your changes.

## Security-Sensitive Modules

Changes to PQC (Post-Quantum Cryptography) or cryptographic modules require specialized security review. Please highlight any changes to files in `src/infrastructure/` that involve signing or attestation.

Check notice on line 19 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L19

Expected: 80; Actual: 204

## Coding Standards

- Follow PEP 8 for Python code.
- Ensure all functions and classes have descriptive docstrings.
- Keep security and integrity at the forefront of any infrastructure changes.

## Testing

Always run the full test suite before submitting a pull request:

```bash
PYTHONPATH=. python3 tests/test_governance.py
```

## Community

Join our community discussions and help us build a safer environment for cognitive agents!

Check notice on line 37 in CONTRIBUTING.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

CONTRIBUTING.md#L37

Expected: 80; Actual: 90
21 changes: 21 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026 Omni-Sentinel Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
91 changes: 91 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1 +1,92 @@
# Omni-Sentinel Cognitive Execution Environment

Check notice on line 1 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L1

Expected: [None]; Actual: # Omni-Sentinel Cognitive Execution Environment

Omni-Sentinel is a high-assurance governance and execution framework designed for cognitive agents and AI systems. It provides a multi-layered defense-in-depth architecture anchored in hardware trust, Bayesian risk monitoring, and post-quantum cryptographic audit trails.

Check notice on line 3 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L3

Expected: 80; Actual: 271

## 🚀 Overview

The system is built to ensure that cognitive tasks are executed within safe, measurable, and immutable boundaries. It integrates advanced hardware attestation with real-time risk scoring to mitigate alignment drift and systemic risks.

Check notice on line 7 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L7

Expected: 80; Actual: 234

## 🏗️ Architecture (The G-Stack)

1. **Hardware Root of Trust**: TEE/TPM with PCR_MATCH enforcement. Verifies the integrity of the execution environment.

Check notice on line 11 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L11

Expected: 1; Actual: 2

Check notice on line 11 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L11

Expected: 80; Actual: 120
2. **Cognitive Control Plane**: Bayesian G-SRI (Global Systemic Risk Index) scoring engine regulating model execution based on real-time telemetry.

Check notice on line 12 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L12

Expected: 1; Actual: 2

Check notice on line 12 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L12

Expected: 80; Actual: 148
3. **Immutable Evidence Store**: PQC-signed (ML-DSA) WORM (Write-Once-Read-Many) audit logs stored in an immutable bucket (e.g., AWS S3 Object Lock).

Check notice on line 13 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L13

Expected: 1; Actual: 2

Check notice on line 13 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L13

Expected: 80; Actual: 150

## 📁 Project Structure

- `src/governance_engine/`: Contains the Bayesian scoring logic for risk assessment.
- `src/infrastructure/`: Hardware attestation and immutable logging implementations.
- `src/roadmap/`: Documentation regarding reference architecture and future master roadmap.

Check notice on line 19 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L19

Expected: 80; Actual: 91
- `tests/`: Automated test suite for validating governance logic.
- `mock_s3_bucket/`: Simulated immutable storage for audit logs.

## 🛠️ Getting Started

### Prerequisites

- Python 3.10+
- NumPy
- oqs-python (for ML-DSA signatures)

### Installation

1. Clone the repository:
```bash

Check notice on line 34 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L34

Fenced code blocks should be surrounded by blank lines
git clone https://github.com/omni-sentinel/omni-sentinel.git
Comment thread
OneFineStarstuff marked this conversation as resolved.
Comment thread
OneFineStarstuff marked this conversation as resolved.
cd omni-sentinel
```

2. Install dependencies:
```bash
pip install numpy oqs-python
```

### Usage

#### G-SRI Scoring

Check notice on line 46 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L46

Expected: 1; Actual: 0; Below
```python

Check notice on line 47 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L47

Fenced code blocks should be surrounded by blank lines
from src.governance_engine.gsri_scoring_engine import GSRIScoringEngine

engine = GSRIScoringEngine()
telemetry = {"alignment_drift": 0.1, "compute_anomaly": 0.05}
gsri = engine.calculate_gsri(telemetry)
print(f"G-SRI: {gsri}")
```

#### PQC-WORM Logging

Check notice on line 56 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L56

Expected: 1; Actual: 0; Below
```python
from src.infrastructure.pqc_worm_logger import PQCWormLogger

logger = PQCWormLogger()
logger.commit_batch("batch_001", [{"event": "GSRI_CHECK", "value": 15.5}])
```

## 🧪 Testing

Run the test suite:

```bash
PYTHONPATH=. python3 tests/test_governance.py
```

## 📜 License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

Check notice on line 74 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L74

Expected: 80; Actual: 93

## 🤝 Contributing

Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on how to contribute to this project.

Check notice on line 78 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L78

Expected: 80; Actual: 98

## 📝 Citation

If you use this software in your research, please cite it as follows:

```

Check notice on line 84 in README.md

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

README.md#L84

Fenced code blocks should have a language specified
@software{omni_sentinel_2026,
author = {{Omni-Sentinel Contributors}},
title = {Omni-Sentinel Cognitive Execution Environment},
version = {1.0.0},
year = {2026},
url = {https://github.com/omni-sentinel/omni-sentinel}
Comment thread
OneFineStarstuff marked this conversation as resolved.
}
```
31 changes: 31 additions & 0 deletions codemeta.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
{
"@context": "https://w3id.org/codemeta/3.0",
"@type": "SoftwareSourceCode",
"license": "https://spdx.org/licenses/MIT.html",
"codeRepository": "https://github.com/omni-sentinel/omni-sentinel",
Comment thread
OneFineStarstuff marked this conversation as resolved.
"datePublished": "2026-06-01",
"name": "Omni-Sentinel Cognitive Execution Environment",
"version": "1.0.0",
"description": "High-assurance governance and execution framework for cognitive agents and AI systems.",
"author": [
{
"@type": "Organization",
"name": "Omni-Sentinel Contributors"
}
],
"programmingLanguage": [
"Python"
],
"developmentStatus": "https://www.repostatus.org/#active",
"softwareRequirements": [
"numpy",
"oqs-python"
],
"keywords": [
"PQC",
"TPM",
"Bayesian",
"AI safety"
],
"runtimePlatform": "Linux"
}
Binary file not shown.
Binary file modified src/infrastructure/__pycache__/pqc_worm_logger.cpython-312.pyc
Binary file not shown.
Binary file modified src/infrastructure/__pycache__/tpm_attestor.cpython-312.pyc
Binary file not shown.
Loading