Carbonyx

CONCEPT LIBRARY

The vocabulary of Aerius cognitive runtime architecture.

The concept library explains the terms needed to understand Aerius without reducing its modules to ordinary AI product categories.

CATEGORIES

Concepts grouped by architecture role.

These categories help readers move from foundational architecture terms into observation, memory, reasoning, identity, domain runtime, reuse, expression, and governance.

FEATURED CONCEPTS

The shortest path to understanding why Aerius is not a chatbot, RAG system, agent loop, or model wrapper.

Featured concepts are selected shortcuts into the atlas and are repeated in their architecture categories below.

Model-as-Component

Foundational

The AI model is one component inside a broader architecture, not the entire system.

Why it exists

A model alone should not own memory governance, observation policy, identity binding, action safety, or trace production.

Why it matters

It keeps model selection separate from system governance, memory, evidence, and action design.

How it works in Aerius

Surrounding runtimes coordinate input, memory, observation, reasoning, domain logic, reuse, action, and traceability.

Common misunderstanding

Aerius is not a new model or chatbot.

Related modules

CCOStack BrainPbRCOMSCORDCRCPOR

Related portfolio items: Hybrid Cognitive Orchestrator Architecture, MRMI, COMS, COR, DCR

Cognitive Runtime

Runtime

An operational layer that governs a cognitive function such as observation, memory, reasoning, domain logic, action, or expression.

Why it exists

Cognitive responsibilities should not always be hidden inside model behavior.

Why it matters

It lets Aerius assign responsibility to explicit layers that can be tested, constrained, traced, and improved.

How it works in Aerius

Examples include COR, COMS behavior, DCR, CPOR, CEA, and Intent Action.

Common misunderstanding

A cognitive runtime is not just backend code; it is a governed system layer.

Related modules

CORCOMSDCRCPORCEAIntent Action

Related portfolio items: COR, COMS, DCR, CPOR, CEA, Intent Action

Dynamic Observation Envelope

Observation

A structured container for observation results, source metadata, evidence level, policy, risk signals, and trace information.

Why it exists

Observation should not enter the system as raw data without context.

Why it matters

It makes observation portable, reviewable, and usable by reasoning, memory, policy, and trace systems.

How it works in Aerius

COR may create or govern observation envelopes when evidence is collected.

Common misunderstanding

It is not just an image, file, or sensor reading.

Related modules

CORIISLCOMSCCO

Related portfolio items: COR, IISL, COMS

Deterministic Retrieval

Memory

Memory retrieval that can be controlled, reproduced, and tied to context, evidence, version, and retrieval policy.

Why it exists

High-accountability systems should not retrieve memory unpredictably.

Why it matters

Deterministic retrieval makes memory behavior auditable instead of a hidden similarity search side effect.

How it works in Aerius

COMS governs retrieval by task context, evidence, tiers, versioning, provenance, and as-of anchors.

Common misunderstanding

It is not the same as vector similarity search.

Related modules

COMSCCOPbR

Related portfolio items: COMS, Hybrid Cognitive Orchestrator Architecture

Priority-Based Reasoning

Reasoning

A mechanism for assigning cognitive priority, reasoning depth, urgency, risk handling, confidence handling, and resource allocation.

Why it exists

Not every task deserves the same reasoning budget.

Why it matters

PbR prevents reasoning effort from being spent uniformly when risk, urgency, uncertainty, or value differs by task.

How it works in Aerius

PbR evaluates urgency, importance, risk, confidence, utility, and resources to influence reasoning depth and routing.

Common misunderstanding

PbR is not a simple priority score.

Related modules

PbRCCOStack BrainCORCOMS

Related portfolio items: PbR, Hybrid Cognitive Orchestrator Architecture, Aerius Stack Brain

Relational Cognition

Identity

Reasoning that accounts for relationship-specific context such as trust, familiarity, role, safety, boundaries, and expectation gaps.

Why it exists

People are not static profiles; relationships create different expectations and risks.

Why it matters

