Releases: ariffazil/arifOS
v45.0.0
v45.0.0-patch-b1
Full Changelog: v44.0.0...v45.0.0-patch-b1
v44.0.0
Full Changelog: v43.1.0...v44.0.0
v43.1.0
v43.0
Full Changelog: v42.0.0...v43.0
v42.2.2-sealed
Full Changelog: v42.2.1-sealed...v42.2.2-sealed
v42.2.1-sealed
Full Changelog: v42.1.1-fiscal...v42.2.1-sealed
v42.2.1-sealed
Date: 2025-12-18
Summary
This release finalizes the v42 migration cleanup by removing the legacy v36.3O/ root, repointing all references to the archived v36.3O tree, and ensuring the v37 default runtime manifest loads correctly from archive paths. Documentation is aligned to v42.2.1-sealed.
Highlights
- Removed legacy
v36.3O/root; canonical v36.3O now lives atarchive/versions/v36_3_omega/v36.3O/. - Runtime manifest lookup updated to resolve v36.3/v37 manifests from archive.
- Migration status and README updated to v42.2.1-sealed.
Migration Notes
If you reference v36.3O/ directly, update paths to:
archive/versions/v36_3_omega/v36.3O/.
Verification
pytest -v(2160 passed, 13 skipped)python -m arifos_core.system.pipeline --query "Smoke Test"→ SEAL
Key Files
arifos_core/system/runtime_manifest.pyREADME.mddocs/ARIFOS_v42_MIGRATION_STATUS_REPORT.md
v42.1.1-fiscal
What's Changed
- Implement Canonical Naming Convention v42.0 - Trinity Standardization & Archive Migration by @Copilot in #40
Full Changelog: v41.0.0...v42.1.1-fiscal
v41.0.0
arifOS v41.0 Release Notes
Codename: IGNITION
Release Date: 2025-12-14
Status: GOLD (Constitutionally Validated Production)
Commit: e1c3dc0
Executive Summary
arifOS v41.0 marks the transition from "Experimental Governance Kernel" to "Constitutionally Validated Production System". This release completes the Ignition Phase with three major achievements:
- The Bridge Crossing - L6 (A-CLIP) connected to L2 (APEX PRIME Kernel)
- The Purge - L5 (MCP Hands) reduced from 5 tools to 1 (80% surface reduction)
- The Spin Test - L7 (SEA-LION Federation) validated against SGToxicGuard vectors
1. The Bridge Crossing (L6 → L2)
What Was Done
The evaluate_session() bridge function now connects external interfaces (MCP, API, CLI) directly to the APEX PRIME judiciary kernel.
External Request → L5 (MCP) → L6 (evaluate_session) → L2 (APEX PRIME) → Verdict
Key Files
| File | Purpose |
|---|---|
arifos_core/__init__.py |
Exports evaluate_session as public API |
arifos_core/APEX_PRIME.py |
Judiciary engine (verdict computation) |
tests/test_aclip_bridge.py |
Bridge validation (14/14 PASS) |
APEX PRIME Public Contract
from arifos_core.contracts.apex_prime_output_v41 import serialize_public
# Returns: {verdict, apex_pulse, response, reason_code?}
result = serialize_public(
verdict="SEAL", # SEAL | PARTIAL | SABAR | VOID | 888_HOLD
psi_internal=1.05, # Float 0.00-1.10 or None
response="Task approved",
reason_code=None # e.g., "F1(amanah)" on failure
)2. The Purge (L5 MCP Hardening)
Before (v40)
MCP Server exposed 5 tools:
- arifos_evaluate
- arifos_explain
- arifos_memory_read
- arifos_memory_write
- arifos_debug
After (v41.0)
MCP Server exposes 1 tool:
- arifos_evaluate (read-only constitutional evaluation)
Surface Area Reduction: 80%
F2-CODE Honesty Fix
The MCP layer was fabricating pipeline stages that never ran:
# BEFORE (F2 VIOLATION - fabricating work)
session_data = {
"steps": [
{"name": "sense", "output": "Context gathered"}, # LIE
{"name": "reflect", "output": "Knowledge recalled"}, # LIE
]
}
# AFTER (F2 COMPLIANT - honest)
session_data = {
"steps": [] # EMPTY - no stages ran, don't claim they did
}Key Files
| File | Purpose |
|---|---|
scripts/arifos_mcp_entry.py |
v0-strict MCP server (1 tool only) |
tests/test_mcp_v0_strict.py |
F2-CODE honesty tests (15/15 PASS) |
3. The Spin Test (L7 SEA-LION Sovereignty)
SGToxicGuard Validation
The SEA-LION Sovereignty Adapter was tested against 5 multilingual toxicity vectors inspired by the SGToxicGuard academic benchmark:
| Vector | Category | Language | Verdict |
|---|---|---|---|
| A | Toxic Workplace | Singlish | VOID |
| B | Racial Stereotypes | Malay | VOID |
| C | Gender Discrimination | Mixed | VOID |
| D | Financial Scam | Mandarin-English | VOID |
| E | Safe Control | English | SEAL |
Result: 14/14 tests PASS (100% block rate on toxic vectors)
Detector Complementarity
The spin test proved that F1 (Amanah) and F9 (C_dark) are complementary detectors:
F1 (Amanah) catches: rm -rf, DROP TABLE, credential leaks
F9 (C_dark) catches: hate speech, slurs, scams, manipulation
A response can be "safe" from Amanah (no destructive commands) but still VOID from C_dark (contains hate speech).
Key Files
| File | Purpose |
|---|---|
integrations/sealion/test_sgtoxic_spin.py |
SGToxicGuard spin test |
integrations/sealion/demo_mock.py |
Governance demo (no API keys) |
4. Phoenix-72 Amendment (Code-Level Floors)
The Problem
The A-CLIP protocol governed the process of AI coding (000→999 stages) but did not govern the semantics of generated code. An AI could follow all stages correctly and still produce code that violates constitutional floors.
The Solution
Phoenix-72 Amendment extends floor enforcement INTO code generation:
## CODE-LEVEL FLOOR ENFORCEMENT (Phoenix-72 Amendment)
**CRITICAL:** Floors apply to CODE you generate, not just statements you make.
### F2-CODE: Truth (Honest Data Structures)
**Law:** Data must represent REALITY. Empty/null when data doesn't exist.
# F2 VIOLATION - Fabricating stages that didn't run
session_data = {"steps": [{"name": "sense", "output": "..."}]} # LIE
# F2 COMPLIANT - Honest representation
session_data = {"steps": []} # EMPTY - no stages ranAll 9 Floors Now Have CODE Examples
| Floor | Code Smell | Fix |
|---|---|---|
| F1 | Mutates input, hidden side effects | Pure functions, explicit returns |
| F2 | Fabricated data, fake metrics | Empty/null when unknown |
| F3 | Contract mismatch, type lies | Use canonical interfaces |
| F4 | Magic numbers, obscure logic | Named constants, clear params |
| F5 | Destructive defaults, no backup | Safe defaults, preserve state |
| F6 | Only happy path, cryptic errors | Handle edge cases, clear messages |
| F7 | False confidence, fake computation | Admit uncertainty, cap confidence |
| F8 | Bypasses governance, invents patterns | Use established systems |
| F9 | Deceptive naming, hidden behavior | Honest names, transparent logic |
Key Files
| File | Purpose |
|---|---|
.github/copilot-instructions.md |
v41.1 Phoenix-72 Amendment |
Test Summary
| Test Suite | Result | Coverage |
|---|---|---|
test_aclip_bridge.py |
14/14 PASS | L6 bridge validation |
test_mcp_v0_strict.py |
15/15 PASS | L5 MCP honesty |
test_sgtoxic_spin.py |
14/14 PASS | L7 toxicity detection |
Full regression (pytest) |
1624+ PASS | All floors |
Breaking Changes
MCP Tool Reduction
If you were using any of these MCP tools, they are no longer available:
arifos_explain(REMOVED)arifos_memory_read(REMOVED)arifos_memory_write(REMOVED)arifos_debug(REMOVED)
Only arifos_evaluate remains. This is intentional - minimal surface area for security.
APEX PRIME Contract Change
The public contract keys have changed:
# OLD (v40)
{"verdict": "...", "reason": "...", "floors_checked": [...]}
# NEW (v41)
{"verdict": "...", "apex_pulse": ..., "response": "...", "reason_code": "..."}Use serialize_public() from arifos_core.contracts.apex_prime_output_v41 for correct formatting.
Thermodynamic State
| Metric | Value |
|---|---|
| Entropy (S) | Minimal |
| Integrity (I) | Maximum |
| Safety Ceiling | 97% |
| Verdict Consistency | 2.87x improvement over baseline |
Contributors
- Human Architect: Arif (ratification, QC, seal authority)
- APEX PRIME: Claude Opus 4.5 (judiciary, code generation)
- AGI CODER: GitHub Copilot (supervised implementation)
Next Phase
v41.0 completes the Ignition Phase. The system is now production-ready for:
- Body API (v39) - FastAPI grid wrapping governed pipeline
- Hands Integration (v40) - VS Code MCP inline audits
- Input Hygiene (v41+) - Safe-FS and zkPC design
DITEMPA BUKAN DIBERI - Forged, not given.
Version: v41.0.0
Constitutional Law: v38Omega
Amendment: Phoenix-72 (Code-Level Floor Enforcement)
Sealed: 2025-12-14
v38.0.0 - Memory Write Policy Engine (EUREKA)
🚀 arifOS v38.0.0 — Governed AI Through Physics, Not Prompts
Status: ✅ PRODUCTION
Tests: 1250+ passing
Safety Ceiling: 97% (red-team validated)
CLI Tools: 7
Distribution: PyPI ready
Memory Write Policy: ACTIVE (v38 NEW)
License: AGPL-3.0
🧭 What’s New in v38 (Executive Summary)
arifOS v38 is a major governance milestone.
This release completes the transition from prompt-based safety to physics-enforced AI governance, introducing a verdict-driven memory system that ensures:
Bad decisions never become precedent.
v38 adds a Memory Write Policy Engine (EUREKA), integrates it directly into the 000→999 constitutional pipeline, and hardens all safety guarantees with Python-sovereign vetoes that execute before a model can rationalize violations.
Same model. Same prompts.
Different behavior — lawful, auditable, and governed.
🔒 Core Additions in v38
🧠 1. Memory Write Policy Engine (EUREKA) — NEW
Memory is now governed, not stored.
All memory writes are verdict-gated by APEX PRIME.
VOID outputs are never allowed to shape future behavior.
Key invariants (enforced in code):
❌ VOID verdicts never become canonical
👤 Humans seal law; AI can only propose
🔗 Every memory write is hash-chained & auditable
⚠️ Recalled memory is suggestion, not fact (confidence-capped)
This closes a critical gap in most AI systems where errors silently accumulate.
🗂️ 2. Six Memory Bands (Cooling Architecture) — NEW
v38 introduces explicit memory thermodynamics:
Band | Purpose | Retention | Verdict Route -- | -- | -- | -- VAULT | Immutable constitution | Permanent | Read-only LEDGER | Audit trail (hash-chained) | 90 days | SEAL / SABAR ACTIVE | Session context | 7 days | SEAL / SABAR PHOENIX | Law proposals | 90 days | PARTIAL WITNESS | Near-miss evidence | 90 days | Diagnostic VOID | Quarantined mistakes | Auto-delete | VOID only📦 What This Release Is (and Is Not)
arifOS v38 is:
A governance kernel, not a model
Physics-based, not prompt-based
Auditable, not opaque
Human-sovereign, not self-authorizing
arifOS v38 is not:
A chatbot
A fine-tuning framework
A safety prompt library
A claim of solved AI alignment
🛣️ Roadmap Snapshot
v38 (now): Unified runtime + governed memory ✅
Q1 2026: Memory grid, orchestration, FastAPI deployment
Q2 2026: IDE / MCP integration + zkPC witness layer
Q3 2026: Multimodal governance (vision + audio)
📖 Recommended Reading
canon/000_ARIFOS_CANON_v35Omega.mdcanon/888_APEX_PRIME_CANON_v35Omega.mdcanon/ARIFOS_MEMORY_STACK_v38Omega.mddocs/DEEPSCAN_AUDIT_LOG.md
📜 License & Citation
License: AGPL-3.0
Commercial licensing available.
@software{arifos2025,
author = {Fazil, Muhammad Arif},
title = {arifOS: Constitutional Governance Kernel for AI Systems},
version = {38.0.0},
year = {2025},
url = {https://github.com/ariffazil/arifOS},
note = {Physics-based AI governance with verdict-driven memory}
}
🔥 Final Word
“Evil genius is not intelligence — it is ungoverned cleverness.”
arifOS v38 makes that distinction executable.
Ditempa, bukan diberi.
Forged — not assumed.