Aligned Decision-Making
Aligned Decision-Making: Context Architecture for AI Agents in Organisations
- The eight-layer context hierarchy (regulatory → immediate task) has a defined authority ordering — Layer 1 (Regulatory) overrides all others; Layer 8 (Task) is subordinate to all others — validated by the independent convergence of Constitutional AI design, enterprise AI architecture literature, and the neuroscience of PFC hierarchical control
- Layers 2 and 3 (values/purpose and vision/mission) must always be resident in the core context window as an organisational constitutional document of approximately 300 tokens, because they are the highest-authority non-regulatory constraints and their relevance cannot be determined by query routing — they apply to every decision regardless of task type
- RAPTOR hierarchical tree indexing (ICLR 2024, arXiv:2401.18059) is the correct offline indexing technique for Layers 1 (regulatory) and 5 (policies/standards), because both layers consist of large, hierarchically structured document corpora where multi-level reasoning is required and offline preprocessing is feasible given low update frequency
- The Cynefin framework provides the meta-routing layer that maps decision complexity (Clear/Complicated/Complex/Chaotic) to retrieval depth across layers: Clear decisions require only Layers 7–8 and a cached policy summary; Complex decisions require deep retrieval from Layers 1–5; Chaotic decisions bypass retrieval entirely and use Layer 2 (values) as the anchor for immediate action
- The PFC's hierarchical organisation — rostral regions for abstract, temporally remote goals; caudal regions for immediate stimulus-response — provides a neurological validation for the context layer hierarchy: abstract constraints (Layers 1–4) must be actively maintained as the goal structure within which concrete task context (Layers 7–8) is interpreted
- Schema theory from cognitive science validates RAPTOR indexing as the computational analogue of schema formation: RAPTOR compresses a large document corpus into a tree of increasingly abstract summaries, mirroring the brain's organisation of experience into hierarchical schemas that guide inference and pattern-completion without requiring recall of raw experiences
- Working memory gating — the cortico-striatal mechanism that selectively admits task-relevant information into active processing — is the neurological analogue of modular RAG query routing; both perform selective filtering of a large information space based on task relevance, suppressing cross-domain noise that would degrade reasoning quality
- Constitutional AI (CAI, Anthropic, arXiv:2212.08073) provides the operational mechanism for encoding Layer 2 (values/purpose): a compact organisational constitution embedded in the agent's system prompt, against which the agent evaluates its outputs before delivering them — the architectural countermeasure for the sycophancy failure mode (token-level compliance at the expense of values alignment)
Research Question
What framework should an organisation adopt to ensure that AI agents making or supporting decisions have access to the right layered organisational context — spanning regulatory boundaries, values and purpose, vision and mission, strategy, policies and standards, current operating position, and immediate task intent — without relying on an impractically large context window?
What insights from cognitive science and state-of-the-art context-management techniques (Retrieval-Augmented Generation (RAG), compression, context architecture) inform the design and sequencing of that framework?
Findings
(Populated from §6 Synthesis above.)
Executive Summary
A layered organisational context architecture should partition organisational knowledge into eight distinct layers — regulatory, values/purpose, vision/mission, strategy, policies/standards, current operating position, intent/priorities, and immediate task — each requiring a different storage, retrieval, and compression strategy determined by its update frequency, volume, and authority weight. Layers 2–3 (values and vision) must always be resident in the core context window as a Constitutional AI (CAI)-style organisational constitution of approximately 300 tokens; they cannot be reliably retrieved on demand because their relevance is universal, not query-dependent. Layers 1 and 5 (regulatory and policies) are indexed offline using Recursive Abstractive Processing for Tree-Organized Retrieval (RAPTOR) hierarchical summarisation, retrieved via Modular Retrieval-Augmented Generation (RAG) with tier-specific routing, and compressed at query time using LLMLingua-2; the Cynefin framework provides the meta-routing layer that maps decision complexity to retrieval depth. Neurological research on prefrontal cortex (PFC) hierarchical organisation and schema theory confirms the architecture's structural validity, with the PFC hierarchy (rostral regions for abstract goals, caudal regions for immediate context) mirroring the Layer 1–4 versus Layer 7–8 split. Knowledge corpus governance — ownership assignment, freshness verification, and contradiction resolution at each layer — remains the primary unsolved prerequisite; no retrieval or compression technique compensates for an ungoverned source layer.
Key Findings
-
The eight-layer context hierarchy (regulatory → immediate task) has a defined authority ordering — Layer 1 (Regulatory) overrides all others; Layer 8 (Task) is subordinate to all others — validated by the independent convergence of Constitutional AI design, enterprise AI architecture literature, and the neuroscience of PFC hierarchical control.
-
Layers 2 and 3 (values/purpose and vision/mission) must always be resident in the core context window as an organisational constitutional document of approximately 300 tokens, because they are the highest-authority non-regulatory constraints and their relevance cannot be determined by query routing — they apply to every decision regardless of task type.
-
RAPTOR hierarchical tree indexing (ICLR 2024, arXiv:2401.18059) is the correct offline indexing technique for Layers 1 (regulatory) and 5 (policies/standards), because both layers consist of large, hierarchically structured document corpora where multi-level reasoning is required and offline preprocessing is feasible given low update frequency.
-
The Cynefin framework provides the meta-routing layer that maps decision complexity (Clear/Complicated/Complex/Chaotic) to retrieval depth across layers: Clear decisions require only Layers 7–8 and a cached policy summary; Complex decisions require deep retrieval from Layers 1–5; Chaotic decisions bypass retrieval entirely and use Layer 2 (values) as the anchor for immediate action.
-
The PFC's hierarchical organisation — rostral regions for abstract, temporally remote goals; caudal regions for immediate stimulus-response — provides a neurological validation for the context layer hierarchy: abstract constraints (Layers 1–4) must be actively maintained as the goal structure within which concrete task context (Layers 7–8) is interpreted.
-
Schema theory from cognitive science validates RAPTOR indexing as the computational analogue of schema formation: RAPTOR compresses a large document corpus into a tree of increasingly abstract summaries, mirroring the brain's organisation of experience into hierarchical schemas that guide inference and pattern-completion without requiring recall of raw experiences.
-
Working memory gating — the cortico-striatal mechanism that selectively admits task-relevant information into active processing — is the neurological analogue of modular RAG query routing; both perform selective filtering of a large information space based on task relevance, suppressing cross-domain noise that would degrade reasoning quality.
-
Constitutional AI (CAI, Anthropic, arXiv:2212.08073) provides the operational mechanism for encoding Layer 2 (values/purpose): a compact organisational constitution embedded in the agent's system prompt, against which the agent evaluates its outputs before delivering them — the architectural countermeasure for the sycophancy failure mode (token-level compliance at the expense of values alignment).
-
The current operating position (Layer 6) is best represented as a structured, pre-compressed Wardley Map or equivalent situational-awareness artefact encoding the evolution stage of key capabilities, current budget constraints, in-flight projects, and strategic priorities — rather than as raw operational documents — because structured representation is smaller, more reliably retrievable, and reduces the risk of stale data from high-frequency document churn.
-
Knowledge corpus governance — ownership assignment, freshness verification, and contradiction resolution for each layer — is the primary prerequisite for the architecture's effectiveness; this is the same failure mode that has caused every prior generation of enterprise retrieval technology to under-deliver, and no retrieval or compression technique compensates for ungoverned source layers.
-
Provenance tracking — tagging each context chunk with its source layer, document identity, version, and timestamp — is the mechanism that makes an AI-assisted decision auditable under EU AI Act Articles 9 and 13, transforming the layered context architecture into a compliance asset rather than merely a technical component.
-
Automatic Cynefin domain classification for enterprise decision queries is not yet a solved problem; the meta-routing step currently requires either human classification or a separately trained classifier, which represents a deployment gap that limits full automation of the context composition pipeline.
Assumptions
-
Assumption: Layers 2–3 (values, vision/mission) can be compressed into approximately 300 tokens without material loss of alignment fidelity. Justification: Vision/mission statements are typically 1–3 sentences in canonical form; values can be encoded as a 10–15 principle constitutional document following the CAI model. No direct validation of this threshold exists; the figure is an operational estimate.
-
Assumption: RAPTOR's performance on literary/general knowledge benchmarks (82.6% on QuALITY) transfers to structured regulatory/policy document corpora. Justification: Both involve hierarchically structured text with multi-level reasoning requirements. RAPTOR's recursive clustering operates on semantic similarity, not document type; policy documents have comparably rich semantic structure. Transfer is an [inference] — no direct benchmark on regulatory/policy text found.
-
Assumption: Cynefin domain classification applied to individual decision queries (rather than organisational domains) provides meaningful routing differentiation. Justification: The Cynefin framework was designed for decision-context classification; query-level application is an extension, but the causal logic (query type → context depth needed) is structurally sound.
-
Assumption: The architecture's effectiveness is primarily limited by knowledge corpus governance quality, not by the technical retrieval and compression components. Justification: Directly confirmed by the completed prerequisite item (KF10) and consistent with the historical pattern of enterprise retrieval technology.
Analysis
The architecture unifies three independent frameworks developed in isolation: the AI context management literature (RAG, compression, memory architectures), cognitive neuroscience (PFC hierarchy, schema theory, working memory gating), and enterprise knowledge management frameworks (TOGAF, Cynefin, Wardley Maps, Constitutional AI). The convergence is striking: each framework independently arrives at the same structural conclusion — that effective decision-making requires a hierarchical, layered representation of constraints, ranging from the most abstract and stable (regulatory, values) to the most concrete and dynamic (task, intent), with selective filtering mechanisms that activate only what is relevant to the immediate decision.
The primary design tension — completeness versus focus — is resolved not by technology but by governance. The organisation must invest in curating each layer independently, with defined ownership and update processes. Without this, the context architecture degrades to a well-indexed, poorly maintained knowledge base — better search over the same poor-quality sources.
The second tension — timeliness versus stability — is resolved by the offline/online compression partition. Stable layers (1–4) are pre-processed and indexed; dynamic layers (6–8) are composed fresh at query time. This requires clear freshness Service Level Agreements (SLAs) for each layer and automated invalidation of offline indexes when source documents change.
The third tension — general values versus specific task constraints — is resolved by the authority hierarchy plus the CAI self-evaluation step. Values (Layer 2) are not retrieved on demand; they are always present. The CAI mechanism ensures the agent evaluates each output against Layer 2 before delivering it, catching sycophancy and values-task conflicts that the precedence engine would not flag as explicit rule violations.
Competing interpretation considered: that Constitutional AI and Reinforcement Learning from Human Feedback (RLHF) alignment training can internalise all necessary organisational constraints at model level, eliminating the need for runtime context layers. This interpretation is not supported by evidence for enterprise-specific constraints. Alignment training can encode general harmlessness; it cannot encode a specific organisation's regulatory posture, risk tolerance, or strategic priorities without enterprise-specific training data and validation — which most deployments lack.
Risks, Gaps, and Uncertainties
- Cynefin classification is not automated. The meta-routing step currently requires human or separately trained classifier input. At scale, this is a bottleneck; a simpler proxy heuristic may be required as an interim measure.
- Values-encoding fidelity gap. Compressing an organisation's values and purpose into a 300-token CAI constitution loses nuance. High-stakes decisions in ethical grey areas will require human escalation; the architecture cannot resolve novel value conflicts autonomously.
- RAPTOR on policy/regulatory text is unvalidated. The benchmark results apply to literary corpora. A pilot evaluation on regulatory/policy documents is required before production deployment.
- Cross-layer contradiction detection at composition time is absent. The architecture detects conflicts at decision time (via the precedence engine) but not when context from multiple layers is assembled. A Layer 5 policy that contradicts the current operating position (Layer 6) would be injected without flagging.
- Organisational knowledge engineering function. The architecture requires a dedicated function responsible for curating each layer — assigning ownership, maintaining freshness, resolving contradictions. This function does not currently exist in most enterprise AI deployment teams.
- Temporal validity of indexed layers. Regulatory changes, strategy pivots, or major policy updates can invalidate offline indexes without immediate detection. An automated change-detection and index-invalidation pipeline is required but not currently part of any standard RAG toolchain.
Open Questions
- Can a lightweight Cynefin-domain classifier be trained on labelled enterprise decision queries to automate the meta-routing step? This is a candidate high-priority backlog item that directly blocks full automation of the context composition pipeline.
- What is the minimum constitutional document size for an organisational values layer that maintains meaningful alignment fidelity under CAI self-evaluation? (100 / 200 / 500 tokens — empirically determinable)
- Does RAPTOR applied to regulatory/policy corpora (Basel III, MiFID II, PRA SS10/18, ISO 27001) achieve comparable accuracy to its literary benchmark? A direct evaluation is required before relying on RAPTOR in regulated-industry deployments.
- What governance function design — roles, processes, tooling — is sufficient to maintain an eight-layer context architecture at enterprise scale? No published playbook currently exists.
- How should cross-layer contradiction detection be implemented at context-composition time rather than at decision time?
sources
- [ ] Findings from
2026-03-15-context-compression-rag-enterprise-knowledge(prerequisite — must be completed first) - [ ] Findings from
2026-03-15-neurological-context-management(prerequisite — must be completed first) - [ ] Anthropic — "Constitutional AI: Harmlessness from AI Feedback" (arXiv:2212.08073) — values/purpose instillation approach
- [ ] OpenAI — "Aligning Language Models to Follow Instructions" (InstructGPT paper, arXiv:2203.02155) — intent alignment
- [ ] TOGAF 10 standard overview (open sections) — enterprise architecture context layers
- [ ] Cynefin framework documentation (Cognitive Edge) — context and decision complexity
- [ ] Wardley Maps introduction (Simon Wardley) — strategic context and situational awareness
- [ ] "AgentBench: Evaluating Large Language Models (LLMs) as Agents" — empirical grounding for agent decision quality
- [ ] Recent ACL/NeurIPS/ICLR papers on context window management and long-context reasoning (search at retrieval time for latest, post-2024)