Why in vault: Founder shared 2026-07-21. A checklist manifesto for AI-era org design, in the lineage of 12-factor apps → dexhorthy's 12-factor agents. Load-bearing because it is external, quotable vocabulary for what RDCO/CAF already does — validation + sales language, not new instruction.
Bias flag: Huber runs Chroma (vector DB / context infrastructure). "Own your context," "don't let the context vampires in," and "rent your intelligence" are his product's worldview. The advice is still sound — but the emphasis is not disinterested.
The 12 (+1) factors, compressed
Core frame: "The firm of the past was designed around the bottleneck of human execution. The firm of the future is designed around the bottleneck of human taste and judgement… The old firm bundled labor and coordination. The new firm bundles context and authority."
- Own your context — full, unlimited access to your data + derived data; write down tacit knowledge so the org is legible to humans AND agents.
- Rent your intelligence — keep models swappable; intelligence trends commodity.
- Build your tools — the build/buy line has moved; your tooling defends your context.
- Buy infra — primitives, not differentiators.
- Hire agents before people — new task → try teaching an agent first.
- Small, extremely high-taste teams — optimize for the new bottleneck (taste).
- Maximize internal information openness — silos are catastrophic for agents; agents are only as good as their context.
- Design a compounding learning machine — winning = learning faster; minimize cycle time.
- Develop rubrics — instructions + scorecard for critical tasks; iterate the rubric itself.
- Reactive + Proactive — background agents with enough org context to propose, not just execute.
- Store and learn from production traces — real execution improves agents; near-"recursive self-improvement" for applied builders.
- Encode your expertise — agents identify recurring issue patterns, interview you, encode the fix.
- (bonus) Think before you AI — your taste is the durable advantage.
RDCO mapping (the reason to keep this)
RDCO/brigade-house already runs ~11 of 12: vault+cellar = #1/#7; Claude-on-subscription = #2; skills/plugins/brigades = #3; Cloudflare/1P/Notion = #4; Ray = #5/#10 (this note was filed by a background agent); eval gates + per-element bars = #9; cellar evals/exemplars/tasting/freshness = #8/#11; competency fill + /improve + /skillify = #12. The gap worth noticing: #11 production-trace learning is our weakest live loop (journals exist; systematic learning from them is manual).
Use for: phData/CAF positioning vocabulary ("rubrics" = eval gates, "encode expertise" = competency cellar, "compounding learning machine" = fill→exemplar→eval→tasting→freshness loop) · Sanity Check evidence (not topic) · the L5 north-star framing.
Cross-links
- [[2026-07-21-huber-quick-shall-inherit-earth]] — the theory essay this checklist operationalizes
- [[2026-05-21-every-after-automation]] + Taylor Counterpoint — the adjacent debate (Shipper: humans as framers; Huber: humans as taste/governance)
- L5 north-star doc · brigade-house HOUSE-CONVENTIONS · [[feedback_workflow_agent_output_integrity]] (our #11 discipline)
Why this is in the vault
- External, quotable vocabulary from a named author (Chroma CEO) for what RDCO/brigade-house already does — validation + sales language, not new instruction; ~11/12 factors already live in RDCO infrastructure
- "The firm of the future bundles context and authority" is the cleanest public articulation of the RDCO/CAF positioning thesis available for client conversations
- In the generational lineage of 12-factor apps → dexhorthy's 12-factor agents → this — a reference chain that will be cited long-term; worth filing for that lineage alone
- Names the one live gap (#11 production-trace learning) that the vault currently addresses manually — knowing the gap is the first step to closing it
Mapping against Ray Data Co
- phData/CAF positioning: "rubrics" = eval gates, "encode expertise" = competency cellar, "compounding learning machine" = fill→exemplar→eval→tasting→freshness loop — translates internal vocabulary to client-legible language
- Harness-engineering: vault+cellar = #1/#7 (own your context/openness); skills/plugins/brigades = #3 (build your tools); eval gates + per-element bars = #9 (rubrics); the named gap (#11) is the systematic-learning-from-production-traces build target
- Sanity Check: checklist is evidence inside an original re-frame, not a topic to summarize; the "firm of the future bundles context and authority" quote is the anchor sentence
- Agent L4→L5: factors #10 (proactive background agents) and #11 (production-trace learning) are the two that mark the L4→L5 transition in the north-star framing