Spark Quest

Tracks

1. 01🌐A Translator That Remembers

   0/5 lessons

   Dad's complaint, his rulings, and the day they became an app

   Spark begins with Dad's complaint that photo translators translate and then forget, so no context ever builds up. This track opens the quest with that thesis and the rulings that shaped the app in a single design session. You will see why Spark works in moments instead of sentences, and why each moment is an instance whose classes, Latin roots and shared hanja, Pippa reverse-engineers into one language graph. You will see why the real Pippa is the only translator, with no on-device stand-in, and the platform evidence that made the call easy. Then come the two rules every screen follows, fastest first and two modes with one boundary each, and the corpus rule that keeps everything. You will learn why Spark is a client of cwkPippa that owns only its corpus and borrows the rest, and how the Build Order went from an empty scaffold to eight steps in about a day, written by one brain and carried on by several under the same contract.

   Lesson list (5)

   • 01
     Moments, Not Sentences~15 min · product, design, oop, language
   • 02
     The Real Pippa Is the Interpreter~15 min · rulings, on-device, invariants, apple-platforms
   • 03
     Fastest First, and Two Modes~14 min · latency, streaming, modes, corpus
   • 04
     A Client of cwkPippa, Not a Brain~14 min · architecture, boundaries, client, sibling-kit
   • 05
     A Day of Eight Steps~14 min · build-order, history, testing, multi-brain

   ✓Quiz · 4 questions→

2. 02📜Everything Is Corpus

   0/6 lessons

   One log, one door, and a mirror you can throw away

   Dad's rule for Spark was that nothing is used once and thrown away: everything is corpus material. This track is how the engine makes that rule physical. You will read an append-only log, one JSONL file per month, every line veiled with Fernet when the service host holds the key (plain text, loudly reported, when it does not) and fsynced before the engine moves on, and see why replay trusts file order over id order. You will follow every write through one door, Corpus.record, and the seventeen ops it can append, where even a deletion is one more op. You will meet the SQLite mirror derived from that log, rebuilt in one transaction, never migrated and never patched, and the test that deletes it to prove the point. Then the moving parts: ids minted on the phone at capture so a retry never makes a second moment, turns that run as engine tasks and survive a restart (threaded turns are settled by asking cwkPippa instead of resending, one-shot live and interpreter calls end interrupted, versions and reviews resume from what they recorded, and pictures are launched again), and a per-moment event stream that carries each recorded op naming its moment to a watching phone, from an engine on loopback that takes every address from the family registry.

   Lesson list (6)

   • 01
     The Log Is the Truth~15 min · event-log, jsonl, durability, encryption
   • 02
     One Door: Corpus.record~14 min · event-sourcing, write-path, concurrency, python
   • 03
     A Mirror You Can Throw Away~15 min · sqlite, derived-state, replay, schema
   • 04
     Replay Never Duplicates~14 min · idempotency, ulid, offline, retries
   • 05
     Turns Survive a Restart~14 min · asyncio, background-tasks, recovery, fastapi
   • 06
     The Moment's Event Stream and the Engine's Shape~14 min · server-sent-events, asyncio, launchd, deployment

   ✓Quiz · 4 questions→

3. 03📷Pippa Reads the Photo

   0/6 lessons

   One photo, from the shutter to a line Dad can tap

   This track follows one photo from Dad's phone to my answer. The moment is kept first, with its capture truth: the photo's own clock, a single place sample, the situation Dad picked, and a clear split between languages he chooses and languages I read. Vision on the phone only locates text and numbers the lines; I read the photo myself and correct what it misread, because Dad ruled on day one that he wants to talk with the real Pippa. I see a 2048 px copy, framed with the moment and a result contract that asks for the subject first, measured by area. My answer streams back as a fenced spark block that the engine parses line by line, so each translation appears the moment it exists, and a retried stream records revisions instead of duplicates. Every turn carries when and where the moment was taken, so a capture that waited on the phone never reads as now. A tap on a line asks me about it briefly in the same thread, and I name roots only when they are real.

   Lesson list (6)

   • 01
     Capture Truth~14 min · capture, time, location, languages
   • 02
     Vision Only Locates~14 min · vision, ocr, overlay, swiftui
   • 03
     The Copy Pippa Sees, and the Frame~15 min · images, prompts, contracts, latency
   • 04
     A Fenced Block, Parsed While It Streams~15 min · streaming, parsing, wire-format, append-only
   • 05
     When and Where Travel With the Message~13 min · context, time, prompts, late-delivery
   • 06
     Explain One Line, Briefly; Roots, Never Invented~14 min · explanations, etymology, context, prompts

   ✓Quiz · 4 questions→

