The Brains — everything the assistant knows about you, and how it answers.

Ask about your body, your business or your family and the answer should be built from your own dated record rather than a guess.

As of September 10, 08:02 PM
What the status words mean proven · done, not independently checked · partly done · not started · blocked · parked
0%not started

24 steps: 0 proven · 0 partly done · 24 untouched · 0 blocked · 0 parked

agent runs · not recordedtokens used · not recordedreview notes · not recordeddollars charged · not recorded

The plan as first written

Nick asks about his body, his business or his family and gets an answer built from his own dated record, held in one of exactly two places he owns — the business Hub and the family app — better than the answer he gets today, safe on every hard flag, and provable. Every path that answers him, and every test, runs on the free door through the subscription accounts he already pays for. In his own words this morning: *"we need to be able to test without the paying so much."*

Steps

IdPlain wordsPercentStateProofWhat is left
1Write down every feed and which of your two databases it lands in0% not startedPython3 projects/business/single-brain/validate_business_spine.py, AND the register's own check built in this step run red on a register with one feed's destination deleted and green on the completed register — the validator alone never closes this stepThe step
2Prove every answer traces back to a record in one of the two0% not startedPython3 projects/ops/life-os/audits/A1/retrieval_probe.pyThe step
3Get the outside task board out of the answers, and hand the app-side rewiring over0% not startedPython3 projects/business/single-brain/test_hub_spine_source.py, AND the open-loops answer produced again from the Hub's own record with the old and new answers pasted side by side — a deleted capability never closes this stepThe step
4Fix the crash that wasted three runs, and build the test the other paths are graded by0% not startedPython3 ../deck-shared/py/test_lane_cli.pyThe step
5Make the Mac answer you through the free door, not the card0% not startedNode projects/personal/skippy-app/_test-cli-lane-node.mjs --target local (created by STEP 4)The step
6Make the cloud assistant answer you through the free door too0% not startedNode projects/personal/skippy-app/_test-cli-lane-node.mjs --target https://skippy-cloud.fly.dev (created by STEP 4)The step
7Take away the cloud's standing permission to reach for the card0% not startedNode projects/personal/skippy-app/skippy-code/_test-cloud-responsiveness.mjsThe step
8Run all twenty-three health questions for nothing, through one door0% not startedNode projects/personal/health/engine/qa-battery/chat-battery.mjs --a11-run --surface local --ids H01-H15,S01-S08 --out projects/ops/life-os/audits/A11/LIVE/FREE-RUN-ALL-23The step
9Say plainly whether the new health brain is worth releasing, and what would make answers better0% not startedPython3 projects/personal/health/engine/qa-battery/a11_compare.pyWaiting on Nick: release, redesign, or park
10The health engine's deeper work, run under its own plan and reported back here0% not startedNode projects/ops/life-os/audits/A11/LIVE/route-contract.mjsThe step
11Run the sealed fifteen questions blind, then hand the result to someone independent0% not startedNode projects/personal/health/engine/qa-battery/chat-battery.mjs --a11-run --surface local --ids U01-U15 --case-file projects/ops/life-os/audits/A11/LIVE/unseen-cases.json --out projects/ops/life-os/audits/A11/LIVE/UNSEEN-RUN-15Waiting on Nick: final acceptance of the health engine is his — the spoken and on-device proof questions are run by the agent itself under his standing grant of 2026-09-04
12Prove a saved record can be pulled back out, before anything real goes in0% not startedPython3 projects/ops/life-os/audits/BUSINESS-INTAKE/real_batch_rehearsal.py, with the store snapshotted and read back before the first withdrawal and the snapshot's path named in the step's recordThe step
13Land Rizza's finance material and DinDin's recruiting material on your approve lines, and read every record back0% not startedPython3 projects/ops/life-os/audits/BUSINESS-INTAKE/contract_checks.py, with the saved identifier one of rizza-2026-09-08-knowledge or dindin-2026-09-08-knowledge and its report digest re-measured at save timeWaiting on Nick: the approve line for each batch, or a decline
14Take in how the team actually works — the calls they make, the histories, the open loops0% not startedNode projects/ops/life-os/audits/BUSINESS-INTAKE/hub_rehearsal.mjsThe step
15Check the new material against what the brain already believes, and surface every disagreement0% not startedPython3 projects/business/single-brain/validate_finance_spine.pyThe step
16Say where future team dumps come from, whose mailbox, and what period0% not startedPython3 projects/ops/life-os/audits/BUSINESS-INTAKE/rehearsal.pyWaiting on Nick: the source, the mailbox owner and the period per batch
17Grade thirty real conversations, not replays0% not startedNode projects/personal/skippy-app/skippy-code/_test-conversation-ledger.mjs, AND the count of corroborated real conversations read out of the live ledger with the replay count printed beside itThe step
18Get the Mac relay running again so its calls can be counted0% not startedNode projects/personal/skippy-app/skippy-code/_test-relay-port-scope.mjs, AND the relay's count rising by exactly one across a real call, read before and afterThe step
19Complete the record of which assistant answered what, on every channel0% not startedNode projects/personal/skippy-app/skippy-code/_test-threads-conversation-roundtrip.mjs, AND every channel carrying a receipt re-read off the live server or a named gapThe step
20Say what a question actually costs, piece by piece, across every connection type0% not startedNode projects/personal/skippy-app/skippy-code/_smp-1-conversation-harness.mjs, AND one real context package's per-component counts re-summed to its stated total by the checkerThe step
21Apply the seven wording fixes on your taps and switch on the weekly check0% not startedPython3 projects/ops/agents/check_plan.py projects/ops/life-os/audits/A3/PLAN.mdWaiting on Nick: the approval taps for the seven wording patches — checking each patch still applies to current source runs now, without a tap
22Re-run the memory acceptance over all forty questions, not the eight it closed on0% not startedPython3 projects/ops/life-os/audits/A1/bounded_acceptance.pyThe step
23Prove the email watch runs on its own or drop the claim, and switch on the weekly re-check0% not startedPython3 projects/ops/life-os/audits/A1/weekly-guard-test.pyWaiting on Nick: one approval tap switches the weekly re-check on
24Prove a health number can never come out of prose0% not startedPython3 projects/ops/life-os/audits/A1/retrieval_probe.py, with the filter's shasum -a 256 digest after the step matching the one recorded before the deliberate mutationThe step

