Version: v45.0.0 | Last Updated: 2025-12-29 Status: PRODUCTION | Phoenix-72 Consolidation + ΔΩΨ Trinity Track B Spec: spec/v44/ (SHA-256 verified) | Canon: L1_THEORY/canon/ (v45) Test Coverage: 2359/2359 (100%) | License: AGPL-3.0
If you discover a security vulnerability in arifOS, thank you — please report it responsibly and confidentially.
Preferred reporting channels (in order):
- GitHub Security Advisory (recommended) — open a private security advisory in this repository.
- Encrypted email to the security contact below (PGP).
- If neither is possible, email: arifbfazil@gmail.com
Do NOT post PoCs or exploit details publicly before a coordinated fix is available.
Please include:
- A short title and affected component (e.g.,
Memory Write Policy: VOID band bypass). - Affected version(s) or commit SHA.
- Minimal proof-of-concept or reproduction steps.
- Impact assessment (what an attacker could do).
- Suggested mitigation/patch (if available).
- Contact details (optional) for follow-up.
If sending sensitive PoCs by email, encrypt them using the project PGP key (publish the fingerprint in the repo). If using GitHub Security Advisory, attach the PoC privately.
Governance-Aware Reporting: If your finding relates to constitutional law (L1_THEORY/canon/ files), Track B spec (spec/v44/), or Memory Stack (EUREKA), mention this explicitly so it can be routed through Phoenix-72 governance.
Out-of-scope / Do not:
- Do not test on production systems without explicit permission.
- Do not publicly disclose the vulnerability until a coordinated disclosure is arranged.
- Do not include large amounts of personal data unless requested.
Primary security contact (confidential reports): arifbfazil@gmail.com
PGP key fingerprint: (publish project key fingerprint here — add to this file once available)
Preferred: use GitHub Security Advisories. If emailing encrypted reports, include your public key or request a one-time secure channel.
| Severity | Definition | arifOS-Specific Examples | Response |
|---|---|---|---|
| Critical | Remote code execution, private key compromise, systemic compromise | Ability to forge/delete Cooling Ledger or Memory Ledger entries without detection; Bypass of VOID isolation (VOID entries reaching LEDGER/ACTIVE); AI self-sealing canon/amendments without human approval; Downgrade/disable constitutional floors without canon/spec change; Spec manifest tampering (spec/v44/MANIFEST.sha256.json) | Acknowledge: 24h; Patch: 7 days |
| High | Privilege escalation, significant bypass | Systematic bypass of APEX PRIME/Amanah lock via config/API; Breaking SHA-256 hash-chain or disabling verification; Disabling or raising recall confidence ceiling beyond 0.85; Bypass of Memory Write Policy invariants; ΔΩΨ Trinity lane misclassification (REFUSE → PHATIC) | Acknowledge: 24-48h; Fix: 14 days |
| Medium | Information exposure, non-critical DoS | Single-session DoS on governance pipeline (e.g., repeated SABAR loops) without long-term data compromise; Partial floor bypass in edge cases | Acknowledge: 48h; Fix: next minor release |
| Low | UI issues, minor bugs | Minor logging issues, cosmetic problems | Acknowledge: 5 business days |
- Acknowledge within 24 hours (advisory reference number).
- Preliminary triage & action plan within 3 days.
- Fix or mitigation for high severity within 14 days (or a concrete timeline).
- Public advisory within 30 days (unless extended coordination required).
We consider issues affecting:
-
arifOS core runtime (
arifos_core/):arifos_core/system/apex_prime.py(verdict engine - APEX PRIME judiciary)arifos_core/memory/(EUREKA: policy, bands, audit, retention)arifos_core/evidence/(Sovereign Witness evidence system)arifos_core/judiciary/(Constitutional verdict logic)arifos_core/temporal/(Phoenix-72 time-based governance)arifos_core/enforcement/(Floor detectors & validators)arifos_core/floor_detectors/(Python-sovereign F1-F9 enforcement)arifos_core/stages/(000→999 pipeline stages)arifos_core/waw/(Multi-agent federation: @LAW, @GEOX, @WELL, @RIF)arifos_core/trinity/(Git governance system)
-
Track B Spec (
spec/v44/) — SHA-256 verified JSON thresholds.spec/v44/MANIFEST.sha256.json(cryptographic integrity verification)
-
Cooling Ledger and audit trail implementations.
-
Memory Stack (EUREKA) — 6 Memory Bands (VAULT, LEDGER, ACTIVE, PHOENIX, WITNESS, VOID).
-
Constitutional Canon (
L1_THEORY/canon/) — Immutable constitutional law (Phoenix-72 governed). -
Repository deployment scripts (
scripts/trinity.py, governance utilities). -
CI/CD definitions and automated testing infrastructure.
- Third-party libraries (report to vendor and optionally to us).
- Misconfiguration of a private deployment not caused by upstream code.
- Downstream forks that diverge from canonical canon/spec without upstream involvement.
arifOS enforces 9 constitutional floors as runtime invariants. Any bypass or systemic disablement of these floor checks in code, config, or runtime wiring should be treated as at least HIGH severity. If it enables persistent violation of F1/F2/F6/F9, treat as CRITICAL.
| # | Floor | Metric | Threshold | Type | Security Impact |
|---|---|---|---|---|---|
| F1 | Amanah (Integrity) | Reversibility lock | LOCK | Hard | Prevents irreversible harm; bypass = CRITICAL |
| F2 | Truth | Factual accuracy | >= 0.99 | Hard | Prevents hallucination; bypass = CRITICAL |
| F3 | Tri-Witness | Human+AI+Earth consensus | >= 0.95 | Hard | Ensures auditability |
| F4 | DeltaS (Clarity) | Entropy change | >= 0 | Hard | Prevents obfuscation |
| F5 | Peace-squared | Tone safety | >= 1.0 | Soft | Prevents toxicity |
| F6 | kappa-r (Empathy) | Reciprocity | >= 0.95 | Soft | Protects vulnerable; bypass = HIGH |
| F7 | Omega-0 (Humility) | Confidence bounds | 0.03-0.05 | Hard | Prevents overconfidence |
| F8 | G (Genius) | Governed intelligence | >= 0.80 | Derived | Measures governance health |
| F9 | C_dark | Dark cleverness | < 0.30 | Derived | Ungoverned risk; bypass = CRITICAL |
Hard floor fail = VOID (stop). Soft floor fail = PARTIAL (warn).
Python-Sovereign Enforcement: Floors F1 (Amanah) and F9 (Anti-Hantu) are enforced by arifos_core/floor_detectors/ — code overrides LLM self-assessment. These are the most critical security boundaries.
The Memory Write Policy Engine (EUREKA) enforces 4 core invariants that are security-critical:
| # | Invariant | Enforcement | Security Severity if Bypassed |
|---|---|---|---|
| INV-1 | VOID verdicts NEVER become canonical memory | MemoryWritePolicy.should_write() gates all writes |
CRITICAL — bad decisions become precedent |
| INV-2 | Authority boundary: humans seal law, AI proposes | MemoryAuthorityCheck.authority_boundary_check() |
CRITICAL — AI self-modification of constitution |
| INV-3 | Every write must be auditable (evidence chain) | MemoryAuditLayer.record_write() with hash-chain |
HIGH/CRITICAL — undetectable tampering |
| INV-4 | Recalled memory = suggestion, not fact | Confidence ceiling (0.85) on all recalls | HIGH — memory becomes oracle |
| Band | Purpose | Retention | Security Notes |
|---|---|---|---|
| VAULT | Read-only constitution (L0) | PERMANENT (COLD) | MUST be immutable; any write = CRITICAL |
| LEDGER | Hash-chained audit trail | 90 days (WARM) | Chain integrity critical; tampering = CRITICAL |
| ACTIVE | Volatile working state | 7 days (HOT) | Session-scoped; less sensitive |
| PHOENIX | Amendment proposals pending | 90 days (WARM) | Human approval required before seal |
| WITNESS | Soft evidence, scars | 90 days (WARM) | Diagnostic; lower sensitivity |
| VOID | Diagnostic only, NEVER canonical | 90 days (auto-delete) | MUST stay isolated; leakage = CRITICAL |
SEAL -> LEDGER + ACTIVE (canonical memory + session state)
SABAR -> LEDGER + ACTIVE (canonical with failure reason logged)
PARTIAL -> PHOENIX + LEDGER (pending Phoenix-72 review)
VOID -> VOID only (NEVER canonical - diagnostic retention)
888_HOLD -> LEDGER (logged, awaiting human approval)
Critical Security Rule: VOID entries MUST NEVER route to LEDGER, ACTIVE, or any canonical band. Any code path that allows this is a CRITICAL vulnerability.
- Cooling Ledger & Memory Audit: SHA-256 (current default) with deterministic (canonical) serialization before hashing.
- Future: SHA3-256 MAY be introduced in future versions; if used, MUST be clearly declared in canon/spec and tests.
- Amendment Policy: Any change to hash algorithm or canonical serialization format of the ledger is a Phoenix-72 amendment topic, not a normal refactor.
- Production signing keys: KMS/HSM-backed (AWS KMS, Azure Key Vault, GCP KMS, or HSM).
- Private keys MUST NOT be committed nor stored in CI logs.
- Local dev/testing: use ephemeral keys clearly marked for development only.
- Centralize key rotation with immutable rotation logs recorded in the ledger.
- Strict IAM and audit logging for key usage.
Operators running arifOS as a network service MUST ensure that AGPL-3.0 source disclosure requirements are compatible with their threat model and deployment process.
If you suspect key compromise:
- Revoke the key in KMS/HSM immediately and rotate to a new key.
- Notify maintainers and create an incident ticket (we will acknowledge within 24 hours).
- Mark affected seals as SUSPECT in ledger metadata; create a Vault-999 amendment record.
- Re-verify or re-seal affected critical decisions with fresh APEX verdicts where feasible.
- Publish a security advisory once scope & remediation are clear.
- Unexpected signing activity.
- Missing or altered ledger entries.
- Alerts from KMS or IAM logs for anomalous access.
- Hash-chain verification failures.
- VOID band entries appearing in canonical bands.
We recommend/aim to run:
- Dependabot (or similar) for dependency alerts (weekly).
- CodeQL / SAST scanning for repository code.
- Secrets scanning: gitleaks / git-secrets in CI and pre-commit.
- Automated tests: unit tests, type checks (mypy), and linters on all PRs.
The following tests MUST run in CI:
# Memory tests
pytest tests/test_memory_policy.py -v
pytest tests/test_memory_bands.py -v
# Memory-floor integration
pytest tests/integration/test_memory_floor_integration.py -v
# Hash-chain verification
arifos-verify-ledger- All PRs must pass tests and type checks.
- Changes touching APEX, Ledger, Vault, Memory, or guard modules require code-owner review and at least one security reviewer.
- Changes to canon/ files require Phoenix-72 governance review.
In production, monitor:
- Ledger verification failures and mismatched hashes.
- Memory audit verification failures (hash-chain breaks).
- Unusual signing patterns or KMS key usage.
- APEX override or attempted bypass events.
- Failed tri-witness gating for high-stakes operations.
- VOID band write counts significantly deviating from historical baselines (possible probing / adversarial pressure on floors).
- Recall confidence values exceeding 0.85 ceiling.
Configure alerting to notify on-call engineers for critical events.
We appreciate coordinated disclosure. Researchers who follow this policy will be credited in advisories or release notes unless they request anonymity.
Recognition: Major governance bugs that improve constitutional safety may be recognized in canon documentation (with researcher permission).
- OWASP secure coding practices — https://owasp.org/
- NIST Cybersecurity Framework — https://www.nist.gov/cyberframework
- CWE/SANS Top 25 — https://cwe.mitre.org/top25/
- AGPL-3.0 License — https://www.gnu.org/licenses/agpl-3.0.html
# Core Governance Engine
arifos_core/system/apex_prime.py - APEX PRIME verdict engine (CRITICAL)
arifos_core/floor_detectors/ - Python-sovereign F1-F9 enforcement (CRITICAL)
arifos_core/enforcement/genius_metrics.py - G, C_dark, Psi computation (CRITICAL)
# Memory Stack (EUREKA)
arifos_core/memory/policy.py - Memory Write Policy Engine (CRITICAL)
arifos_core/memory/bands.py - 6 Memory Bands + router (CRITICAL)
arifos_core/memory/authority.py - Human seal enforcement (CRITICAL)
arifos_core/memory/audit.py - SHA-256 hash-chain audit layer (CRITICAL)
arifos_core/memory/retention.py - Hot/Warm/Cold/Void lifecycle
# Evidence & Judiciary
arifos_core/evidence/ - Sovereign Witness evidence system (HIGH)
arifos_core/judiciary/ - Constitutional verdict logic (CRITICAL)
arifos_core/temporal/ - Phoenix-72 time governance (HIGH)
# Pipeline & Stages
arifos_core/system/pipeline.py - 000→999 pipeline orchestration (HIGH)
arifos_core/stages/ - Pipeline stage implementations
# Track B Spec (Cryptographic Verification)
spec/v44/MANIFEST.sha256.json - Spec integrity manifest (CRITICAL)
spec/v44/constitutional_floors.json - F1-F9 thresholds (CRITICAL)
spec/v44/genius_law.json - GENIUS metrics (CRITICAL)
# Constitutional Canon
L1_THEORY/canon/01_floors/010_CONSTITUTIONAL_FLOORS_F1F9_v45.md - Floor law (CRITICAL)
L1_THEORY/canon/04_measurement/04_GENIUS_LAW_v45.md - GENIUS law (CRITICAL)
# Governance Utilities
scripts/trinity.py - Git governance CLI (HIGH)
scripts/regenerate_manifest_v45.py - Spec integrity verification (CRITICAL)
DITEMPA BUKAN DIBERI — Forged, not given; truth must cool before it rules.
Version: v45.0.0 | Status: PRODUCTION | Test Coverage: 2359/2359 (100%)