---
type: concept
topic: agent-wiki
status: active
created: 2026-04-06
updated: 2026-04-06
source_notes:
  - "[[research/agent-wiki/sources/anthropic-building-effective-ai-agents]]"
  - "[[research/agent-wiki/sources/amp-how-to-build-an-agent]]"
derived_from:
  - workspace-initialize
confidence: high
shared_concept:
---

# Simplicity Before Autonomy

## Definition

Agent systems should begin with the smallest, clearest workflow that can solve the problem, and only escalate to more autonomous behavior when the simpler form is no longer adequate.

## Why It Matters Here

This principle is a design brake on the entire workspace. It argues that the knowledge compiler should stay inspectable, structured, and lightly tooled rather than racing toward a fully autonomous note ecosystem.

## Supporting Sources

- [[research/agent-wiki/sources/anthropic-building-effective-ai-agents]] argues directly for simple, composable patterns before agentic escalation.
- [[research/agent-wiki/sources/amp-how-to-build-an-agent]] shows that effective agents can emerge from a small loop plus tools rather than from elaborate architecture.

## Tensions

- Some worthwhile behaviors, like cross-workspace promotion and richer retrieval, may eventually require more sophistication.
- Overcommitting to simplicity can become under-engineering if the corpus outgrows the workflow.

## Implications

- Start with `index.md`, links, and plain file search before adding retrieval infrastructure.
- Keep source notes read-only and compiler-owned files strongly templated.
- Make promotion and merge deliberate operations rather than ambient background behavior.

## Related Concepts

- [[research/agent-wiki/concepts/compiled-knowledge-layer|Compiled Knowledge Layer]]
- [[research/agent-wiki/concepts/obsidian-as-agent-ide|Obsidian as Agent IDE]]

## Related Outputs

- [[research/agent-wiki/outputs/first-pass-thesis|First-Pass Thesis]]