# Architecture Decisions

## Separate Durable Memory From Transcript History

Durable preferences and project summaries live in curated markdown files.

Large session JSONL files are treated as archival evidence that can be summarized or archived, not as the primary continuity layer.

## Prefer Profiles Over One Global Setting

There is no single best cost/performance configuration for every task. This kit uses `economy`, `balanced`, and `deep` profiles so the user can pick the right tradeoff quickly.

## Keep Instruction Files Lean

Small, targeted `AGENTS.md` files improve efficiency more reliably than giant all-purpose prompt files.