Relational context changes what should be remembered, trusted, escalated, expressed, or blocked.

How it works in Aerius

RCC activates relevant relational dimensions when triggered by context, entity, role, risk, domain, or emotional cues.

Common misunderstanding

It is not a social graph or relationship label.

Related modules

RCCIMCCOMSCEAPbRIntent Action

Related portfolio items: RCC, IMC, CEA, Intent Action

Domain Capsule

Knowledge

An operational unit of domain-specific knowledge, reasoning protocols, rules, tools, verifiers, constraints, risk profiles, and authority boundaries.

Why it exists

Domain knowledge should be operationalized, validated, and governed before affecting reasoning.

Why it matters

A domain capsule turns expertise into runtime behavior rather than leaving it as passive documents.

How it works in Aerius

DCR loads, validates, binds, and governs domain capsules inside the reasoning runtime.

Common misunderstanding

A domain capsule is not a document folder or prompt pack.

Related modules

DCRKELCCOPbRStack Brain

Related portfolio items: DCR, KEL, MRMI

Conditional Reuse

Reuse

A previous cognitive processing outcome can be reused only when current task, context, evidence, time, risk, and policy conditions justify reuse.

Why it exists

Systems should avoid recomputation without reusing outdated or mismatched results.

Why it matters

Conditional reuse saves cognitive work while preserving accountability when conditions have changed.

How it works in Aerius

CPOR decides whether to reuse, verify, partially reuse, recompute, or block a prior outcome.

Common misunderstanding

Conditional reuse is not cache.

Related modules

CPORCOMSPbRCCOMRMI

Related portfolio items: CPOR, COMS, MRMI

Governed Output

Expression

An output, response, expression, or action that has passed through the relevant runtime context, policy, risk, evidence, and review constraints before being delivered.

Why it exists

AI output should not be treated as a direct model emission when safety, context, policy, and accountability matter.

Why it matters

It makes delivery a governed architecture event rather than the final token emitted by a model.

How it works in Aerius

CEA, Voice / Expression, Intent Action, Policy Gates, and Trace / Evidence can shape or block output before it reaches a user, system, or physical environment.

Common misunderstanding

Governed output is not just filtered text.

Related modules

CEAVoice / ExpressionIntent ActionPolicy GatesTrace / Evidence

Related portfolio items: CEA, Voice / Expression, Intent Action

Evidence Trace

Governance

A link between a system output, decision, observation, memory retrieval, reuse decision, or action and the evidence and process that supported it.

Why it exists

High-accountability AI systems need inspectability.

Why it matters

Evidence trace enables reconstruction of how a decision, observation, reuse, or action was reached.

How it works in Aerius

Evidence traces may be produced by COR, COMS, CPOR, DCR, Intent Action, and other modules.

Common misunderstanding

Evidence trace is not a chat transcript.

Related modules

CORCOMSCPORDCRIntent ActionCCO

Related portfolio items: COR, COMS, CPOR, DCR, Intent Action

Policy Gate

Governance

A checkpoint that determines whether a process should proceed, be limited, be escalated, be reviewed by a human, or be blocked.

Why it exists

High-accountability AI systems need explicit governance points.

Why it matters

Policy gates turn governance into runtime behavior instead of after-the-fact review language.

How it works in Aerius

Policy gates may apply to observation, memory retrieval, identity memory, domain capsules, reuse, expression, action, and review.

Common misunderstanding

Policy gates are not only content moderation.

Related modules

CORCOMSDCRCPORCEAIntent ActionCCO

Related portfolio items: COR, COMS, DCR, CPOR, CEA, Intent Action

Human Review

Governance

A governed escalation path where runtime behavior can be reviewed by a person when risk, uncertainty, authority, privacy, or policy requires human judgment.

Why it exists

Human review is not failure; it is an explicit governance pathway for decisions that should not be fully automated.

Why it matters

It preserves human judgment where automation should be constrained by authority, risk, privacy, or uncertainty.

How it works in Aerius

