This hub gathers the analogies and metaphors the narrative reaches for to make AI-collective-memory legible, spanning several registers. A developer register anchors the new to the familiar: organizational narrative that [branches like code] (StyleObs_analogy_git), evoking version-control intuitions already held by the target audience. A physical/embodiment register evokes coherence: AI identity as a [resonant body with a shape] (StyleObs_Analogy_Resonant) and sailing [telltales as worldview-drift detectors] (StyleObs_4). An organizational/economic register reframes expectations: [Google runs search on ~10-15 people] (StyleObs_GoogleAnalogy) to calibrate ICP scale assumptions, and the [cross-functional sales↔eng cascade] (Observation_CrossFunctionalCascade) to dramatize bidirectional immediacy. A humanizing register frames the tool as a [coworker that frees devs] (StyleObs_ScarletPMBurden) from PM-communication overhead, with the self-aware in-joke of [duplicating the customer's chief architect's brain] (StyleObs_Analogy_DuplicateBrain) grounding knowledge-extraction value in enterprise humor. Across all registers: analogy used to anchor an abstract product concept to something already held.
Witness phrases
verbatim collective memory creates a living organizational worldview that evolves through intentional memory-saving and branches like code
verbatim AI identity as this sort of resonant body that has a shape to it
verbatim They serve as telltales. That's the right word. They serve as telltales
verbatim an organization like Google really only has like 10 or 15 people actually working on search
verbatim Communicating vision etc with developers is half the point of all-hands, product process, putting context in tickets, etc and we're able to free devs now to focus on working and ask their coworker (the AI) for context
verbatim the constant joke in the enterprise customer, literally—I'm not kidding—is 'if only we could get AI to duplicate the customer's chief architect's brain.'
verbatim As soon as a salesperson, you know, gains additional context about a client, the engineer immediately benefits in the actual hands-on coding and vice versa.
verbatim The telltales analogy is explicitly self-correcting mid-utterance — the speaker audibly searches for and then commits to the word — making it the one analogy marked as *found*, not pre-planned, which gives it a different rhetorical texture than the others.
verbatim The duplicate-brain in-joke operates as humor rather than argument, relying on enterprise-insider recognition; it may not travel to audiences outside that context, unlike the Google or git analogies which are broadly legible.
verbatim The coworker/liberation framing ('free devs') implicitly positions AI as replacing PM-to-dev communication load — a claim that could read as threatening to PMs rather than reassuring, depending on audience.
verbatim The resonant-body analogy operates in an embodiment/phenomenological register absent from all other analogies here, which are organizational or technical — it may serve a different persuasive function or audience.
In this area
StyleObservationObservation_CrossFunctionalCascade As soon as a salesperson, you know, gains additional context about a client, the engineer immediately benefits in the actual hands-on coding and vice versa. When they make an architectural decision or implement the feature that now becomes
StyleObservationStyleObs_4 They serve as telltales. That's the right word. They serve as telltales
StyleObservationStyleObs_Analogy_DuplicateBrain the constant joke in the enterprise customer, literally—I'm not kidding—is 'if only we could get AI to duplicate the customer's chief architect's brain.'
StyleObservationStyleObs_analogy_git collective memory creates a living organizational worldview that evolves through intentional memory-saving and branches like code
StyleObservationStyleObs_Analogy_Resonant AI identity as this sort of resonant body that has a shape to it
StyleObservationStyleObs_GoogleAnalogy an organization like Google really only has like 10 or 15 people actually working on search
StyleObservationStyleObs_ScarletPMBurden Communicating vision etc with developers is half the point of all-hands, product process, putting context in tickets, etc and we're able to free devs now to focus on working and ask their coworker (the AI) for context