← BC9 Bootcamp (International)All programsHomeSearch
BC9 Bootcamp (International)·Recordings·4:32:17

Day 1: How a Model Learns (Teachable Machine Live), Context Engineering, CO-STAR, Artifacts, Connectors, and Claude Cowork Running a Daily Stand-up

Raghuveer Trainer - growth marketer turned AI consultant; the whole teaching block (0:58-3:31) · Fani Krishna Host ('PK') - logistics, the mindset framing, the hands-on artifact lab

The short version

  1. The boot camp's promise: a three-day, five-level path from awareness to building; 'AI won't take your job, it replaces narrow specialist roles' - be the orchestrator (0:37-0:57). Raghuveer's ladder: basic user -> prompter -> automations -> agents -> builders -> AI generalist (1:04-1:11).
  2. How a model learns, shown not told: a Teachable Machine cats-vs-dogs classifier trained on 100 images per class calls a dog 98% cat; retrained on 500 per class it gets both right (1:11-1:27). Then tokens -> embeddings (king near queen, far from barber) -> attention -> prediction, GPT-3's six pages to today's book series, and 'lost in the middle' - capacity is not capability (1:33-1:49).
  3. Context engineering is the parent of prompt engineering: identity, world, task, example and constraint context; prompt = command; two rules and three habits (edit, don't follow up; new chat per topic; 'no commentary, just output'). System prompt = Tony Stark's character brief, user prompt = the scene - and Anthropic's guardrails push back on a copyrighted persona (1:50-2:17).
  4. CO-STAR (Context, Objective, Style, Tone, Audience, Response) built into a reusable 'Prompt Engineer' project in Claude and ChatGPT from a screenshot of the framework; Haiku fast, Sonnet balanced, Opus most capable (2:17-2:33). Artifacts and Canvas: an interactive 'worry translator' built in both (2:29-2:49).
  5. Connectors are MCP - Excalidraw draws the session's flowchart on command (2:49-2:59). Claude Cowork reads a local app folder, proposes v2, writes a two-week roadmap and schedules a 9 AM stand-up; when the scheduled run fails for lack of context, the roadmap goes into the task prompt (2:59-3:13). Claude for Chrome plays a track and ships an artifact, self-correcting, 'act without asking' (3:13-3:21). Privacy: learn on dummy data, use enterprise or local for real work (3:22-3:26). Lab: build and publish an expense-tracker artifact (3:36-3:56).

At a glance, three clicks deep

Skim here first: the closed row is the glance, open is the study card with the key points and timestamps, and the ↓ link drops to that concept's full write-up below.

01How a model learns: the Teachable Machine cats-and-dogs demoMore and better labelled data -> better model;›

More and better labelled data -> better model; generative AI predicts rather than retrieves.

100/class: 98% cat (1:20-1:23)

500/class: correct (1:24-1:27)

ANI vs generative; AI vs Google (1:04-1:10, 1:24-1:33)

↓ Full write-up of this concept

02Tokens, embeddings, attention - and 'lost in the middle'Embedding = meaning as position;›

Embedding = meaning as position; attention = weighting; long context != reliable recall of the middle.

Cake / address / attention (1:39-1:46)

6 pages -> 64 pages -> a book series (1:46-1:48)

Lost in the middle (1:48-1:49)

↓ Full write-up of this concept

03Context engineering: identity, world, task, example, constraint - and the three habitsManage the five contexts;›

Manage the five contexts; command clearly; edit, new chat, constrain; system = persona, user = scene.

Five contexts (1:49-1:52)

Two rules, three habits (2:00-2:06)

Iron Man system/user prompt; guardrails (2:06-2:17)

↓ Full write-up of this concept

04CO-STAR, and a 'Prompt Engineer' project that writes your promptsSix fields;›

Six fields; a project that converts tasks into CO-STAR prompts; pick the model tier by job.

CO-STAR fields (2:22-2:25)

Framework screenshot -> system prompt -> project (2:25-2:33)

Haiku / Sonnet / Opus (2:26-2:28)

↓ Full write-up of this concept

05Artifacts and Canvas: interactive micro-tools; Chat vs ProjectArtifact = published front-end micro-tool;›

Artifact = published front-end micro-tool; Project = persistent instructions + knowledge.

Worry translator in both tools (2:33-2:49)

Lab: toggles -> prompt -> model -> test -> Publish (3:36-3:56)

Chat vs Project (3:44-3:54)

↓ Full write-up of this concept

06Connectors give the brain hands - and the technology underneath is MCPConnector = MCP server behind a product;›

Connector = MCP server behind a product; start with the tasks you hate most.

Brain-in-a-jar analogy (2:49-2:51)

Excalidraw flowchart live (2:51-2:57)

'Underneath is MCP' (2:57)

↓ Full write-up of this concept

07Claude Cowork: read the folder, write the roadmap, run the 9 AM stand-up - and fix it when it forgetsFolder access + roadmap + scheduled task;›

Folder access + roadmap + scheduled task; give scheduled tasks their context explicitly; browser agent for cross-tab work.

Folder read -> v2 features -> roadmap (3:00-3:06)

Scheduled 9 AM task; fails; roadmap embedded (3:06-3:13)

Claude for Chrome, act without asking, self-correct (3:13-3:21)

↓ Full write-up of this concept

08Learn on dummy data, work on enterprise or local - and keep a personal system promptDummy data to learn;›

Dummy data to learn; enterprise/local to work; a maintained personal system prompt.

Learning vs using AI (3:22-3:25)

The personal system prompt (3:26-3:31)

OpenClaw declined for safety (0:54, 4:20)

↓ Full write-up of this concept

The concepts in full

01

How a model learns: the Teachable Machine cats-and-dogs demo

One hundred pictures each and the dog is a cat. Five hundred each and it knows.

PROCEDURE: Google Teachable Machine -> Image Project -> Standard image model -> classes 'cats' and 'dogs' -> upload labelled images from a Kaggle dataset (100 per class) -> default epochs and batch size -> Train -> test on an unseen dog: 98% cat. Retrain with 500 per class: correct on both. The point, made without a line of code: training-data volume and quality decide accuracy. Framed against narrow AI (spam filters, credit scores, Face ID) versus generative AI's next-word prediction, and Google-as-retrieval versus AI-as-'context engine' - factual only as far as its references.

Why it matters

The most hands-on explanation of training in the corpus.

02

Tokens, embeddings, attention - and 'lost in the middle'

King sits near queen and far from barber. That is what an embedding is.

The whiteboard rule: sentences are cut into tokens 'like a cake', each token gets a numeric address with related concepts nearby, attention weights the words that matter, and the model predicts. Context windows grew from GPT-3's ~2-4K tokens (six pages, 2022) to file attachments (~64 pages, late 2024) to today's book series - but models remember the start and the latest turns best and can hallucinate on facts buried in the middle. 'Capacity is not equal to capability.'

Why it matters

Explains why a key word gets ignored and why long chats degrade.

03

Context engineering: identity, world, task, example, constraint - and the three habits

Prompt engineering is one layer. Context engineering is everything the model is holding when it answers.

Five kinds of context: identity (role or persona), world (situation and audience - 'presenting to a CEO'), task, example (reference material), constraint ('three slides'). A prompt is a command: be specific (the coffee-ordering parody), state expectations, don't mix instructions. Three habits: edit the prompt instead of piling on follow-ups; a new chat per topic; add output constraints such as 'no commentary, just output'. System prompt versus user prompt via Iron Man - the character brief versus the scene - demoed by generating a Tony Stark persona from a screenshot and watching Anthropic's guardrails object until it became 'a character from a superhero series'.

Why it matters

The tidiest statement of the prompting discipline the rest of the camp assumes.

04

CO-STAR, and a 'Prompt Engineer' project that writes your prompts

Screenshot the framework, hand it to a project, and never hand-write a structured prompt again.

CO-STAR = Context, Objective, Style, Tone, Audience, Response - 'around a couple of years, that's a big deal'. PROCEDURE: create a project (Claude) or custom GPT with no instructions; paste the framework screenshot and ask 'convert this into a system prompt for my prompt-engineer assistant'; put the result in the project's instructions; from then on drop any task in and get a full CO-STAR prompt to run elsewhere. Model choice: Haiku fast, Sonnet balanced and good at code, Opus most capable. The lab later builds the same project with the framework file as knowledge.

Why it matters

A reusable prompt factory in ten minutes.

05

Artifacts and Canvas: interactive micro-tools; Chat vs Project

A 'worry translator' built live in both Claude and ChatGPT, broken twice, working on the third pass.

Artifacts (Claude) and Canvas (ChatGPT) build interactive HTML/React front ends from a prompt. PROCEDURE from the lab: claude.ai -> Settings -> Capabilities -> enable the three visual toggles -> new chat -> a detailed prompt (an expense tracker) -> choose the model -> test (add entries, categories, weekly and monthly views) -> Publish artifact to the team or the web. Limits stated: front end only, no database, not sellable in app stores - micro-tools for yourself and your team. A Chat has no memory across chats; a Project keeps instructions and knowledge across every chat inside it (one notebook per subject) and spends tokens more efficiently.

Why it matters

The quickest way to a shareable tool, and the Project habit that makes prompts reusable.

06

Connectors give the brain hands - and the technology underneath is MCP

'Summarise today's topics as a flowchart' - and Excalidraw draws it.

Connectors let the model act on Microsoft 365, Canva, Gmail, Calendar, Zoom, Slack, CRMs - the brain in a jar gets hands. Named plainly: 'the technology it uses underneath is called MCP.' PROCEDURE: enable the Excalidraw connector, ask for the session as a flowchart, get a link with the canvas filled. Advice: connect first the tools behind your most hated recurring tasks (calendar, email).

Why it matters

The first MCP mention in the camp, in the friendliest form.

07

Claude Cowork: read the folder, write the roadmap, run the 9 AM stand-up - and fix it when it forgets

The first scheduled run failed because the task had no memory of the roadmap. The fix was to put the roadmap in the prompt.

PROCEDURE: new Cowork task -> pick a local folder (his 'ADHD Shortcuts' app) -> Always Allow -> 'read the folder, summarise, propose v2 features' -> 'turn that into a two-week roadmap' -> create a scheduled task: daily 9 AM stand-up referencing the roadmap. It fails on first run (missing context); embed the roadmap text in the task prompt and it works. Then Claude for Chrome: 'open YouTube Music and play Daft Punk, then build an interactive artifact that reveals welcome to the agentic era', permission 'act without asking' - it errs, screenshots, self-corrects. Cowork and the extension are Pro features ($20/month pitched).

Why it matters

A live demonstration of exactly the tool this knowledge base is built with, including its first-run failure mode.

08

Learn on dummy data, work on enterprise or local - and keep a personal system prompt

'Call yourself John Doe while you learn.' Once it is real work, it goes to an enterprise plan or a local model.

Separate learning AI (anonymised data, no worry) from using AI (enterprise plans with liability cover, local models, paid private cloud); becoming the internal AI champion who pushes for the enterprise plan is also career protection. Raghuveer's own two-year-refined account-level system prompt: no emojis, hype or filler; no mood mirroring; stop immediately after the information; 'restore independent high-fidelity thinking'; guard against model obsolescence - stay able to think if the tool vanished. A living document to build in Settings. OpenClaw was explicitly not taught: 'it will take access to literally everything on your system'.

Why it matters

Two habits - data hygiene and a standing instruction set - that outlast any tool.

Tools referenced

ToolCoverageMomentContext
Google Teachable MachinedemonstratedCats-vs-dogs classifier
ClaudedemonstratedProjects, artifacts, connectors, Cowork, Chrome extension
ChatGPTdemonstratedCanvas; Projects; custom GPT
ExcalidrawdemonstratedFlowchart via connector
Claude CoworkdemonstratedFolder, roadmap, scheduled stand-up
GetMultiexplainedBonus tool; coupon redemption
KagglementionedTraining dataset
OpenRoutermentionedBring-your-own-key model access
Wispr FlowmentionedDictation; 125 wpm
NotebookLMmentionedRAG for a doctor's textbooks
OpenClawmentionedNot taught - security
n8nmentionedDay 3 automations

Action items

    Resources mentioned

    Resources
    • docBoot-camp logistics
    • docHands-on lab

    Extraction notes

    This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

    Transcript corrections applied

    The transcript saysThe trainer actually means
    Ragwir / Ragmir / Ragweed / Ragu / RVRaghuveer
    Fanikrishna / FannyFani (Phani) Krishna
    Grove School / cross schoolGrowth School
    Enetenn8n
    NumerusNumerous.ai
    Massdaily / RedHealthunresolved former employers

    True on recording day — verify before relying