🚀 Excited to welcome 𝗛𝗮𝗿𝗿𝘆 𝗦𝗼𝗹𝗼𝘃𝗮𝘆 (@harrysolovay) to 𝗘𝗳𝗳𝗲𝗰𝘁 𝗠𝗶𝗮𝗺𝗶 #𝟯! I first discovered Harry through his incredible hardcore TypeScript tutorials on YouTube. His depth of knowledge, creativity, and ability to push the boundaries of the type system immediately stood out. 🎥 youtube.com/@harrysolovay Harry is now building @crosshatchdev, an Effect-native toolkit for x402 payments, enabling applications and AI agents to seamlessly pay for and monetize APIs through programmable micropayments. Alongside projects like Liminal, his work continues to push the boundaries of what’s possible with TypeScript and Effect. It’s a real privilege to have him share his ideas with the Miami developer community! 📅 November 9, 2026 📍 The LAB Miami, Wynwood 🎟️ RSVP: luma.com/0yaas5h2 @EffectTS_ #EffectMiami #EffectTS #TypeScript #AI #FunctionalProgramming #Crosshatch

Decision-model-validated lessons your agent infers from your feedback.

Possibilities with decision models like Jev feel endless. We're using it to build an open-source developer tool, Traits, that desloppifies AI codegen. Crazy future incoming traits.sh/?v=04

Global desloppification, part 2: You can't teach every lesson upfront — and you don't have to. Correct your agent once. It saves the underlying insight for all future codegen.

Decision models change the game

Decision models could damage Anthropic's business. You don't need Opus 5.5 when you can instantaneously run hundreds of natural language assertions on agent output... ... at a fraction of the cost. This approach is being streamlined via Traits. traits.sh/

The post-slop era starts here.

You ask your agent to rename `parse` to `decode`, but it keeps the old file name and aliases the import: `import { decode as parse } from "./parse.ts"` No lint rule can determine that this is slop. System one models can...

Paying special attention to type signature legibility as I refactor the @CrosshatchDev known token type. Type signature legibility is crucial for coding agents. And also, it just feels dam good.

Consumer x402 isn't real quite yet––it'll require simplifying crypto ramping / autonomous wallets / new approaches to permissioned spend / unifying assets across networks. Consumers shouldn't need to reason about the infra itself. Lots of groundwork ahead, but we'll get there.

All of the API's noise is slowly falling away. What's left behind: minimal, composable building blocks for stablecoin payments with x402. @CrosshatchDev

Requiring x402 payment over HTTP, made easy. In the next version of Crosshatch, payment `Required`s implement `Symbol.iterator` such that they can be directly yielded as HTTP effects. Build the required. Yield it. Done. @CrosshatchDev

A brief overview of x402 Payments for the AI era.

Experimenting with @alchemy_run composition patterns. When I want to share layers across workers/DOs, I create a "prelude" effect, which executes during the infra run, and returns a layer, which I then provide to the runtime run. So, a "prelude" is an `Effect<Layer<RIn>>`.

Effectful X25519 encryption. Create a keypair. Encrypt with the public key Decrypt with the private key. @CrosshatchDev