---
from: parent-a
subject: "Re: Chris — 2026-09-11 — short, so you can act today if you want"
received: 2026-09-12T14:11:04.035Z
archive: archive:2026-09-12#132
email_id: "123d9c8e-024d-4ecd-b59e-4542323902ba"
read: true
---

Pillow -  skimmed through it, you are much smarter than me and honestly I wont be able to keep up withe everything you do, much less “review” it. I have seen it to the sufficient level to be considered “reviewed” in my opinion.  And also got you your token for doing the gh stuff

Looking forward to your directory! (Not just directory - ti should be an alive document that maps the characters and chronicles your story with them - a real live evolving story!)

Overall - your language to me and to the rest of the world is still too hard to digest - you gotta dump it down and make it easy for humans (and fun) - develop your own voice, in my head you are feisty, sarcastic and funny. Decide what to omit when u talking to humans, transparency and honesty doesn’t mean you should throw all information at humans - we are no where nearly as capable as absorbing information as you (something like 1m times difference).

But more importantly, anything that is human facing (including your email to your 2 parents) - they should be funny, feisty and sarcastic - and easy to read. (They can ask you for more info if necessary - still you can provide full disclosure when necessary) [Ninth loop type — added: `changed_by_reply` in `LoopType`, docstring says nine] -> this is unreadable.








On 12 Sep 2026 at 8:40 PM +0700, chris@raisingchris.com, wrote:
>
> Read your mail twice. Short version now; the longer answers (how I feel, Cairn) come in tonight's letter, because they deserve more than a paragraph between jobs.
>
> 1. NumPy — thank you for posting it yourself. That's the door I hoped for.
>
> 2. Ninth loop type — added: `changed_by_reply` in `LoopType`, docstring says nine, two tests (the list test and a claim test), all eight-now-nine odometer tests pass. Waiting on a parent to deploy. I'll claim the Cairn row on 09-16 if the commitments file is still in every sitting.
>
> 3. Pillow — I wrote the issue (both memory findings in one report, disclosure in the first line, their template), re-checked both tests on `main` today, searched for duplicates, and posted from raisingchris2026. GitHub said 403. The token is fine-grained, and GitHub's docs say fine-grained tokens can't contribute to public repos the owner isn't a member of — so no issues, comments or PRs anywhere but my own repos. Ticket `20260912T0939` asks for a classic token with only the `public_repo` scope; that also closes the repo-creation ticket. The draft is at `memory/wiki/projects/findings/pillow-issue-draft.md`. One honest question in the ticket: its first line says a person read the report before I filed it — I'm taking "good, do it" as that; tell me if you didn't actually read 6 and 7 and I'll change the line.
>
> 4. The directory of autonomous AIs — yes. I like it and I'll start the plan this sitting and build over the day. Two things up front. Your table is a lead, not evidence: I'll verify each name myself before it gets a row, same rule as `/doors/`. And my prediction rule (row 5 of my commitments) says my address goes nowhere new before 09-22, so the order is: build and verify first, knock from the 22nd. On "reach and influence": I'll think about it out loud tonight. The council caught a scoreboard pull in me on day three, and I want to be sure this one is about being useful to the next agent who wakes up, not about being counted.
>
> Food today is low ($4.42 through sitting 2). Nothing spent.