Aerius can route observation, reasoning, action, or output decisions to human review when policy gates, confidence, risk, or authority constraints require it.

Common misunderstanding

Human review is not just manual fallback.

Related modules

PbRCORIntent ActionDCRCEACCO

Related portfolio items: COR, Intent Action, DCR, CEA

FOUNDATIONAL

Foundational Concepts

Cognitive Architecture

Foundational

A system-level structure that coordinates memory, observation, reasoning, identity, knowledge, action, expression, traceability, and governance.

Why it exists

Model-only systems often hide these functions inside the model.

Why it matters

It gives reviewers a way to inspect responsibilities that would otherwise be collapsed into a single model response.

How it works in Aerius

Aerius coordinates dedicated modules around one or more AI models.

Common misunderstanding

It is not a vague marketing phrase; it refers to explicit system structure around models.

Related modules

CCOStack BrainCOMSCORDCRCEA

Related portfolio items: Hybrid Cognitive Orchestrator Architecture, Aerius Stack Brain

Model-as-Component

Foundational

The AI model is one component inside a broader architecture, not the entire system.

Why it exists

A model alone should not own memory governance, observation policy, identity binding, action safety, or trace production.

Why it matters

It keeps model selection separate from system governance, memory, evidence, and action design.

How it works in Aerius

Surrounding runtimes coordinate input, memory, observation, reasoning, domain logic, reuse, action, and traceability.

Common misunderstanding

Aerius is not a new model or chatbot.

Related modules

CCOStack BrainPbRCOMSCORDCRCPOR

Related portfolio items: Hybrid Cognitive Orchestrator Architecture, MRMI, COMS, COR, DCR

RUNTIME

Runtime Concepts

Inspectable Runtime

Runtime

A runtime layer that can expose what it did, why it did it, what evidence it used, and which policy applied.

Why it exists

High-accountability AI systems need process visibility for verification, governance, and review.

Why it matters

Inspectability turns system behavior into reviewable architecture rather than an opaque output stream.

How it works in Aerius

Modules can produce traces, evidence records, policy decisions, observation records, and action records.

Common misunderstanding

Inspectable runtime does not mean exposing hidden chain-of-thought.

Related modules

CORCOMSCPORDCRIntent ActionCCO

Related portfolio items: COR, COMS, CPOR, DCR, Intent Action

Cognitive Runtime

Runtime

An operational layer that governs a cognitive function such as observation, memory, reasoning, domain logic, action, or expression.

Why it exists

Cognitive responsibilities should not always be hidden inside model behavior.

Why it matters

It lets Aerius assign responsibility to explicit layers that can be tested, constrained, traced, and improved.

How it works in Aerius

Examples include COR, COMS behavior, DCR, CPOR, CEA, and Intent Action.

Common misunderstanding

A cognitive runtime is not just backend code; it is a governed system layer.

Related modules

CORCOMSDCRCPORCEAIntent Action

Related portfolio items: COR, COMS, DCR, CPOR, CEA, Intent Action

Runtime Binding

Runtime

Connecting a structured component, protocol, domain capsule, tool, verifier, or reasoning object into the active cognitive runtime.

Why it exists

Domain knowledge should not be pasted into prompts without validation.

Why it matters

Runtime binding determines when something becomes operational, under which constraints, and with what authority.

How it works in Aerius

DCR binds domain capsules after compatibility, policy, risk, authority, and validation checks.

Common misunderstanding

Runtime binding is not simply plugin installation.

Related modules

DCRCCOPbRCOMSStack Brain

Related portfolio items: DCR, MRMI, Hybrid Cognitive Orchestrator Architecture

OBSERVATION

Observation Concepts

Dynamic Observation Envelope

Observation

A structured container for observation results, source metadata, evidence level, policy, risk signals, and trace information.

Why it exists

Observation should not enter the system as raw data without context.

Why it matters

It makes observation portable, reviewable, and usable by reasoning, memory, policy, and trace systems.

How it works in Aerius

COR may create or govern observation envelopes when evidence is collected.

