# CAS - COGNITIVE ARCHITECTURE SPEC
version: v1.1
status: ACTIVE
parent: master_architecture_index.md
phase: 02
phase_name: Architecture & Engineering Canon
document_role: cognitive_architecture_authority

## 1. OBJECTIVE
Define the canonical cognitive architecture of Devon.

This file owns:
- architecture placement of layers
- module responsibility at architecture level
- separation between probabilistic and deterministic components

This file does not own:
- detailed flow behavior
- latency budget
- security policy
- operational flow sequence

Those belong to:
- cfc.md
- lpc.md
- sec.md
- ofc.md

## 2. CORE PRINCIPLE
Devon is not an LLM-centric system.
Devon is a governed cognitive system where the LLM is one probabilistic component under deterministic control.

## 3. CANONICAL LAYERS

### 3.1 Interpreter Layer
- LLM
- extraction
- classification
- semantic parsing

### 3.2 Deterministic Control Layer
- FSM
- policy engine
- transition enforcement

### 3.3 Validation Layer
- validator
- contract checker
- policy enforcement

### 3.4 Execution Layer
- executor
- dispatch
- bounded side effects

### 3.5 Memory Layer
- working memory
- canonical memory
- audit-linked memory routing

### 3.6 Retrieval Layer
- embeddings
- retrieval
- recall support

Rule:
retrieval is a support layer.
retrieval is not sovereign decision authority.

## 4. SOVEREIGNTY BOUNDARY
Architecture ownership in this file means:
- where a capability belongs
- what responsibility it has
- what it must not absorb from another layer

This file may not redefine:
- exact state transitions
- hot path latency limits
- security controls
- end-to-end operational sequencing

## 5. LLM BOUNDARY
The LLM may:
- interpret
- extract
- structure
- propose

The LLM may not:
- own final policy
- override FSM
- bypass validator
- execute protected action directly

## 6. RETRIEVAL BOUNDARY
Retrieval belongs to architecture as a support capability.

Retrieval may:
- provide relevant context
- support reasoning inputs
- enrich decision inputs

Retrieval may not:
- define sovereign policy
- replace state control
- mutate canonical truth by itself

## 7. ARCHITECTURE OUTPUT CONTRACT
Any architecture derived from Devon must preserve:
- deterministic control above probabilistic interpretation
- validator before protected execution
- retrieval as support, never sovereignty
- explicit auditability