06-reference

secret cfo spare brain four buckets cfo operating system iv

2026-10-24·reference·source: CFO Secrets (The Secret CFO, anon)·by The Secret CFO (anon)
cfo-secretspersonal-operating-systeminformation-managementmemory-architecturecfo-operating-systemseries-part-iv

Why this is in the vault

Part IV of "The CFO Operating System" lays out a four-bucket model for where information should live — in your head, at your fingertips, on your radar, in the bin — and it maps almost one-to-one onto the memory architecture RDCO already runs (AGENTS.md / MEMORY.md / vault+qmd / cron-with-escalation), making this one of the series' strongest independent-convergence hits rather than just a frameworks piece.

Mapping against Ray Data Co

The sharpest hit: the author's four buckets are, functionally, a CFO's hand-built version of the exact layered-memory system RDCO runs for Ray. "In your head" (permanent judgment + ever-changing headline numbers, selected for high judgment/high relevance/immediate availability) is AGENTS.md hard rules plus the ever-refreshed working-context scratchpad. "At your fingertips" (high-precision detail too voluminous to memorize, retrieved reliably on demand) is the vault plus qmd semantic search — exactly the role described: "I couldn't recall much of that detail off the top of my head, but I knew where it was, and could get to it in minutes." "On your radar" (material but delegable to a trusted process that escalates on change) is the cron skill set — open-threads-check, check-board, community-watch — each a "someone/something else is watching, and I trust I'll hear about it when it matters" arrangement, which is precisely [[feedback_auto_mode_signal_to_noise]]'s existing default: channel messages reserved for decisions, surprises, blockers, everything else handled and reported by exception. "In the bin" (low materiality, no action required, deliberately not tracked) is the inbox-minimalism anecdote (500 emails/day, daily scan, otherwise ignored) — a direct precedent for RDCO's own "don't babysit" posture ([[feedback_no_babysitting]]) and for treating most inbound as noise unless it clears a bar.

The one genuinely new idea for RDCO's own thinking: the author explicitly distinguishes permanent in-head information (unit economics, foundational judgment) from ever-changing in-head information (this quarter's numbers, discarded the moment the quarter closes) — a split AGENTS.md doesn't currently make explicit between its hard rules (permanent) and the working-context narrative (ever-changing, meant to be discarded at compaction). That's a vocabulary worth borrowing, not a structural gap to fix unprompted. The four-bucket model is also a useful outside confirmation of [[2026-07-25-memory-container-vs-accumulated-content]]'s container-vs-content distinction: the buckets themselves (head/fingertips/radar/bin) are container design, commoditizable and copyable from any CFO playbook, while what actually sits in "your head" and "at your fingertips" — 18 months of RDCO-specific judgment and retrievable detail — is the accumulated content that resists it.

Also notable: the piece is explicit that the hard part isn't AI generating a system, it's a human knowing what to build ("AI can absolutely invent a system for you. The hard bit is knowing what to build") — consistent with the harness-engineering thesis RDCO already operates on, that scaffolding design is the scarce skill, not model capability.

The core argument

Reframes the CFO's mental-capacity problem (introduced in Part I's altitude framing) as an information-routing problem: everything a CFO tracks — numbers, people, projects, risks, decisions — needs to live in one of four places, and the skill is knowing which. In your head: things needed instantly and often, split into permanent (foundational judgment, e.g. unit economics), ever-changing (headline numbers, replaced each quarter), and situational (surfaces only during a live crisis or negotiation). At your fingertips: high-precision, high-volume detail you don't memorize but can retrieve in minutes — management accounts, forecast models, debt documents — the modern-day version of the CEO's lever-arch file from Part I. On your radar: material items delegated to a trusted owner, process, or KPI set that escalates on change, explicitly flagged as the bucket AI most transforms by effectively promoting radar items into fingertip-level accessibility. In the bin: low-materiality, low-consequence, no-action-required noise — illustrated by the author's 500-emails-a-day inbox-minimalism habit and a seven-year news-abstinence habit, both framed as a deliberate trade of occasional embarrassment for sustained headspace. Closes by tying the four buckets back to Part I's altitude-control metaphor and teases Part V: the author's own CFO-era operating system and how he'd rebuild it with AI today.

⚠️ Sponsorship

Sponsor: Campfire (AI-powered ERP / close automation) — same disclosed sponsor as Parts I, II, and III, confirming the series runs entirely on one standing sponsor rather than rotating through the broader CFO Secrets pool (Zip, Pulley, Stuut, Una, Ledge, Summation, Nominal, CloudZero, Aleph, Numeric, Airwallex). This is the author's long-flagged investor/user relationship (first noted 2026-05-11), not an arm's-length placement — the sponsor copy ("the answers are scattered across three systems in your head… which makes you the most expensive search bar in the company") is thematically on-brand for this issue's "spare brain" argument, which sharpens rather than dilutes the sales pitch. Appears as one mid-issue block plus the standing "Thank you to our sponsor" footer. No new third-party sponsor entrant this issue.

Related