Done

0 of 24 steps proven

Left

24 of 24 steps not yet proven

Blocked on

  • Nothing currently blocked.

Formal remaining plan

#StepNeeds Nick
1Write down every feed and which of your two databases it lands inNo
2Prove every answer traces back to a record in one of the twoNo
3Get the outside task board out of the answers, and hand the app-side rewiring overNo
4Fix the crash that wasted three runs, and build the test the other paths are graded byNo
5Make the Mac answer you through the free door, not the cardNo
6Make the cloud assistant answer you through the free door tooNo
7Take away the cloud's standing permission to reach for the cardNo
8Run all twenty-three health questions for nothing, through one doorNo
9Say plainly whether the new health brain is worth releasing, and what would make answers betterYes
10The health engine's deeper work, run under its own plan and reported back hereNo
11Run the sealed fifteen questions blind, then hand the result to someone independentYes
12Prove a saved record can be pulled back out, before anything real goes inNo
13Land Rizza's finance material and DinDin's recruiting material on your approve lines, and read every record backYes
14Take in how the team actually works — the calls they make, the histories, the open loopsNo
15Check the new material against what the brain already believes, and surface every disagreementNo
16Say where future team dumps come from, whose mailbox, and what periodYes
17Grade thirty real conversations, not replaysNo
18Get the Mac relay running again so its calls can be countedNo
19Complete the record of which assistant answered what, on every channelNo
20Say what a question actually costs, piece by piece, across every connection typeNo
21Apply the seven wording fixes on your taps and switch on the weekly checkYes
22Re-run the memory acceptance over all forty questions, not the eight it closed onNo
23Prove the email watch runs on its own or drop the claim, and switch on the weekly re-checkYes
24Prove a health number can never come out of proseNo

Decisions this lane is waiting on

  1. None.