Five Scopes, Not Three

Anthemic synth-pop, 124 BPM, four-on-the-floor, big chant hook, bright arps; double-time rap break

V5.5

[Intro]
(bright arp swell, soft pad)
(whispered) Three scopes? Count again...
(count it: one, two, three... four, five)

[Verse 1]
You name a user file, a project file, maybe a folder too
A tidy little cascade, the closest one rules — that's what you knew
It borrows from CSS, from gitignore, the override frame
But Claude Code reads its memory a whole different way, not the same

[Pre-Chorus]
(build)
Two scopes hiding that you never said
And the override model? It's the trap instead

[Chorus]
(drop)
Five scopes, not three — count 'em all, let 'em be (let 'em be!)
Concatenated, every line, present at the same time
Five scopes, not three — nothing's silently dropped
Closer wins by recency, but the override's a lie (no override!)

[Verse 2]
Managed policy sits on top, deployed by IT, can't be cut away
User, then project, then local, gitignored — then subdirs come into play
They all get stitched into one window, every rule still in the light
A nearer file leans in by recency, but it never wins the fight outright

[Verse - Rap]
(double-time)
Broadest to most specific, lemme list the lineage clean:
managed policy, then user, then project, then local, then subdir scene —
that's five, not three, and here's the mechanism the exam will probe:
all discovered files concatenated into a single globe.
No formal override, nothing suppressed, nothing erased —
British versus American? Both sit in the same space,
project tends to lead 'cause it loads later, recency soft-tiebreaks the case,
but "never commit secrets" up in managed policy holds its place —
non-excludable authority, a project can't countermand.
Above the working dir? Loads at launch, the full stack manned;
subdirectory's lazy — on demand, only when Claude reads in that land.
Want a rule by file type, not directory? That's not the hierarchy's hand —
that's .claude/rules with glob patterns in the frontmatter planned.
And @path imports pull a file in, four hops max where they expand.

[Bridge]
(half-time)
Don't assume it's only project-level and the nearest file's the king —
that borrowed cascade is the distractor, it gets the whole thing wrong.
Five scopes, additive context, and managed policy can't be undone;
say "concatenated," not "overridden," and the marks are won.

[Final Chorus]
(full drop)
Five scopes, not three — count 'em all, let 'em be (count to five!)
Concatenated, every line, present at the same time
Five scopes, not three — nothing's silently dropped
Closer wins by recency, but the override's a lie (no override!)

[Outro — call to action]
(spoken over the final fade)
Want the deep version? Get *The CCA-F Study Guide* on Leanpub —
leanpub.com/cca-f
(...five, not three)

2921/7500

[Intro] (bright arp swell, soft pad) (whispered) Three scopes? Count again... (count it: one, two, three... four, five) [Verse 1] You name a user file, a project file, maybe a folder too A tidy little cascade, the closest one rules — that's what you knew It borrows from CSS, from gitignore, the override frame But Claude Code reads its memory a whole different way, not the same [Pre-Chorus] (build) Two scopes hiding that you never said And the override model? It's the trap instead [Chorus] (drop) Five scopes, not three — count 'em all, let 'em be (let 'em be!) Concatenated, every line, present at the same time Five scopes, not three — nothing's silently dropped Closer wins by recency, but the override's a lie (no override!) [Verse 2] Managed policy sits on top, deployed by IT, can't be cut away User, then project, then local, gitignored — then subdirs come into play They all get stitched into one window, every rule still in the light A nearer file leans in by recency, but it never wins the fight outright [Verse - Rap] (double-time) Broadest to most specific, lemme list the lineage clean: managed policy, then user, then project, then local, then subdir scene — that's five, not three, and here's the mechanism the exam will probe: all discovered files concatenated into a single globe. No formal override, nothing suppressed, nothing erased — British versus American? Both sit in the same space, project tends to lead 'cause it loads later, recency soft-tiebreaks the case, but "never commit secrets" up in managed policy holds its place — non-excludable authority, a project can't countermand. Above the working dir? Loads at launch, the full stack manned; subdirectory's lazy — on demand, only when Claude reads in that land. Want a rule by file type, not directory? That's not the hierarchy's hand — that's .claude/rules with glob patterns in the frontmatter planned. And @path imports pull a file in, four hops max where they expand. [Chorus] (drop) Five scopes, not three — count 'em all, let 'em be (let 'em be!) Concatenated, every line, present at the same time Five scopes, not three — nothing's silently dropped Closer wins by recency, but the override's a lie (no override!) [Bridge] (half-time) Don't assume it's only project-level and the nearest file's the king — that borrowed cascade is the distractor, it gets the whole thing wrong. Five scopes, additive context, and managed policy can't be undone; say "concatenated," not "overridden," and the marks are won. [Final Chorus] (full drop) Five scopes, not three — count 'em all, let 'em be (count to five!) Concatenated, every line, present at the same time Five scopes, not three — nothing's silently dropped Closer wins by recency, but the override's a lie (no override!) [Outro — call to action] (spoken over the final fade) Want the deep version? Get *The CCA-F Study Guide* on Leanpub — leanpub.com/cca-f (...five, not three)

0/500