SKIPPY: Skippy tested as Nick uses him — every door, memory, files, hand-offs, two speeds

Updated just now.

52% overall0 of 8 steps finished
  1. Hold a natural spoken conversation and do the family task75%

    ⚠️ only 0 of 2 required verifications recorded so far

    How we know

    Definition of done: the three text doors pass a conversation of at least ten turns (a floor) with context retained across the whole exchange; the voice app passes at least forty messages and answers past the fortieth from the extended memory file; the substantive answer lands within four seconds on the pinned recordings; an independent listener scores warmth, relevance, continuity and humanness at least 4 of 5

    Proof: the relevant item

  2. Finish ordinary work and return delegated results30%

    ⚠️ only 0 of 2 required verifications recorded so far

    How we know

    Definition of done: every destination reads back what was asked, the business workspace card appears in Nick's own view, delegated work returns to the conversation it came from, and a failed worker returns an honest failure

    Proof: the relevant item

  3. Continue without repeating yourself40%

    ⚠️ only 0 of 2 required verifications recorded so far

    How we know

    Definition of done: the second surface answers using the first surface's decision, with no repeated turn, no duplicated record and no change of speaker

    Proof: the relevant item

  4. Read files and return something usable70%

    ⚠️ only 0 of 2 required verifications recorded so far

    How we know

    Definition of done: the content answer is right on every door, the attachment arrives, and Open retrieves the intended file

    Proof: the relevant item

  5. Use Nick's chosen model depth99%

    ⚠️ claimed done with no VERIFIED line from an independent checker — shown as in progress, not done

    How we know

    Definition of done: an open-ended ask on any door (Slack, WhatsApp, Gmail, spoken) gets, within seconds, one line that restates the task and promises a return ("On it — I'll check X and come back here in a few minutes"), then the real result — cause, evidence of what was checked, what was done or the one decision Nick must make — in the SAME the relevant record session, minutes later, from an Opus worker with the whole workspace; a quick ask ("what's the weather", "add milk") stays seconds on Sonnet with no "on it"; every "on it" is a tracked task with an origin and a deadline, and a task nobody picks up comes back as one honest line by its deadline, never silence; no tool is withheld from a turn because of a word in the sentence, and no canned sentence ever replaces an answer.

    Proof: the relevant item — Nick's exact Anatoly ask replayed on Slack (ack within 30 s, evidenced result in-thread within 15 min), the weather control (seconds, no "on it"), the stopped-worker control (honest line by the deadline), and the same ask spoken on the Talk page with the result spoken back.

  6. A look-up answers in under a minute, with a running commentary, without booting a session0%
    How we know

    Definition of done: an ask that only needs reading (where a post stands, what a card says, what a file contains, where a lane left off) is answered by the brain itself in the turn, with its own tools, in under 60 seconds end to end on the relevant record and under 90 on voice; while it works the person hears or sees what it is doing every 10–15 seconds ("reading the Captus cards… checking Anatoly's link… nearly there"); the acknowledgement says WHAT it will check, WHERE it will look and what, if anything, it is handing to a separate worker; a separate Opus session is started only for work that changes things or genuinely needs a builder, and when it is, the worker's two-minute progress lines reach the person, a standing per-machine workspace copy replaces the five-minute copy, and a "start here" pointer in the brief puts its first useful action under a minute; the four kinds of "where does X stand" read their own sources with their age stated (the lane plan for build state, the business workspace board for cards and posts, the running-sessions list for "is anyone on it", conversation memory for what was said)

    Proof: the relevant item (CREATED BY STEP 0) — Nick's Captus ask replayed on Slack and spoken: first useful words within 60 s, the commentary counted, the answer graded against the board; the weather control; one genuine build ask that still goes to a worker with its progress relayed; the four source classes (the relevant item)

  7. The job runner cannot be stalled by one job, and a stalled carrier is noticed and restarted within fifteen minutes99%

    ⚠️ claimed done with no VERIFIED line from an independent checker — shown as in progress, not done

    How we know

    Definition of done: a job whose file hangs or fails at load is isolated to its own row and the runner boots anyway, with the row saying the module is still running; a nightly check imports every scheduled job in its own child with a 20-second ceiling and fails on one that hangs; a watchdog outside the runner, on the machine that owns the jobs role only, restarts it when both hand-off carriers have had no successful run for fifteen minutes (judged on the runner's own local log, never the shared heartbeat file), at most three times an hour with a 20-minute cooldown, then raises a signal to a person; every restart is written into the runner's own self-restart record; the watchdog is declared in the machine's approved services

    Proof: the relevant item (every scheduled job loads in time) and the relevant item (the restart decision and the budget) · FAILS IF: the runner writes no boot manifest with a hung job present, the watchdog restarts a runner with a carrier row under fifteen minutes old, or the guard fails on the real folder for something that is not a defect

  8. Every confirmation carries the thing it changed, not a description of the checking0%
    How we know

    Definition of done: when Skippy confirms an action, the reply carries the link to what changed — the business workspace card, the item on the family list, the calendar entry, the thread a message went into — as a link under the sentence on Slack, WhatsApp and Gmail and as a tap-to-open chip on the Talk page (the same shape as the file hand-back card), with the spoken line unchanged; the words stay human ("Renamed." / "It's on there for Friday.") and the proof rides alongside; behind a switch so it can come off once trusted

    Proof: the relevant item (the action turns of the existing instrument, graded for a link that opens the right record; CREATED BY STEP 0 for the new grading) · FAILS IF: a confirmation names no link, a link opens the wrong record, or the words return to report-speak