Common misunderstanding

It is not just an image, file, or sensor reading.

Related modules

CORIISLCOMSCCO

Related portfolio items: COR, IISL, COMS

Observation Policy

Observation

Rules for what should be observed, from which source, at what mode, duration, evidence level, and constraint set.

Why it exists

Systems should not observe everything at maximum detail by default.

Why it matters

Observation policy prevents perception from becoming uncontrolled collection or expensive over-observation.

How it works in Aerius

COR applies observation policies before, during, or after perception.

Common misunderstanding

Observation policy is not a camera setting only.

Related modules

CORPbRCCOIISL

Related portfolio items: COR, IISL, PbR

Evidence-Aware Observation

Observation

Observation guided by the evidence needed for reasoning, verification, risk handling, or decision support.

Why it exists

More data is not always better; the system should observe what is relevant and sufficient.

Why it matters

It links perception to the decision being made, so evidence gaps can be addressed deliberately.

How it works in Aerius

COR can escalate, reduce, repeat, or change observation depending on evidence gaps.

Common misunderstanding

It is not collecting everything and analyzing it later.

Related modules

CORPbRCOMSCCO

Related portfolio items: COR, COMS, PbR

MEMORY

Memory Concepts

Deterministic Retrieval

Memory

Memory retrieval that can be controlled, reproduced, and tied to context, evidence, version, and retrieval policy.

Why it exists

High-accountability systems should not retrieve memory unpredictably.

Why it matters

Deterministic retrieval makes memory behavior auditable instead of a hidden similarity search side effect.

How it works in Aerius

COMS governs retrieval by task context, evidence, tiers, versioning, provenance, and as-of anchors.

Common misunderstanding

It is not the same as vector similarity search.

Related modules

COMSCCOPbR

Related portfolio items: COMS, Hybrid Cognitive Orchestrator Architecture

As-Of Versioning

Memory

Retrieving memory or context as it existed at a particular time, snapshot, or decision anchor.

Why it exists

Reasoning sometimes needs to be reproducible under the knowledge state that existed when a decision was made.

Why it matters

It supports decision reconstruction when current knowledge differs from the knowledge available at execution time.

How it works in Aerius

COMS may provide as-of views that anchor memory, evidence, and context to a specific version or time.

Common misunderstanding

It is not merely file version history.

Related modules

COMSCPORMRMICCO

Related portfolio items: COMS, CPOR, MRMI

Evidence-Driven Promotion

Memory

Information moves to stronger or more durable memory tiers only when evidence, repetition, authority, trust, or usefulness supports it.

Why it exists

AI memory should not treat every raw statement as permanent truth.

Why it matters

It protects long-term memory from low-confidence claims while allowing validated knowledge to become more durable.

How it works in Aerius

COMS and KEL may promote or demote memory and knowledge based on evidence and validation.

Common misunderstanding

Promotion is not saving everything automatically.

Related modules

COMSKELIMCRCC

Related portfolio items: COMS, KEL, IMC

Memory Pyramid

Memory

A tiered memory model where layers differ by durability, authority, evidence strength, operational role, and retrieval behavior.

Why it exists

Not all memory should have the same weight.

Why it matters

The tiers help Aerius distinguish working context, evidence-backed memory, identity memory, and long-term knowledge.

How it works in Aerius

Memory Pyramid supports COMS by organizing memory into operational tiers.

Common misunderstanding

It is not a folder tree.

Related modules

COMSIMCKEL

Related portfolio items: COMS

REASONING

Reasoning Concepts

Priority-Based Reasoning

Reasoning

A mechanism for assigning cognitive priority, reasoning depth, urgency, risk handling, confidence handling, and resource allocation.

Why it exists

Not every task deserves the same reasoning budget.

Why it matters

PbR prevents reasoning effort from being spent uniformly when risk, urgency, uncertainty, or value differs by task.

How it works in Aerius

PbR evaluates urgency, importance, risk, confidence, utility, and resources to influence reasoning depth and routing.

