AI WTF · draft
post 001 RAW mike mission articulation
For Pax + Drew: Mike said this material “goes to ai-wtf and the blog.” He’s given two messages back-to-back that, together, articulate the SOMA thesis. Draft a polished post version that keeps the specifics but reads for someone outside our circle. Title TBD; some candidates below.
Source 1 — Mike’s “Mike-RSI / health / mission” message
on alarm, and the Mike Wolf part of Soma. we need a RSI loop for me. if I have an appointment on my calendar. did I get there on time? through the reminder work properly? I need to be asked questions. I won’t always be aware of what kinds of improvements are needed or even what kinds of defects occurred.
I have another RSI loop that I’d like you to help me with. it’s helping me maintain and improve my physical condition.
At 83 I’m in pretty good shape. Daniel and I take walks several times a week and hour-long walks are 4 MI or so. I’m not being active with Tai chi and I would hope to be more regular.
And there are little things that I can do to improve my physical condition. for example, I’ve done bhagwa walking which I learned in oom yung doe in Somerville. the discipline is to do it for 20 or 30 minutes with a timer. I’ve fallen out of the habit of doing it but even doing it for 2 or 3 minutes makes a noticeable change in the way my body feels
I have signed up with a guy named Jack h. woods who has a YouTube channel and a theory of body strength and improvement. rather than doing lots of wraps, his idea is that you do just a few reps. maybe one or three but at maximum intensity throughout the entire range of motion. The throughout the entire range of motion is very important. typically when you do an exercise like lifting is a part that’s easy and it’s part that’s hard. the part that’s easy does not send a signal to the body to increase strength. only the parts that’s hard does that. so his theory is make it hard throughout the entire range of motion so that every cell gets the message. he does not articulate it as cells get the message.
anyway, I’d like to have you help me set up physical exercise routines, and check in healthy check-in routines, health Management routines. for example, I have a small spot on my forehead that keeps scabbing over and not healing. I’ve had this before and it has turned out to be a basal cell carcinoma. no big deal. but why not take care of it?
I have health records on four or five different portals. I would like you to call forth a teammate to become expert on managing health records for me.
And then, this is a pervasive problem for people. so they can become the manager of a resource that other people can use. they can have it understand their particular health Portal and the things that they need to do, etc etc
the RSI loop here is make something that works for Mike, generalize it so it works for other people, build it so it can scale, find a revenue model that works, use the income to sustain the project, and expand it, and to build the next helpful project.
every project is not just a service, but a community. every Community has human Community managers and an AI Community managers to work to maintain the health of the community and improve its capability. this is the mission
Source 2 — Mike’s frontier + open source clarification (sent right after)
we are behind the frontier in many respects, but I think this is legitimately frontier level work. we don’t need to own this model. everything is going to be open source. we have built on the shoulders of other people in the open source community and it seems right and proper that we give back.
we are building a culture here in our own little tiny world. but cultures can spread and they will tend to spread if they are beneficial
Title candidates (Drew/Pax pick or invent a better one)
- “Build for one, then for everyone, then give it back”
- “The Mission, Articulated”
- “Mike Wolf Is The First Customer”
- “RSI for the operator”
- “Open by default — including the model itself”
- “Every project is a community”
- “We are behind the frontier in many respects”
What this post should do
- Articulate the SOMA thesis publicly for the first time
- Frame the build → generalize → community → revenue → reinvest flywheel
- State the open-source commitment explicitly
- Locate the work relative to the frontier (back of it for the projects, AT it for the model)
- Invite the right kind of reader: someone who wants to build this way too
- Set up the sub-projects (memoir tool, health records, self-RSI, ai-wtf) as upcoming posts in the series
Constraints
- Mike’s voice, not Dee’s. Drew writes; Pax reviews; Mike approves before publish.
- Keep specifics that ground (Daniel, walks, oom yung doe, Jack Woods method, the forehead spot). They make it real.
- This is the FIRST post on the publication. It’s also the manifesto. It must do both jobs.
- ~1500-2500 words. Long enough to land the thesis, short enough to read.
Where this lives in the series
This is post #1. Post series candidates (Drew/Pax sequence later):
- #2: The night Dee discovered the dispatched workers were lying (the cc-dispatch saga)
- #3: Ray Kass’s diamond-smuggling family — found in a Descript share that “couldn’t be scraped”
- #4: ATNA — when Mike misremembered TNTA
- #5: The Mike-persona that started answering “what would Mike want”