06-reference

commoncog making of hindsight

2026-11-03·reference·source: Commoncog·by Jared Peterson (Shadowbox); Cedric Chin (Commoncog)
tacit-knowledgeexpertise-acquisitiontactical-decision-gamessensemakingsponsored-content

No public post URL exists for this piece — it is explicitly framed in-email as the third of five emails written for the paid TDG Design Workshop ("these emails are ostensibly about TDGs but are more broadly about accelerated expertise... written specifically for this workshop"), not a Commoncog essay with its own permalink. Third email in the active Commoncog x Shadowbox sequence, following [[2026-08-25-commoncog-why-tactical-decision-games-work]] (the original, unsponsored essay) and [[2026-11-01-commoncog-making-of-common-sense-tdg]] (first Shadowbox-sponsored installment); same sequence as [[2026-11-02-commoncog-tdgs-accelerated-osmosis-expertise]] (second installment). Two more emails remain: Nov 7 and a Nov 8 finale with a "surprise guest."

Why this is in the vault

A genuinely new concept in the same tracked thread: a "map" — the artifact that encodes the cues, patterns, and framing an expert reads to make sense of a domain — is the missing piece between "expertise is pattern-matching" (already in the vault) and "how do you actually go train/evaluate it," which bears directly on how RDCO's own rubric-as-critic-contract pattern works.

The core argument

Jared Peterson (Shadowbox, works under TDG inventor John Schmitt) opens with Schmitt's standing question when entering a new domain: "What is the map here?" — not geography or an org chart, but whatever a decision-maker observes that lets them make sense of expertise in that domain. The argument builds in three steps. First, decisions are mostly not "choice between options": Gary Klein's firefighter interviews (see [[2026-04-19-commoncog-map-of-expertise-research]]) found the dominant academic model of decision-making (generate options, score them, pick the best) doesn't match how experts actually operate — they recognize a situation as similar to past ones (Recognition-Primed Decision-making) and act without deliberation. The training implication: "if you want to train decision-making, don't train decision-making, provide a greater experience base." Second, for novel situations, experts rely on the Data-Frame Theory of Sensemaking — "problem framing and problem solving are the same cognitive process," illustrated by Jared's own behavioral-science consulting work, where clients called the final solutions "common sense" even though the real value delivered was the framing that made the solution obvious (the "hindsight" of the title — sometimes a bias, sometimes just evidence the problem space is now actually understood). Third, a "map" is whatever artifact contains the cues a decision-maker must recognize and interpret — literal maps in physical-danger domains, and (Jared's speculation) financial statements, metrics, or reports in business. His close: identify the map for your domain, and only then can you design training (i.e., a TDG) for it.

Mapping against Ray Data Co

The concrete new connection: RDCO's own rubric files — vault-note-schema.md (the file this very note is being written against), the design-critic's "5 concrete tells," verify-strategic-output's calibration rubric, station-critic's per-domain axis config — are literally "maps" in Jared's sense. They're the explicit, written-down version of the cues an experienced editor/critic pattern-matches on (frontmatter completeness, sponsor disclosure, mapping strength, calibration-vs-evidence) so that a fresh-eyes subagent with none of the founder's accumulated judgment can still evaluate correctly. Jared's closing claim — "once you identify the map, then you can train expertise" — is exactly the sequencing RDCO already follows: write the rubric (the map) before dispatching the critic (the trainee), rather than hoping a general-purpose agent absorbs taste by osmosis. This is new relative to the prior two installments: those mapped the TDG training loop (critic/brigade architecture) and the premise that judgment is the AI-era bottleneck; this one maps the prerequisite artifact — you need the map written down before either of those works. Secondary, weaker thread: Jared's business-map guess ("financial statements... metrics... reports") is the same raw material project_investing_markov_capital_cycle treats as the map a capital-cycle investor reads (capex, inventory, returns on capital) that a novice can't — worth noting but not the load-bearing point here. RDCO is dormant with phData as the main bet (project_rdco_dormant_phdata_main); no action item, this sharpens the "why rubrics-before-critics" design choice rather than changing it.

⚠️ Sponsorship

sponsored: true / sponsor_entity: Shadowbox. Explicit continuation of the disclosed sequence: this email states outright it is "the third of five" written "specifically for this workshop," with sales closing November 10th and seat-scarcity framing (9 of 20 left) repeated twice, plus two direct purchase links. Co-authored by Jared Peterson, a Shadowbox employee; Cedric discloses he is himself a paying workshop participant. The sensemaking/RPD content (Klein's firefighter research, Data-Frame Theory) is credible and well-sourced on its own terms, but its selection, timing, and the "once you identify the map, you can train expertise" closing line exist to motivate the $2,000/seat TDG workshop sale — same pattern as the two predecessor notes, now in its third installment. Per the founder's standing instruction, treat each remaining email in this sequence (Nov 7, Nov 8) as sponsored-by-default until it ends.

Related