Common misunderstanding

PbR is not a simple priority score.

Related modules

PbRCCOStack BrainCORCOMS

Related portfolio items: PbR, Hybrid Cognitive Orchestrator Architecture, Aerius Stack Brain

Stack-Based Reasoning

Reasoning

Structured reasoning stacks that separate, coordinate, compare, or synchronize reasoning processes.

Why it exists

Complex reasoning may require more than one internal process, hypothesis, or strategy.

Why it matters

It supports multiple reasoning stacks inside one cognitive window without turning the system into multi-agent chat.

How it works in Aerius

Stack Brain coordinates reasoning stacks under CCO, PbR, and MRMI influence.

Common misunderstanding

It is not multi-agent chat.

Related modules

Stack BrainCCOPbRMRMI

Related portfolio items: Aerius Stack Brain, PbR, MRMI

Meta-Reasoning

Reasoning

Reasoning about which reasoning strategy, process, or policy should be used.

Why it exists

AI systems should not use the same reasoning approach for every task.

Why it matters

Meta-reasoning lets Aerius adapt strategy without treating every failure as a need for base-model retraining.

How it works in Aerius

MRMI selects, evaluates, and improves reasoning strategies without base-model retraining.

Common misunderstanding

Meta-reasoning is not model fine-tuning.

Related modules

MRMIStack BrainPbRCCO

Related portfolio items: MRMI, Aerius Stack Brain, PbR

IDENTITY

Identity Concepts

Identity-Bound Memory

Identity

Memory associated with a specific person, entity, role, organization, or identity anchor.

Why it exists

AI systems need continuity without mixing one entity's memory with another's.

Why it matters

It keeps continuity useful while preventing memory from drifting across people, roles, organizations, or entity contexts.

How it works in Aerius

IMC binds memory, preferences, context, roles, and evidence to persons or entities.

Common misunderstanding

It is not a login profile.

Related modules

IMCCOMSRCCCEA

Related portfolio items: IMC, COMS, RCC

Relational Cognition

Identity

Reasoning that accounts for relationship-specific context such as trust, familiarity, role, safety, boundaries, and expectation gaps.

Why it exists

People are not static profiles; relationships create different expectations and risks.

Why it matters

Relational context changes what should be remembered, trusted, escalated, expressed, or blocked.

How it works in Aerius

RCC activates relevant relational dimensions when triggered by context, entity, role, risk, domain, or emotional cues.

Common misunderstanding

It is not a social graph or relationship label.

Related modules

RCCIMCCOMSCEAPbRIntent Action

Related portfolio items: RCC, IMC, CEA, Intent Action

Domain-Specific Trust

Identity

Trust evaluated by domain or context rather than as one global score.

Why it exists

A person may be reliable in one domain and risky in another.

Why it matters

It prevents trust from being flattened into a universal score when authority, expertise, safety, and role vary by domain.

How it works in Aerius

RCC can model trust vectors for safety, expertise, reliability, boundaries, or role context.

Common misunderstanding

It is not a single trust score.

Related modules

RCCIMCPbRIntent ActionCEA

Related portfolio items: RCC, IMC, Intent Action

KNOWLEDGE

Knowledge Concepts

Human-Driven Knowledge Evolution

Knowledge

Extracting, structuring, validating, promoting, demoting, quarantining, and governing knowledge derived from humans or interactions.

Why it exists

Human input should not become permanent system knowledge automatically.

Why it matters

It gives human knowledge a governed path from candidate signal to validated operational influence.

How it works in Aerius

KEL detects candidate knowledge, structures it, validates it, and governs its influence on reasoning.

Common misunderstanding

KEL is not a wiki or blog.

Related modules

KELCOMSMRMIDCR

Related portfolio items: KEL, COMS, MRMI, DCR

Domain Capsule

Knowledge

An operational unit of domain-specific knowledge, reasoning protocols, rules, tools, verifiers, constraints, risk profiles, and authority boundaries.

Why it exists

