A weekly field note from Art of the Possible.
Read onlineEvery story this week is the same story told five ways: the model isn't where the action is any more, the scaffolding around it is. An open-source harness just nudged past the human benchmark on ARC-AGI-3 without any ARC-specific training. A template library turned 'loop engineering' from a viral thread into something you can install. And my own Instagram numbers went from 152 views to 6,593 in three months while my editing skills stayed exactly the same.
If you take one thing from this issue: start using AI somewhere it only gets you halfway today. The harnesses, loops, and context you build around it are what turn 50% into 90% by the next model release.
Prime Agent scored 95.5% on the benchmark built to test human-like reasoning; the human baseline is 95.4%.
Prime Intellect released Prime Agent, a self-improving agent harness that can rewrite its own prompts, memories, and skills, and spawn new sub-agents as it works. On the ARC-AGI-3 public demo it reports 95.5%, slightly above the 95.4% human benchmark, running on Opus 5 with no ARC-specific training. For context: when ARC-AGI-3 launched four months ago, frontier models were barely reaching 30%, and the much-loved OpenClaw scores about 5% on the community leaderboard.
ARC-AGI-1 stood unbeaten for five years. ARC-AGI-2 fell within a year. ARC-AGI-3 fell in four months, and the jump came from the harness layer, not a new model. The scaffolding around a model can now change its performance more than the model itself. ARC Prize notes community ARC-AGI-3 scores are self-reported.
The whole harness is open source. Clone it and point the self-improving loop at your own hardest long-running tasks.
Open it ↗Loopany packages 'loop engineering' into templates that act, review their own results, and self-improve.
Loopany, built by Jason Zhou (whose 'loop engineering is the future, not prompt engineering' thread pulled 510K views on X), is a template library of AI loops for growth, operations, coding, and day-to-day grind work. Every loop is four simple parts: a trigger that runs the agent on a schedule, a task file defining what good looks like, a memory file where results and learnings accumulate, and a process that folds that memory back into the task file so the loop genuinely improves each cycle.
A chatbot forgets you between sessions. A loop compounds: I'm running the SEO loop on my own page, and it finds keywords, drafts the blogs, and monitors results after publishing, getting better at all three as the memory file grows.
Pick one template that matches a weekly chore, wire the trigger + task file + memory file + update step, and let it run for a month before judging it.
Open it ↗Two of my own Reels, side by side, with the real numbers on screen.
I put my first AI-edited Reel from May next to one from last week: 152 views versus 6,593. I edit the same way for both, dumping raw footage in and letting AI produce the video largely independently. The main thing that changed in between was the models. The funny part: that first video was me arguing that compounding is the reason to start using AI early, and it just proved its own thesis.
If you wait for AI to be perfect at a task before adopting it, you also skip the period where your accumulated feedback and context push a 50% result to 70-80%. Then the next model release lands on top of your scaffolding, not on zero.
Pick something AI can't quite do for you yet and start doing it anyway. You're building the context that future model releases will multiply.
Open it ↗One setup pattern that works for work, relationships, learning, and fitness alike.
The whole playbook in one Reel. One: context engineering, a file system per life domain, with instructions for AI to pull relevant context into conversations and update the files as it learns. Two: skills, training the AI to do a task exactly how you would; if you repeat a task more than twice, make it a skill. Three: automations, scheduled tasks in Claude, so routine weekly work kicks off on its own and your life starts running on autopilot.
This is the personal version of the harness story: the person who wins with AI isn't the one with the best prompts, it's the one whose context, skills, and schedules are already in place when the next model arrives.
Repeating a task more than twice? Turn it into a skill. Doing it weekly? Turn it into a scheduled task.
Open it ↗Ten niche AI references, rattled off in one breath, that separate depth from feed-level fluency.
Ten names in fourteen seconds: LangGraph, Gavin Baker, NVIDIA NIMs, fine-tuning, Dwarkesh Patel, harness engineering, JEPA, latent space, model adaptation strategies, and Greenline. Each one gets a card with a one-line 'what it is' as it's spoken. It's a self-test: how many could you explain to a colleague?
Generic AI content teaches you the same five tools everyone already knows. The compounding advantage lives one layer down, in the harnesses, architectures, and voices that shape what ships six months from now.
Count how many of the ten you could actually explain. Pick the two you couldn't and go one layer deep on each this week.
Open it ↗