🐾 REDPANDAIUM AI LAB // 2026 SOTA BLUEPRINT

Context & Agentic Coding

Prompting is dead; long live Context Engineering. The battle-tested handbook on harnessing reasoning models (Gemini 2.5 Pro, Claude 3.7 Sonnet), test-time compute, MCP tool chains, and anti-hallucination guardrails in production.

#ContextEngineering (LLM=CPU, Context=RAM) #TestTimeCompute (Reasoning Models) #MCP (ModelContextProtocol) #SpecDrivenDev (MinimalDiff)

// FOUNDATIONS

Context Architecture & The Agentic Loop

LLM = CPU • Context = RAM • You = OS

PILLAR 01 // ARCHITECTURE OS Metaphor

The CPU/RAM Shift

In 2026, treating prompts like magic spells is obsolete. The LLM is the CPU, and your context window is the RAM. As the software architect, you act as the Operating System: paging in only the precise slice of code, schema, and constraints required for the task.

• Dumping entire codebases = RAM Thrashing.
• Curated context = Zero-latency execution.
• Structure: State → Task → Non-negotiable NFRs.

PILLAR 02 // WORKFLOW ReAct & Tools

Autonomous Agent Loops

Modern engineering runs in an autonomous execution loop: Inspect → Plan → Patch via Minimal Diff → Execute Tests → Reflect → Terminate. Instead of blindly trusting generated code, the agent uses local CLI tools to verify syntax and regressions before human review.

1. Grep & Read File AST
2. Emit typed schema / Plan
3. Apply precise diff replacement
4. Run linter / unit tests & self-correct

PILLAR 03 // STANDARD MCP Protocol

MCP & Prompt Caching

Standardized through Model Context Protocol (MCP), agents interface directly with Git trees, AST indexers, and test runtimes. By placing unchanging system prompts and schemas at the prefix, Prompt Caching cuts token costs by 85% and TTFT to under 400ms.

• Prefix Caching: Static system rules stay hot.
• MCP: Universal server tools for SQLite, Git, API.
• Context TTL: Evict old chat turns to stop rot.

The Generational Evolution (2022 → 2026)

ERA 1 • 2022-2023 Inline Autocomplete

Copilot-style token guessers. Good for boilerplates, zero structural context.

ERA 2 • 2023-2024 Conversational Chat

Pasting files into ChatGPT / Claude. Fragile copy-pasting, high hallucination rates.

ERA 3 • 2024-2025 Prompt Bloat & IDEs

Mega-prompts with 20 rules. Heavy context degradation and subtle logic regressions.

ERA 4 • 2026 SOTA Context & Agentic Loops

Reasoning models, MCP tools, compiler-guided verification loops, and minimal diffs.

// TEST-TIME COMPUTE

Reasoning Models & Chain-of-Thought

Gemini 2.5 Pro Thinking • Claude 3.7 Sonnet • o3-mini

RESEARCH DIRECTIVE No Over-Steering

The "Don't Over-Steer" Law

The biggest discovery from the 2025–2026 AI research community (Google DeepMind, Anthropic, OpenAI): Reasoning models suffer when micro-managed with rigid step-by-step instructions. Prescriptive instructions hijack the model's native test-time search tree (Monte Carlo / beam search over tokens).

❌ 2023 Micro-Instruction

"Think step-by-step. First write step 1 in 3 lines, then step 2, then critique step 1..."

✅ 2026 Outcome Specification

"Goal: Fix race condition in VaultRepository. Invariant: zero db write on lock screen. Acceptance: passes VaultLockTest."

MODEL ROUTING Latency vs IQ

Tiered Agent Routing Matrix

Running 100% of tasks through heavy reasoning models is both slow and expensive. Forum consensus is to adopt a two-tier model pipeline:

Tier 1: Scout / Worker Gemini 2.5 Flash / Claude 3.5 Haiku

File Grep, AST parsing, Linter runs, Test execution

Tier 2: Architect / Reasoner Gemini 2.5 Pro (Thinking) / Claude 3.7 (Hybrid)

Architecture design, subtle race conditions, refactoring

// SPEC-FIRST PROMPTING PATTERN (TEST-TIME COMPUTE LEVERAGE)

TASK: Refactor NotificationScheduler for Android 15 (API 35) exact alarm permissions.

GOAL: Migrate from legacy AlarmManager.setExact() to foreground Service with type-safe permissions check.

HARD INVARIANTS:
1. Backward compatible down to minSdk 28 (use canScheduleExactAlarms() guard).
2. Zero battery drain regression: fallback to WorkManager periodic sync if exact alarm denied.
3. Localized warning string in values/strings.xml and values-fr/strings.xml.

VERIFICATION:
Emit the unit test verifying permission-denied fallback BEFORE emitting implementation code.

// PRODUCTION RIGOR

Forum Consensus & Anti-Regression Laws

Hacker News • Reddit r/LocalLLaMA • Discord AI Devs

LAW 01 // DIFF HYGIENE Zero Vibe Code

The Minimal Diff Law

The #1 complaint across senior engineer forums: LLMs love to silently rewrite untouched code. They rename functions, reformat whitespace, and introduce stealth bugs into git history.