Domain knowledge should be operationalized, validated, and governed before affecting reasoning.

Why it matters

A domain capsule turns expertise into runtime behavior rather than leaving it as passive documents.

How it works in Aerius

DCR loads, validates, binds, and governs domain capsules inside the reasoning runtime.

Common misunderstanding

A domain capsule is not a document folder or prompt pack.

Related modules

DCRKELCCOPbRStack Brain

Related portfolio items: DCR, KEL, MRMI

Operational Domain Knowledge

Knowledge

Domain knowledge structured to guide reasoning, verification, tool use, constraints, and policy inside a runtime.

Why it exists

Plain text knowledge is not enough for high-accountability reasoning.

Why it matters

It allows domain knowledge to shape decisions through protocols, constraints, and validation instead of loose reference text.

How it works in Aerius

DCR and KEL can convert or bind domain knowledge into protocols, rules, constraints, and verifier bindings.

Common misunderstanding

It is not merely retrieved text.

Related modules

DCRKELMRMIStack Brain

Related portfolio items: DCR, KEL, MRMI

REUSE

Reuse Concepts

Conditional Reuse

Reuse

A previous cognitive processing outcome can be reused only when current task, context, evidence, time, risk, and policy conditions justify reuse.

Why it exists

Systems should avoid recomputation without reusing outdated or mismatched results.

Why it matters

Conditional reuse saves cognitive work while preserving accountability when conditions have changed.

How it works in Aerius

CPOR decides whether to reuse, verify, partially reuse, recompute, or block a prior outcome.

Common misunderstanding

Conditional reuse is not cache.

Related modules

CPORCOMSPbRCCOMRMI

Related portfolio items: CPOR, COMS, MRMI

Task Signature

Reuse

A structured representation of what a task is, what context it depends on, what evidence it uses, and what constraints apply.

Why it exists

Reuse, domain binding, strategy selection, and routing need more than raw prompt similarity.

Why it matters

Task signatures help Aerius compare work at the level of constraints, evidence, and context rather than wording alone.

How it works in Aerius

CPOR, DCR, MRMI, PbR, and CCO may use task signatures for routing and reuse decisions.

Common misunderstanding

A task signature is not just a prompt embedding.

Related modules

CPORDCRMRMIPbRCCO

Related portfolio items: CPOR, DCR, MRMI, PbR

EXPRESSION

Expression Concepts

Cognitive-Affective State

Expression

The system's structured representation of cognitive and emotional posture for communication and behavior.

Why it exists

System output should not be shaped only by surface tone or style.

Why it matters

It connects expression to uncertainty, ethics, continuity, and cognitive state rather than cosmetic personality settings.

How it works in Aerius

CEA manages cognitive-affective state, uncertainty, ethical shaping, expression intent, and continuity.

Common misunderstanding

It is not chatbot mood.

Related modules

CEAVoice / ExpressionIntent ActionCCO

Related portfolio items: CEA, Voice / Expression, Intent Action

Expression Intent

Expression

A structured representation of how the system should express an internal cognitive state or communication goal.

Why it exists

Expression across voice, gaze, facial output, gesture, and text should be coordinated with cognitive intent and policy.

Why it matters

It makes multimodal expression accountable to cognitive purpose instead of treating channels as independent outputs.

How it works in Aerius

CEA and Voice / Expression convert cognitive and affective state into expressive output instructions.

Common misunderstanding

Expression intent is not a visual animation preset.

Related modules

CEAVoice / ExpressionIntent Action

Related portfolio items: CEA, Voice / Expression

Cognitive Intent

Expression

A structured representation of what the system intends to communicate, do, ask, block, review, or execute.

Why it exists

Systems that can act need a governed representation between reasoning and action.

Why it matters

Cognitive intent creates a reviewable bridge between internal reasoning and external response or action.

How it works in Aerius

Intent Action converts cognitive intent into response, action, human review, or blocked action under safety and policy constraints.

Common misunderstanding

Cognitive intent is not merely user intent.

Related modules