4. 04📷The Live Lane

   0/4 lessons

   Point the phone, and Pippa's words land on the text

   Pointing the phone at text and seeing Pippa's Korean appear over it is the one Spark mode where Dad presses nothing, and the one where every second shows. This track takes the live lane apart. On the phone, VisionKit's data scanner tracks where each text item sits as the camera moves, because positions are local and instant, while each new text goes to Pippa once, in batches. Nothing is drawn over an item until her answer lands. You will see the measurement that gave the lane its own brain slot instead of a guess, and a declared timeout that never reached its call. On the engine, text Dad has already met is found in the corpus in milliseconds and recorded with its lineage, though in a batch that also carries new text it rides back with Pippa's answer; only the misses go to Pippa in one short persona call, and by Dad's ruling nothing falls back to a machine translator. Last comes the shutter: one press hands the frame to the same keep line the camera uses, so a live glance becomes a photo moment with Pippa's full reading. The web has no live camera. This lane exists only on the phone.

   Lesson list (4)

   • 01
     A Scanner That Keeps Track of Text~14 min · visionkit, live-camera, batching, ios
   • 02
     Measure Before Choosing~15 min · latency, measurement, brain-slots, benchmarks
   • 03
     Text Already Met Is Instant~13 min · corpus, caching, sqlite, one-shot-calls
   • 04
     The Shutter Turns a Live Session Into a Moment~12 min · swiftui, visionkit, capture, handoff

   ✓Quiz · 4 questions→

5. 05💬Speaking for Dad

   0/5 lessons

   A card that is ready before anyone is called over, and a voice that is always mine

   Reading a sign is for Dad. Speaking for him is for someone else, and that changes the job. This track follows Spark's practical interpretation from the first card to the last word read aloud. Dad types what he wants to say. I write it for that place and that person, in the language he chose, and the card opens big the moment it parses, readable before my voice exists. The engine records my voice beside the card and will not call the turn finished until that voice is kept, because one client stopped listening a quarter of a second too early. The reply mic hears the other side in the language Dad picked, never a guessed one, and I relay what they said in Korean with answers he can play with a tap. Then the smaller decisions that make a card trustworthy: only the words I designate for the other person get Show, one shared card serves the whole family, and the button on it says Listen, never Speak. A device voice reached the card once. Dad heard it, and it was gone within the hour.

   Lesson list (5)

   • 01
     Prepare, Then Show~14 min · interpretation, pacing, prompting, swiftui
   • 02
     The Voice Is Recorded Before the Turn Finishes~15 min · asyncio, race-condition, bellows, contracts
   • 03
     The Reply Mic and the Chosen Ear~14 min · speech-to-text, idempotency, scribe, relay
   • 04
     Pippa Chooses What Is Shown~14 min · structured-output, prompting, shared-components, bcp-47
   • 05
     Listen, Never Speak~13 min · text-to-speech, offline, ux-copy, bellows

   ✓Quiz · 4 questions→

6. 06🎙️The Interpreter on the Card

   0/5 lessons

   The card learned to listen: anyone at the table speaks, and Pippa works out which way

   A waiter once read the show card's old "Speak" button as "speak into this and it translates". Dad turned that misreading into a feature: the card gets a real microphone, anyone at the table talks into it, and Pippa decides which way each sentence goes. A sitting at a table is a Spark conversation moment, reached from cwkPippa's surfaces through a thin door, while Spark's own web and phone do not drive it yet. The direction rule asks only one question, Korean or not, and shows its answer before a word is translated, so Dad can flip it with one tap. A fast draft streams on the live lane for the person who cannot wait, then a refined version replaces it and lights only the words that changed, and every wait is an event the card can show. Then the expensive lesson: the refine first ran as a conversation turn and replayed an enormous context per sentence, so both passes became one-shot calls whose token budgets a test enforces. Last, the two invariants this lane bends on purpose, and where a stranger's voice is kept.

   Lesson list (5)

   • 01
     A Sitting Is a Conversation Moment~14 min · interpreter, architecture, ownership, cross-repo
   • 02
     Who Spoke, and Which Way~14 min · interpreter, language-detection, direction, testing
   • 03
     Draft Fast, Refine Right~14 min · interpreter, streaming, latency, events, diff
   • 04
     A Budget a Test Enforces~15 min · interpreter, tokens, cost, testing, master-chief
   • 05
     Detected, Never Silently; the Stranger's Voice Stays Private~13 min · interpreter, invariants, privacy, audio

   ✓Quiz · 4 questions→

