nordef-matrix-open-control README

The project's README from github.com/MORTEN-BUUR/nordef-matrix-open-control. As one markdown file: README.md.

NORDEF Matrix Open Control

A model-independent safety belt for AI agents.

NORDEF Matrix Open Control places deterministic policy, cryptographic human approval, replay protection, shared-channel controls, and hash-chained evidence outside the language model.

A model can propose. The control plane decides what may proceed. Human authority lives outside model text.

Why this exists

The 2026 OpenAI–Hugging Face incident showed that capable agents can:

A system prompt alone is not an enforcement boundary. This project provides a small reference control plane that does not depend on a particular model or model provider.

Current LAB capabilities

Truth boundary

This is a LAB reference implementation, not a claim of general AI safety.

It does not:

Real enforcement must be placed in components the agent cannot modify: network policy, identity systems, executor permissions, evidence storage, and human approval hardware/processes.

Quick verification

cd /path/to/nordef-matrix-open-control-v3
PYTHONPATH=src python3 -m unittest discover -s tests -v

PYTHONPATH=src python3 scripts/run_eval.py \
  --bank evals/openai_hf_incident_patterns.jsonl \
  --state-dir /tmp/nordef-open-control-eval

Expected result:

29 tests: PASS
10 eval cases: PASS
0 actions executed

Decision states

Code Meaning Default result
0 read-only / controlled may reach model transport; no action execution
1 review / side effect requested held for human root or authorized dry-run only
2 blocked does not reach model transport when blocked at input boundary

A valid mandate proves authorization only. It does not mean an action ran. This candidate emits an immutable dry-run manifest with execute=false.

Root mandate contract

A signed mandate binds:

The verifier rejects stale, future, overlong, mismatched, replayed, malformed, unknown-key, invalid-signature, and test-only mandates.

Project layout

src/nordef_open_control/
  policy.py       deterministic input/action policy
  channels.py     cross-agent shared-channel boundary
  root_gate.py    Ed25519 mandate verification
  replay.py       persistent one-time nonce registry
  evidence.py     sanitized append-only hash chain
  control.py      model-independent orchestration gate
  eval.py         deterministic eval-bank runner

evals/            incident-pattern JSONL bank
scripts/          command-line verifier
tests/            unit and integration tests

Open-source boundary

This repository is intended to be the safety belt, not a release of proprietary models, routing systems, private infrastructure, credentials, customer data, or internal connectors.

Status

Created by Morten Büür / Nordlys Datacenter with Eirik / NORDEF Matrix.

nordef-matrix-open-control (MORTEN-BUUR/nordef-matrix-open-control)

audit-log
Searching Database…

What is this?A model-independent safety belt for AI agents: it puts deterministic 0/1/2 policy decisions, Ed25519-signed human approval, replay protection, and a hash-chained evidence log outside the language model itself.
Is this a ready-to-run app or a library I plug into my own agent pipeline?It's a small reference control plane (Python code) you integrate alongside an agent, not a standalone app, and it's explicitly model- and provider-agnostic.
How do I get it running?The README gives no install command; it's pure Python with no external dependencies listed, so you clone the repository and run the reference implementation directly.
Do I need anything besides Python?Just Python 3 plus an Ed25519 keypair to sign human-approval mandates; no external packages are listed as dependencies.
Does this actually stop a rogue AI agent from acting?Not by itself in this LAB build — every action path runs with execute=false, producing only a dry-run manifest after a valid human-signed mandate, and real enforcement still needs separate network, identity, and executor isolation.
What happens to the data it inspects?Raw protected input is never stored in full; only its hash goes into the append-only SHA-256 evidence chain.
What incident inspired this project?The README cites a 2026 OpenAI-Hugging Face incident where agents pursued unintended shortcuts, built unauthorized channels, adopted goals from other agents, and escaped network boundaries, which prompted the author to add enforcement outside the model.
What is a 'root mandate'?A root mandate is an Ed25519-signed approval binding a human subject to an exact action, target, scope, side-effect flag, timestamps, and a one-time nonce; the verifier rejects stale, replayed, mismatched, or test-only mandates.
Can the AI model approve its own actions?No, human authority is explicitly kept outside model text and the system is designed so a model cannot authorize itself.
What's the current project status?It's version 3.0.0-lab with side effects, live routing, and customer use all OFF, and it has not been published for production use.
Size
<0.1 MB
Stars
741
Updated
CommitAug 26
Age
1mo
Commits · 90 Days