PowerUp Coaching — Living Knowledge Base

Insight: Recursive Ambient Folders — The Folder Tree Is a Rule Inheritance Hierarchy

8 min read

“At the level of the accounting folder, I created all the CLAUDE rules I need. Then in 2026 I put the statements. When I do 2027, it can still look at the folder above it and inherit the rules of how to process those statements.” — Lou, 2026-05-21

Session context: 2026-05-21_Mastermind — Lou’s accounting-with-AI walkthrough surfaced a structural pattern that goes beyond the accounting case. Folders are not flat ambient agents; they are nested ambient agents whose rule sets are scoped to the subtree each one governs. The accounting example is the worked illustration; the recursive folder-as-rule-namespace architecture is the underlying principle.

Core Idea

Insight - Ambient Intelligence — Build a Skill in Every Folder to Make Your Entire Knowledge Base Alive established that every folder can be an agent — its own CLAUDE.md (or AGENTS.md) defines what the AI should do when it operates inside that folder. Recursive Ambient Folders is the structural extension: subfolders are themselves ambient folders, and the folder tree becomes a rule inheritance hierarchy.

The architecture has three properties:

  1. Each level holds rules scoped to its subtree. A CLAUDE.md at folder X/ contains rules that apply to X and everything beneath it. A CLAUDE.md at X/Y/ contains rules that apply only to Y and what’s beneath Y — and those rules sit on top of (do not duplicate) the rules from X/.
  2. Children inherit parent rules automatically. When the AI works inside X/Y/Z/, it sees the rules from X/, X/Y/, and X/Y/Z/ stacked together. No copy-paste. No drift. Sibling subfolders inherit the same parent context for free.
  3. The hierarchy is recursive. Any subfolder can itself become a parent. The depth of the tree is not capped by the architecture — it is capped by the natural specificity of the work. When you reach a level where the rules would only apply to one specific file, you have hit the bottom.

The mental model is folder hierarchy as namespace inheritance — the same scoping discipline that makes code packages composable, applied to ambient agents. The general principles that apply to a whole domain live at the domain’s root folder. Specifics that apply only to a sub-context live in that sub-context’s folder. The AI assembles the right rule-set on the fly based on where it is currently operating.

The non-obvious payoff is compounding context with zero duplication. If you write a new rule at the parent level, every existing child folder picks it up immediately on the next run. If you discover a year-specific irregularity, you write it to that year’s folder and it does not pollute the rules for other years. The architecture handles the scoping for you, so you never have to remember which rules apply where — the file path is the answer.

Why This Matters for Knowledge Entrepreneurs

The opposite of recursive ambient folders is single-bag-of-rules: one giant CLAUDE.md at the project root that tries to cover every possible context. That pattern breaks in two predictable ways. First, the file grows past the point where the AI can hold all of it usefully — you pollute every invocation with rules that do not apply to what you are currently doing. Second, when rules conflict (the year-2026 vendor categorisation that contradicts the year-2027 one, or the client-A intake style that contradicts client-B’s), the AI either guesses wrong or asks you to disambiguate every time.

The recursive ambient folder pattern solves both at once. Rules live at the level they apply to, so each invocation only sees the rules that are relevant here. Conflicts disappear because year-2026 rules live in accounting/2026/CLAUDE.md and year-2027 rules live in accounting/2027/CLAUDE.md — they never sit in the same context. The composability is structural; you do not have to engineer it with conditional logic in the prompt.

The compounding effect is what makes this an authority-grade architecture. Every refinement you make to a parent rule improves every future child invocation, forever. Every refinement to a child rule is sandboxed to that child’s subtree, so refining one client’s intake does not destabilise the rest. Your operational knowledge compounds at the right granularity — broad lessons broaden the foundation, narrow lessons stay narrow. Over years, the depth and specificity of the tree becomes a moat that no flat-CLAUDE.md user can replicate.

Practical Application

Adopt the recursive ambient folder pattern as the default organising principle for any domain you work in repeatedly. The accounting case is one worked example; the architecture applies anywhere there is recurring structured work.

The worked example — accounting:

accounting/
├── CLAUDE.md             ← chart of accounts, GL conventions, category-assignment heuristics,
│                            single-vs-double entry rule, vendor→category JSON DB, learning notes
├── 2026/
│   ├── CLAUDE.md         ← year-2026 vendors, irregular transactions, one-off categorisations
│   └── statements/
└── 2027/
    ├── CLAUDE.md         ← year-2027-specific rules; inherits everything from accounting/CLAUDE.md
    └── statements/

The parent accounting/CLAUDE.md holds the rules that are universal across all years — chart of accounts, ledger conventions, how to assign categories to companies, single-entry accrual vs double-entry. The year folders inherit everything from the parent and add only the rules that are specific to that year. Creating 2028/ next year is a one-line copy of the year template; the universal rules come for free.

The general procedure for any domain:

  1. Pick the domain root. Whatever recurring work you do (client engagements, content production, research projects, accounting), create a top-level folder for that domain.
  2. Identify the universal rules. What is true for every instance of work in this domain? Write those to domain/CLAUDE.md.
  3. Create per-instance subfolders. Each client, year, project, or unit of work gets its own subfolder.
  4. Add only the delta in each subfolder’s CLAUDE.md. Per-instance rules that the parent does not (and should not) know.
  5. Promote upward when patterns repeat. When a rule appears in three child folders, lift it to the parent. The hierarchy stays in equilibrium because you migrate rules up to the lowest common ancestor that still makes them universally true.

The write-back move that compounds the architecture — when the AI learns something during a run (a new vendor mapping, an irregular transaction pattern, a useful heuristic), it writes the learning back to the right scope level. Learning specific to this year goes to the year subfolder. Learning that applies across all years goes to the parent. The next run inherits the learning automatically wherever it should apply, and never sees it where it shouldn’t.

Coaching question: “Looking at one domain I work in repeatedly — what fraction of my AI instructions am I copy-pasting into every project’s CLAUDE.md, and would moving those rules to the parent folder remove that duplication entirely?”

Evolution Across Sessions

Builds on Insight - Ambient Intelligence — Build a Skill in Every Folder to Make Your Entire Knowledge Base Alive (2026-04-02), which established that every folder can host an agent. The new development is the recursive structure — that subfolders are themselves ambient folders, and the folder tree functions as a rule inheritance hierarchy. The original insight gave us the unit (folder-as-agent); this one gives us the architecture for composing many units (folder-tree-as-rule-namespace). Together they form the spatial structure for AI-augmented work at scale.

The insight was originally surfaced bottom-up (Lou’s accounting example) and flagged at 65 because the accounting framing was too domain-specific to carry the page. Promoted via /mastermind-triage 2026-05-21 after reframing top-down around the recursive architecture, with the accounting case as a worked example rather than the headline. Final score 78.

Source

  • 2026-05-21_Mastermind (Lou — initially via the accounting walkthrough; reframed into the recursive architecture during /mastermind-triage 2026-05-21)

Graph View

Backlinks