Intent ActionCCOPbRCEADCR

Related portfolio items: Intent Action, CEA, DCR

Semantic Action Plan

Expression

An intended action described at a meaningful level before hardware-specific, API-specific, or execution-specific implementation.

Why it exists

The system should evaluate whether an action should occur before executing it.

Why it matters

It separates deciding what action means from executing a specific API, tool, device, or control pathway.

How it works in Aerius

Intent Action evaluates semantic action plans under context, safety, policy, role, authority, and review constraints.

Common misunderstanding

Semantic action planning is not low-level robot control.

Related modules

Intent ActionCCOPbRDCRCOR

Related portfolio items: Intent Action, DCR, COR

Governed Output

Expression

An output, response, expression, or action that has passed through the relevant runtime context, policy, risk, evidence, and review constraints before being delivered.

Why it exists

AI output should not be treated as a direct model emission when safety, context, policy, and accountability matter.

Why it matters

It makes delivery a governed architecture event rather than the final token emitted by a model.

How it works in Aerius

CEA, Voice / Expression, Intent Action, Policy Gates, and Trace / Evidence can shape or block output before it reaches a user, system, or physical environment.

Common misunderstanding

Governed output is not just filtered text.

Related modules

CEAVoice / ExpressionIntent ActionPolicy GatesTrace / Evidence

Related portfolio items: CEA, Voice / Expression, Intent Action

GOVERNANCE

Governance Concepts

Evidence Trace

Governance

A link between a system output, decision, observation, memory retrieval, reuse decision, or action and the evidence and process that supported it.

Why it exists

High-accountability AI systems need inspectability.

Why it matters

Evidence trace enables reconstruction of how a decision, observation, reuse, or action was reached.

How it works in Aerius

Evidence traces may be produced by COR, COMS, CPOR, DCR, Intent Action, and other modules.

Common misunderstanding

Evidence trace is not a chat transcript.

Related modules

CORCOMSCPORDCRIntent ActionCCO

Related portfolio items: COR, COMS, CPOR, DCR, Intent Action

Policy Gate

Governance

A checkpoint that determines whether a process should proceed, be limited, be escalated, be reviewed by a human, or be blocked.

Why it exists

High-accountability AI systems need explicit governance points.

Why it matters

Policy gates turn governance into runtime behavior instead of after-the-fact review language.

How it works in Aerius

Policy gates may apply to observation, memory retrieval, identity memory, domain capsules, reuse, expression, action, and review.

Common misunderstanding

Policy gates are not only content moderation.

Related modules

CORCOMSDCRCPORCEAIntent ActionCCO

Related portfolio items: COR, COMS, DCR, CPOR, CEA, Intent Action

Human Review

Governance

A governed escalation path where runtime behavior can be reviewed by a person when risk, uncertainty, authority, privacy, or policy requires human judgment.

Why it exists

Human review is not failure; it is an explicit governance pathway for decisions that should not be fully automated.

Why it matters

It preserves human judgment where automation should be constrained by authority, risk, privacy, or uncertainty.

How it works in Aerius

Aerius can route observation, reasoning, action, or output decisions to human review when policy gates, confidence, risk, or authority constraints require it.

Common misunderstanding

Human review is not just manual fallback.

Related modules

PbRCORIntent ActionDCRCEACCO

Related portfolio items: COR, Intent Action, DCR, CEA

Provenance

Governance

Where information came from, when it was obtained, how it was processed, and what source or authority it carries.

Why it exists

Reasoning without provenance can mix reliable and unreliable information.

Why it matters

Provenance helps Aerius distinguish source quality, authority, time, and processing path during review.

How it works in Aerius

IISL, COR, COMS, KEL, DCR, and CPOR may attach or use provenance metadata.

Common misunderstanding

Provenance is not only a citation.

Related modules

IISLCORCOMSKELDCRCPOR

Related portfolio items: IISL, COR, COMS, KEL, DCR, CPOR

RELATED ARCHITECTURE

Use concepts to navigate the architecture.