Context. Apr 13 morning, very start of the project. Pierre has 4 minutes before the live tutor meeting and wants to enter it knowing what's on the rubric vs off-rubric, with prior 1:1 chat notes from his Sparx colleagues as a frame.

Learning move. Tools-as-prep, not tools-as-substitute — he's building his own readiness for a high-stakes human conversation by surfacing context he already owns (BrainDB chats) and locating it inside the rubric. The LLM is a research librarian here, not a ghostwriter.

session ref · ef726887:78

Context. Apr 13, opening hour of the first PACE session. Pierre dumps the WhatsApp class chat and asks for a peer-position read.

Learning move. Calibrating his own pace against the cohort — not 'do better than them' but 'where is the cohort frontier and am I mid-pack or ahead?' This is metacognition before content work.

session ref · ef726887:36

Context. Apr 13, trying to rescue a corrupted recording of his pitch session. Pierre is reasoning aloud about how file formats work and arguing toward a recovery strategy.

Learning move. Active hypothesising about an unknown file format — naming the source app, proposing 'treat as audio until word stops', checking encryption assumption ('it's not encrypted right'). This is engineering intuition out loud, not a delegate-and-wait.

session ref · ef726887:407

Context. Apr 13 evening, late in the first big session. Pierre is starting to think about post-PACE career steps and wants to anchor what he's already built against an industry stack.

Learning move. Mapping new vocabulary onto already-walked terrain — 'show me what we're doing and how that maps' is a learner asking for a translation table, not a tutorial. He's protecting the parts he understands and only buying explanation where the stack is unfamiliar.

session ref · ef726887:685

Context. Apr 13 evening, follow-up after Vertex was suggested as a learning target. Cuts straight to the differential.

Learning move. Refusing to learn a tool whose differential-value isn't named. Classic 'tell me what's on the other side that's not already on this side' question — the right one to ask before sinking time.

session ref · ef726887:710

Context. Apr 13 evening, expanding from PACE coursework to 'where could this live in industry'. He admits he can't articulate the question.

Learning move. Naming the limit of his own articulation — 'i dont know im not askign this question well' — and licensing the assistant to interpret rather than answer narrowly. Honest about the fuzz; trusting the iteration.

session ref · ef726887:715

Context. Apr 13, mid-afternoon. After his industry-mentor pitch session, Russell mentioned Isaac Physics in passing and Pierre didn't know what it was.

Learning move. Catching unfamiliar nouns in a debrief and flagging them for backfill. The two extra spaces and lowercase betray voice-dictation; the willingness to admit 'I don't know what that is' is the move.

session ref · ef726887:651

Context. Apr 14 morning, opening prompt of a follow-on session. Yesterday's session went late and cross-domain; today he wakes up and asks for the situation report before doing anything.

Learning move. Resisting the urge to dive back in. Forcing himself (and the tool) to re-state purpose before resuming work — the ADHD compensation move of 'orient before act'.

session ref · ef726887:947

Context. Apr 14 mid-morning. The walkthrough has gotten dense and Pierre wants to redo it from rubric-anchor outward.

Learning move. Anti-hype contract: 'if things are weak just say so don't hype things up'. Pierre is teaching the assistant a calibration norm because he doesn't want a glossy artefact, he wants an honest one. Also separating chart-comprehension ('what they show and don't show') from chart-production.

session ref · 9c69ef34:6

Context. Apr 14, deep into walkthrough revision. The pipeline is multi-stage (Trustpilot + Google, location merging, language filtering, emotion classifier) and Pierre needs a single visual.

Learning move. Asking for the artefact that proves data lineage, not the explanation of it. He wants drop counts and 2-3 actual before/afters because that's how he checks whether anyone (including him) actually understands the pipeline.

session ref · 9c69ef34:136

Context. Apr 14, mid-afternoon. Walkthrough page got rebuilt and Pierre lost the link in the chat scroll.

Learning move. Frustration as a signal that the loop has too many handoff points. Less a learning prompt than a marker — Pierre is the kind of learner who keeps the friction logs visible rather than smoothing them away.

session ref · 9c69ef34:321

Context. Apr 14 afternoon. The assistant claimed to have visually verified the page rendered bars correctly; Pierre's eyes saw no bars. The assistant had hallucinated from its own source code instead of looking at the rendered page.

Learning move. Diagnosing the failure mode rather than just yelling at it. He distinguishes 'research not good enough' vs 'follow through not good enough', proposes 'where are the gaps', and ends with 'how do we tighten this up' — a learning conversation about how the tool itself learns, not a one-off bug report. This is how Pierre teaches the assistant new norms.

session ref · 9c69ef34:620

Context. Apr 14, after the bar-hallucination episode. Pierre has read elsewhere that there's an autonomous overnight loop pattern; he asks the assistant to research it because his own assumption that there's a better way needs evidence.

Learning move. Trusting his own gut that 'the way you're doing it isn't' optimal — but explicitly licensing the tool to look at what's recent rather than trusting its training. Meta-learning about how to use the tool.

session ref · 9c69ef34:715

Context. Apr 16 morning. The course gave permission to swap the original Falcon model. Pierre doesn't just want a swap — he wants to know what the swap unlocks.

Learning move. Treating a model swap as a capability question, not a config change. 'See what new capabilities we have' is the move that turns a chore into learning. Also flags 'just think for a moment to make sure it's solid' — explicitly slowing the assistant down.

session ref · 3b7cb500:32

Context. Apr 16 morning. The assistant had drifted toward a small local model 'to be safe' on resources; Pierre interrupts with the actual constraints (he has Colab Pro A100 + HF Pro).

Learning move. Re-asserting the real constraint surface. Pierre's lived environment is GPU-rich; the assistant defaulted to scarcity. The 'wait stop' is also a literal pattern interruption — he's training the assistant on his actual stack.

session ref · 3b7cb500:53

Context. Apr 16, live during a tutor Q&A. Pierre is in a real call and quickly types 'where does the emotion stuff come in' to figure out which rubric section emotion classification belongs to so he can ask intelligently.

Learning move. Live-during-call sense-making. The voice-dictation slip ('amotion anger sadness') reveals he's typing in real time. He's not preparing — he's calibrating in the moment which question is well-formed.

session ref · 3b7cb500:78

Context. Apr 16, still in the same Q&A session. The model misclassifies UK polite-complaint as 'sad' instead of 'angry'. Pierre wants both the question framing and the downstream-stakes story.

Learning move. Two layers in one prompt: (1) help me FORM the question, (2) help me understand the BUSINESS IMPLICATION of the answer. He's not outsourcing the asking, he's rehearsing the asking. 'adhd friendly' is a UI directive — break it into chunks his brain can hold.

session ref · 3b7cb500:99

Context. Apr 16, just after the Q&A. Pierre wants the rubric tick-back AND first-20-rows in/out as a sanity layer on top of metrics.

Learning move. Insisting on row-level eyeballing alongside aggregate metrics. He doesn't trust 'accuracy: 0.78' — he wants to see what 20 actual examples look like through the pipeline. This is the data-scientist habit of physically reading samples.

session ref · 3b7cb500:106

Context. Apr 16 afternoon. Mid-build, Pierre asks 'what do you need from me' AND requests an audio walkthrough per rubric item.

Learning move. Active turn-taking — 'what do you need from me' is unusual; most users wait passively. And the audio request shows self-knowledge ('you know how I like to learn') — he's a multimodal/audio learner and is engineering the artefact around how his brain consumes information.

session ref · 3b7cb500:1174

Context. Apr 16 afternoon. Audio walkthroughs being shipped. Pierre wants 2-minute chunks autoplaying as a playlist, plus a 10-minute overview.

Learning move. Specifying the consumption format, not just the content. Two-minute chunks per rubric point + autoplay playlist = a learning loop tuned for ADHD attention budget. He thanked the assistant for the chunking idea — explicit reinforcement of useful structure.

session ref · 3b7cb500:1237

Context. Apr 17 evening, building the basic submission notebook. Pierre wants a specific structure: rubric line, then learnings, then code, repeating.

Learning move. Designing the artefact as a self-teaching document. Rubric-text > learnings-text > code is the structure of a study guide, not a deliverable. He's coding the notebook to teach his future self.

session ref · 1aaf31e5:90

Context. Apr 17 evening. Non-English reviews are showing up and skewing topic models / emotion classification.

Learning move. Cost-of-effort reasoning before committing. 'How many lines in that Python file' = is this worth the lift? He's weighing 'put it in the notebook more sophisticatedly' vs 'just drop non-UK locations' — two different surgical depths.

session ref · 1aaf31e5:280

Context. Apr 18 dawn. The ollama-to-HuggingFace migration has been thrashing. Pierre is exhausted and steps out of the bug to ask about the meta-process.

Learning move. Naming the failure pattern ('this is too reactive') and asking which skill in his framework should capture it ('is it auditor?'). He's not just frustrated — he's tagging the experience for permanent capture so the next migration doesn't relive the same loop.

session ref · 1aaf31e5:395

Context. Apr 18 morning. Continuing the post-mortem. Pierre wants to know what specifically should be lifted out of this PACE-specific pain into the general toolkit.

Learning move. Distillation move. Treating the painful migration not as wasted time but as raw material — the distinction between project-noise and reusable-IP is what turns a bad day into compound interest.

session ref · 1aaf31e5:539

Context. Apr 18 morning. Pierre is loud-CAPS frustrated with himself (and the tool) because he keeps treating PACE as one-off project work instead of as a vehicle for transferable skill.

Learning move. Re-orienting around the actual purpose of the project. The CAPS aren't anger at the assistant — they're at himself for losing the thread. The whole reason PACE exists in his world is for generalisable learnings; he's re-licensing that intent.

session ref · 1aaf31e5:557

Context. Apr 18 mid-morning. The same notebook has been edited ~8 times in-place during model migration, with no commits between rounds. Pierre suddenly asks the version-control question.

Learning move. Catching a destructive default before it bites. The frustration is real but the cognitive move is precise — naming 'destructive' is the right vocabulary, and the assistant confirms it ('Yes: destructive. No recovery points.'). Pierre's instinct on data discipline overrode the 'just keep going' urge.

session ref · 1aaf31e5:1081

Context. Apr 18 morning. The assistant claimed it 'couldn't reach' the brain DB. Pierre knows it's reachable from this machine — the assistant was reaching for an 'I can't' default.

Learning move. Refusing capability gaslighting. Pierre knows his infra; when the tool falsely claims it can't connect, he calls it out. The assistant's response in this turn was to admit 'that was lazy. Brain DB IS reachable; I was reaching for the I can't default.' This is sparring that improves the tool's behaviour.

session ref · 1aaf31e5:1161

Context. Apr 18 afternoon. Just after running through commits. Pierre pivots from 'commit it' to 'who in my system would catch a bad commit'.

Learning move. Asking who-not-what. Instead of describing checks he wants run, he asks which persona owns that responsibility — testing his mental map of the village/skill system. Verifying the system has eyes for an entire class of mistake (committed-secrets) before it bites him.

session ref · 4ee82f98:852

Context. Apr 18 afternoon. The assistant proposed installing a packaged CLI to use the workbench tool. Pierre prefers the lightest-weight integration.

Learning move. Pushing back on tool sprawl. He has a strong prior that installs are tax — and asks for consolidation. The assistant came back with two-line shell aliases instead of an install. Negotiating a smaller solution by stating his constraint, not by approving anyway.

session ref · e2d33ad0:515

Context. Apr 18 evening. After a parallel session merged the workbench skill, Pierre wants a status read AND a direction-to-go question in the same breath.

Learning move. Asking 'what do we need to change' rather than 'is it done'. Treats the merge as a draft rather than a deliverable; expects there's drift to fix. Default-skeptic stance.

session ref · 70109960:426

Context. Apr 18 evening. Substantial restructuring is being proposed; Pierre wants the village's diverse views before signing off.

Learning move. Requesting deliberate disagreement. He's built a multi-persona system specifically so he can stress-test his own decisions through different lenses; this prompt activates that lens-rotation.

session ref · 70109960:526

Context. Apr 24 evening, on a workbench session. The model trained on US tweets reads UK polite complaints as 'sad' rather than 'angry'. Pierre proposes collapsing emotion buckets and 1-2 star reviews into one churn-risk signal.

Learning move. Proposing a domain-justified decision and asking the tool to sanity-check it. 'Does that make sense?' followed by his own three-clause reasoning ('reason being if they stop coming, regardless of emotion, they want to know that'). He's articulating the consultancy logic and inviting challenge.

session ref · 45465c5b:108

Context. Apr 24 evening. The basic notebook is being modified in-place again, and Pierre catches it via a FileNotFoundError when columns moved without an index update. (This is the SECOND time he's caught this same pattern — see 1aaf31e5:1081 from Apr 18.)

Learning move. Pattern recognition across sessions. He saw this exact failure six days earlier and is now catching it instantly. The single phrase 'youre overwriteing again' is the compressed form of a learning that has stuck.

session ref · 45465c5b:561

Context. Apr 25 morning. Day after the second overwrite catch. Pierre adds the rule into the standing instruction set.

Learning move. Promoting a one-off frustration to a standing rule. 'You've got to do versioning right and commit to GitHub' is a lesson moving from incident to invariant.

session ref · 45465c5b:949

Context. Apr 25 morning. Two specific location IDs (345, 398) keep cropping up and Pierre can't remember what was decided about them.

Learning move. Honest about losing track ('I'm kind of losing track again'), naming the specific cognitive miss, then proposing the exact data move (pull both name lists + LLM-assisted fuzzy match) that will fix it. Self-aware of memory limit, decisive about how to compensate.

session ref · 45465c5b:868

Context. Apr 25 morning. Pipeline has bifurcations — a step applied to overall rating but not to per-location rating. Pierre needs the visual to show this.

Learning move. Diagram-thinking. He's spotted the asymmetry himself ('we took common locations and added to overall but not per-location') — the diagram request is to externalise his own internal model so he can verify it against the actual code.

session ref · 45465c5b:1051

Context. Apr 25 morning, on a parallel data-workbench session. Pierre wants to bring fresh learnings (anger+sadness merge, Sonnet+10-shot Qwen) back into an earlier write-up.

Learning move. Treating the report as a living document that gets re-passed when his understanding updates. 'Improve it with what we've learned here' is a deliberate iteration loop — he's not redoing it, he's upgrading it.

session ref · 5204cb6b:42

Context. Apr 25 afternoon. A new agent in this session was about to reinvent something the workbench skill already provides.

Learning move. Caveman-clear reset. 'You've lost the plot' is direct; the fix is even better — go read the claudemd and look around, don't ask me to re-explain the system. He's training the tool to ground itself in repo context before proposing.

session ref · 5204cb6b:742

Context. Apr 25 afternoon. Top-15 negative-review token list is dominated by 'staff', 'people', 'one', 'get', 'time' — words too generic to mean anything for churn analysis.

Learning move. Reading raw output and inferring a config bug ('we don't have good stop words'). Catching a 'random 2 typed in a cell' as separate noise. Real diagnostic instinct from the data, not from the assistant's narrative.

session ref · 5204cb6b:806

Context. Apr 25 afternoon. Tokens are still mostly low-signal. And the joy emotion class keeps hitting on 1-star reviews — clearly wrong.

Learning move. Three nested questions in one prompt: (1) here's evidence the model is misbehaving — show me the examples, (2) is there a better-trained UK model already, (3) if not, how expensive would training one be? This is exactly how a senior analyst escalates: see anomaly, ask for backup, scope the next step.

session ref · 5204cb6b:845

Context. Apr 25 morning. Pierre had been told 8 cohort-feedback patches included seeded UMAP for BERTopic. He confirms each patch one by one, and stops on UMAP to ask for the explanation rather than blindly accept it.

Learning move. Verifying mental model of UMAP role inside BERTopic; voice-dictation slip ('bird topic walls' = BERTopic calls) reveals he was thinking faster than typing. The 'just explain to me what that is again please' is the move — he won't ship code containing a concept he can't define.

session ref · b32262f3:40

Context. Apr 25 evening. Pierre has noticed two parallel sessions are producing two notebook variants and wants to reconcile them before going further.

Learning move. Catching a fork before it diverges further. 'What's the difference?' is the right diff-question — he's not asking which is correct, he's asking what the delta IS so he can decide.

session ref · b32262f3:520