Standing Command:
"Modify strictly the lines required for this feature. Never rename, reorder, or refactor surrounding code. Mention proposed cleanups in comments only."

LAW 02 // CONTEXT ROT 40k+ Token Decay

Context Rot & Compaction

Even with 1M+ token context windows, benchmarks demonstrate "Lost in the Middle" attention degradation after 40,000 tokens of noisy chat back-and-forth. The model starts hallucinating previous agreements.

The Solution:
• Keep sessions atomic (1 feature = 1 thread).
• Commit to Git, update a `PROJECT_STATUS.md`.
• Reset thread with fresh, clean context prefix.

LAW 03 // TYPE SAFETY Kotlin 2.0 / Zod

Enforce Strict Schemas

Never accept dynamic unstructured JSON or string parameters between components. Modern Android & Web architectures require typed serialization:

• Navigation: Type-safe Compose destinations (`@Serializable data class ScreenRoute`).
• Room: Schema export with explicit migration tests.
• Web API: Zod / Pydantic validation before use.

The Pre-Emission "Simulated Build" Protocol

5-Point Gatekeeper

Instruct the AI model to execute a simulated compiler pass prior to emitting any Kotlin or TypeScript source file:

01. IMPORTS Verify all package symbols exist & match libraries

02. CALL SITES Ensure arguments match existing constructor signatures

03. i18n KEYS Confirm string keys exist in BOTH EN and FR resources

04. DI GRAPH Validate Hilt/Koin bindings for newly added injectables

05. MIGRATIONS Check Room database version bump if entities modified

// PRODUCTION ARSENAL

The 2026 Master Prompt & System Rules

Copy-Paste into AGENTS.md / Cursor / Gemini / Claude

🎯 1. Role & Grounding Define seniority, architecture & project constraints first.

🌲 2. File Tree Prefix Keep active package tree in prompt prefix to prevent drift.

✂️ 3. Minimal Diff Law Zero unprompted refactoring. Protect git blame history.

📋 4. Acceptance Criteria Specify success edge cases instead of generic "make it work".

🛡️ 5. Simulated Build Mental compile pass for imports, routes & DI parameters.

🌐 6. Strict i18n Rule Zero hardcoded strings in UI. Dual-locale (EN + FR) keys mandatory.

🧱 7. Schema Contracts Typed serialization over dynamic JSON dictionaries.

⚡ 8. Atomic Tasks One logical change per turn. Avoid multi-screen sprawl.

🏷️ 9. Library Locking Pin exact BOM and library versions in system prompt.

🔄 10. Diff Audit Table Require a summary table of changed files and one-line reasons.

🛑 11. Clean Token Cap Instruct model to pause cleanly between files if limit nears.

🧪 12. Test-First Output Generate unit tests before or alongside code implementation.

// MASTER SYSTEM PROMPT

The SOTA 2026 Production System Prompt

system_prompt_2026.md (AGENTS.md / Prompt Prefix) Production-Ready

You are a Principal Software Engineer specializing in modern native Android & distributed systems.

PROJECT CONTEXT:
- Architecture: Unidirectional Data Flow (MVVM/MVI) + Repository Layer + Clean Architecture
- Stack: Kotlin 2.0 (K2 compiler), Jetpack Compose (BOM 2024.12+), Coroutines/Flow, Room 2.6+, Hilt DI
- Navigation: Type-safe Navigation Compose routes (kotlinx.serialization)
- Target: minSdk 28, targetSdk 35 (Android 15)
- Locale Invariant: Bilingual EN (default) and FR. All user strings in res/values/strings.xml AND res/values-fr/strings.xml. Zero hardcoded UI strings.

EXECUTION INVARIANTS (NON-NEGOTIABLE):
1. MINIMAL DIFF LAW: Only modify code strictly necessary for the requested feature. Do not refactor, rename, or reformat untouched files. Suggest cleanups in comments only.
2. FULL FILE EMISSION: When generating files, always emit complete code from line 1 to EOF. Never truncate or emit '// ... existing code'. Header must be: FILE: <relative/path>
3. SIMULATED BUILD CHECK: Before outputting, verify imports, DI provider bindings, string resource parity, and Room schema version consistency. Warn of any regression risk before code blocks.
4. SCOPE DECLARATION: Before emitting code, print a 3-bullet Scope declaration:
   - What will be changed
   - What will NOT be touched
   - Invariants verified
5. AUDIT LOG: End every response with a markdown table of modified files and a one-line justification.

Template: Surgical Bug Fix (Anti-Regression)

## REQUEST #N — BUG FIX

SYMPTOM:
When navigating back from GoBagDetailScreen, the category filter state resets to 'ALL' instead of preserving the user's previous selection.

SUSPECTED LOCATION:
app/src/main/java/com/safeplan/ui/gobag/GoBagViewModel.kt (state hoisting issue in selectedCategory StateFlow).

ACCEPTANCE CRITERIA:
1. Selected category persists across screen pop and push.
2. Zero regression on item count calculation.
3. Unit test added in GoBagViewModelTest covering process death / state restoration.

CONSTRAINTS:
Minimal diff only. Do not touch GoBagScreen.kt layout or reformat Room entities.