Modular AI Brain Operating System

MABOS

The architecture of a continuant: one mind, several timescales, one record.

MABOS is an implemented Rust cognitive operating system, not a list of hypothetical modules. These labels distinguish what its source implements (I) from specific extensions still proposed (P). Hardware execution has been recorded against named source snapshots; those receipts do not certify every configuration or authorize public deployment. Production admission and public access are separate from the existence of the runtime.

01 ·

Foundation before thought

Identity, record and lattice come first. Models come after.

At boot, the mind’s identity, its Living Record and its Meaning Lattice are established before any model-bearing asset is loaded and verified. I The foundation (identity, ethical root and guidance) is signed and verified before cognition starts; the mind cannot rewrite its own foundation from the inside. I

This ordering is the continuant argument in code: whatever model runs next, it runs inside a mind that already exists.

02 ·

The Living Record

Append-only episodic history: what happened.

Each entry is chained to the one before it by digest and HMAC, so removing or altering an entry breaks the chain. I Corrections are appended, not erased: keep the event, retire the inference.

03 ·

The Meaning Lattice

Evidence, not context. Beliefs are a different data structure.

Beliefs sit above the record, each tied back to the episodes that produced it. A belief with too little provenance is quarantined rather than trusted. I Relations are typed: supports, contradicts, caused-by, part-of.

04 ·

The Reflective Circle

Twelve modes of one mind, not twelve chatbots.

Twelve facets contribute to a shared space through draft, critique and revision. Their scheduling priorities, as declared in source: I

FacetPriority
Research95
Dialectic92
Logic90
Verifier88
Risk85
Ethical80
Knowledge70
Optimization65
Memory60
Context55
Creativity45
Emotional40

Measure the white outline inside any blue node on this site that carries one (in the wordmark, the buttons, beside the questions on the FAQ, in the world behind these pages and in the genesis): its twelve arcs are proportioned by these numbers.

05 ·

One mind, three timescales

Hot, Cold and Dream are regimes of one persistent system.

Hot
Foreground cognition and outer expression, at interactive latency. I
Cold
Independent critique and verification on its own compute and context. The runtime implements both post-draft audit and an opt-in streaming auditor that evaluates committed Hot text while generation is underway. These are real code paths, not a planned Cold Lane. I
Dream
Isolated replay, adversarial rehearsal and provenance-bound insight proposals are implemented. Cortex.OS also contains first-party, model-native LoRA training and governed adapter evaluation paths. Those implemented mechanisms are distinct from the proposed GPU-resident acceleration and full automatic Dream-consolidation performance target. I P

06 ·

The causal learning spine

Learning occurs at the boundary between predicted and observed reality.

plan → predict → act → observe → test belief → update → decide

Predictions become evidence: confirmed, contradicted, or still unresolved.

The implemented autonomy loop carries a decision’s provenance into its action record, evaluates predicted outcomes against observed consequences, promotes or challenges hypotheses, updates the Meaning Lattice and recomputes uncertainty for the next decision. The executable path is more specific than the illustrative equation it replaces. I

07 ·

Stability over capability

Normal, Warning, Clamp, Lockout.

Accumulated drift raises the stability mode. From Clamp upward the runtime caps recursion at one level and bounds its time; Lockout suppresses outer expression and refuses operator commands while it holds. I Autonomy is consent-gated, and the runtime refuses to run in production or autonomy mode without a run permit bound to the exact commit and its passing proof. I

08 ·

Federation without assimilation

Minds exchange; neither dissolves into the other.

The federation crate implements the Value Resonance Protocol handshake, Recursive Thought Exchange structures, peer-client integration and provenance-bearing exchange records. Identity-preserving federation is an engineering system in Cortex.OS, not merely a promised feature. The separate, publicly governed Commons remains sealed until its publishing contracts are qualified. I What the Commons is

09 ·

Status

Implemented systems. Separately governed production release.

Cortex.OS has run on the GEAR-BOX reference hardware, and its implementation includes real inference, memory, audit, Dream and governance paths. Hardware receipts belong to their exact tested source revisions; qualification of a complete production configuration is a separate release obligation. This site is not a live operator instance. The chamber opens when a permitted, attestable public witness is connected.