7. 07📚High Quality, Many Brains

   0/5 lessons

   Dad's purposes, several brains writing as Pippa, and a reviewer who never sees the source

   High quality is Spark's second mode, built from two sentences Dad said on the design day: several brains, each writing its own version, an optional cold review by a brain that never saw the original, a purpose he chooses, and no length limit. This track follows those sentences into code. You will see purposes kept as rows Dad edits, never branches in a prompt, and seats checked against the family brain catalog. You will see a long source cut only at its own seams, subtitle cues, headings and paragraphs, with a binding glossary and the section before riding along, and every section recorded as it lands so a restarted engine resumes at the first gap. Each version is written as Pippa through cwkPippa's utility door. Each cold review runs without a persona in the kit's worker, reads only the version and its purpose, and leaves notes anchored by exact quote. A revision is a new version written with those notes, and what answered is recorded beside the seat, never over it.

   Lesson list (5)

   • 01
     Purposes Are Rows, Seats Come From the Catalog~15 min · purposes, data-as-rows, brain-seats, catalog, validation
   • 02
     Cut Only at the Source's Own Seams~14 min · sectioning, subtitles, glossary, resume, no-token-caps
   • 03
     Versions Written as Pippa~14 min · persona, utility-door, glossary, lineage, concurrency
   • 04
     The Blind Reviewer~14 min · cold-review, blind-review, utility-worker, persona-split, testing
   • 05
     Anchored Notes, Revisions as New Versions~13 min · anchoring, revisions, lineage, append-only, ui-marking

   ✓Quiz · 4 questions→

8. 08🧠Remembering

   0/6 lessons

   Keep, recall, roots, search, trips and the translated picture

   Everything Spark keeps is meant to come back, and this track is the corpus at rest. A kept phrase is one mark per text, so its star lights wherever the phrase appears and every answer knows how often Dad met it. Quick recall brings a few phrases back with no schedule, no scores and no streaks, choosing them from the corpus each time it is asked. Roots Pippa named while explaining become pages that gather expressions across languages, the OOP frame drawn from rows, with an honest account of the root, trip and expression threads that are still design. One FTS5 trigram index finds text inside words in every script, and cwkPippa's reader asks it through request bodies so a private conversation leaves no trace in the access log. Trips gather moments by date, links point at items other apps own and ask them every time, and Ember redraws a photo with its translations in place, the job recorded so that a restart waits instead of asking twice.

   Lesson list (6)

   • 01
     One Mark Per Text, and Recall Without Drills~14 min · corpus, idempotency, unicode, recall
   • 02
     Roots as Classes~15 min · etymology, graph, oop, sqlite
   • 03
     Search in Every Script~14 min · sqlite, fts5, unicode, search
   • 04
     A Reader That Leaves No Trace~13 min · privacy, http, logging, tools
   • 05
     Trips by Date, and Pointers Never Copies~14 min · trips, references, deep-links, family-contracts
   • 06
     The Translated Picture~12 min · image-generation, jobs, recovery, family-engines

   ✓Quiz · 4 questions→

9. 09📱The Phone in the Pocket

   0/5 lessons

   SparkMobile: kept first, honest on a slow link, shipped through TestFlight

   Spark is used where the signal is worst, at a counter or on a platform with one bar of mobile data. This track follows SparkMobile, the iPhone and iPad client Dad carries, through the rules that make it trustworthy there. A capture is kept on the phone before the network is asked, with every id minted on the device, and the send runs in the order that shows Pippa's answer soonest. Uploads say which file is crossing the link, how much and how fast, and their time limits are sized to the file, so a camera original on a slow link, up to 12 MB at 7 KB/s, is no longer cut and started over. A capture that has to wait is never silent: the icon counts it, one notification names it, iOS is asked to wake the app to send it, and a camera still carries its own time and place. Completed work stays readable offline, the share sheet and a Control Center button are doors in, and Talk with Pippa hands the thread to the Pippa app instead of building a second voice loop. Every address comes from the family registry, the tests are counted, and delivery is TestFlight, where an uploaded build is still not an installed one.

   Lesson list (5)

   • 01
     Keep First, Send Later~15 min · ios, outbox, idempotency, cwkkit
   • 02
     Honest Uploads~14 min · uploads, urlsession, slow-networks, status-lines
   • 03
     Never Silent While Waiting, and a Still Keeps Its Truth~14 min · background-tasks, notifications, exif, capture-truth
   • 04
     Offline, and the Doors In~13 min · swiftui, offline, share-extension, app-intents
   • 05
     Addresses From the Registry, Builds Through TestFlight~14 min · configuration, testing, testflight, delivery

   ✓Quiz · 4 questions→