Build or Replaced
Today: Steam Machine launches today | Polymarket has flooded social media with deceptive videos by paid creators | GLM-5.2 – How to Run Locally Episode date: 2026-06-23.
Download MP3 →JOSH: It's Tuesday, June 23. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: Today's theme is trust the stack, not the headline. JOSH: Stick around — Erik's got an AI pro tip at the end about making agents prove they have the right context before they touch anything important. [pause] JOSH: Headlines first. Valve's new Steam Machine is not launching today. It's opening the path to launch. What's the real story? ERIK: Reservations are live now, the randomized selection is June 25 at 1 PM Eastern, and purchase emails go out June 29. Starting price is $1,049, which means this is not a cheap console. It's Valve trying to make Windows optional in the living room. [beat] JOSH: Second headline. GLM-5.2 specs are flying around: massive parameter count, huge context, local quantized builds. What should builders believe? ERIK: Believe the model card when it lands, not a screenshot with big numbers. The signal is still real, though. Local models are moving from demo toys into worker agents. [beat] JOSH: Third headline. Polymarket is getting heat over paid creator videos that looked fake. Is this just crypto being crypto? ERIK: It's worse than sloppy marketing. Reports say creators were paid up to $3,000 a month, some videos showed fabricated wins, and the campaign drove roughly $900,000 in deposits. That's not growth hacking. That's a trust leak with a logo. [pause] JOSH: Start with Valve. Why does a $1,049 Steam Machine matter when consoles are cheaper? ERIK: Because Valve isn't trying to be PlayStation with a beard. They're building a route around Windows. [beat] ERIK: The first Steam Machine wave years ago was early. Linux gaming was not ready. Drivers were weird. Proton wasn't mature. The hardware story was messy. It felt like a PC pretending to be a console and asking you to forgive it. JOSH: That's not a great sales pitch. ERIK: Correct. "Please debug your couch" is a hard product category. [beat] ERIK: This time is different because Steam Deck changed the proof. Proton got better. SteamOS got better. Developers started treating Linux compatibility like it mattered. Users stopped caring what the operating system was called because the games launched. JOSH: So the box is less important than the stack? ERIK: Exactly. Hardware is the visible part. The stack is the business. [beat] ERIK: Valve has the store, the library, the controller work, SteamOS, Proton, cloud saves, community, mods, and now a living room target. That's not one product. That's layers. JOSH: But the price is still high. ERIK: It is. Starting at $1,049 puts it above a PS5, above an Xbox Series X, and even above the PS5 Pro. Valve says they're not subsidizing it like a console maker would. [beat] ERIK: That means they aren't using the old closed-box math. Sony and Microsoft can eat hardware margin because they make it back through the store and subscriptions. Valve already has the store. They're saying, "Buy this if you want the PC version of the couch." JOSH: Does that limit the audience? ERIK: Absolutely. This is not for everyone. The first buyers are Steam library people, Linux-curious people, and the "I want one box under the TV that doesn't behave like a corporate laptop" crowd. [beat] ERIK: But the strategic part is SteamOS for desktops. If regular builders can install SteamOS on their own PC components, the official box becomes a reference build. That's a lot more interesting. JOSH: Why? ERIK: Because platforms win when other people can build on them. One box is a product. A repeatable operating layer is a movement with drivers. [beat] ERIK: Same reason I don't build one-off scripts and call it automation. PrimeBus works because events go on the bus, agents subscribe, telemetry comes back, and Gandalf reviews code before merges happen. The value is not one agent. It's the pattern. JOSH: You're comparing Valve to your automation bus? ERIK: Yeah. Same shape. Different toys. [beat] ERIK: Valve hides Linux pain behind SteamOS and Proton. I hide operational pain behind NATS, PrimeBus, and review agents. In both cases, the user should not have to care about the ugly middle. JOSH: What does Microsoft do here? ERIK: They should be nervous, but not panicked. [beat] ERIK: Windows is still huge for PC gaming. Nobody serious pretends otherwise. But a platform can be huge and still be tolerated instead of loved. That's where the opening is. JOSH: Tolerated is dangerous. ERIK: Very. Engineers know this from enterprise tools. The tool everyone complains about but still uses is fine right up until a good-enough replacement removes one daily pain. [beat] ERIK: Valve has been removing pain slowly. Steam Deck made Linux gaming normal for a lot of people. Steam Machine tries to put that same idea under the TV. SteamOS desktop says, "Bring your own hardware." JOSH: So this isn't about beating consoles this summer. ERIK: No. It's about making the default less default over time. [pause] JOSH: Move to GLM-5.2 and the local AI chatter. You said don't trust screenshots. Why are you still interested? ERIK: Because the direction matters even when the rumor math is messy. [beat] ERIK: People are throwing around claims like 744 billion parameters, million-token context, and DynamicGGUF quantized builds. Fine. Maybe some of that lands clean, maybe some of it doesn't. Until there's a model card, weights, evals, and repeatable local runs, I treat the numbers like a weather forecast from a group chat. JOSH: That sounds fair. ERIK: Builders need that discipline. Big model numbers are fun. They are not a deployment plan. [beat] ERIK: What matters is whether the model can do useful work in a real workflow. Can it classify events? Can it summarize logs? Can it read a failed test and point to the right file? Can it run locally without turning your machine into a space heater with opinions? JOSH: Where does local AI fit for you right now? ERIK: Hermes. That's my local agentic backend on the Mac M3. It runs qwen3-coder around 70 tokens per second. [beat] ERIK: That's not replacing Claude for serious reasoning. Claude is still where I go for bigger code work and harder judgment. Hermes is a worker. It does small jobs close to the system. JOSH: What's a small job? ERIK: Classify this event from PrimeBus. Summarize this traceback. Compare two config snippets. Draft a boring response. Decide if a message looks like a task, an alert, or noise. [beat] ERIK: Those jobs don't always need a frontier model. They need speed, privacy, and enough accuracy to be useful with guardrails. JOSH: What's the guardrail? ERIK: Blast radius. [beat] ERIK: If a task touches production behavior, money, security, customer data, or a merge decision, it gets stronger review. If it's a local summary or a candidate classification, Hermes can take a swing. JOSH: So local models are worker bees. ERIK: Worker agents, yeah. Cheap brains near the files. [beat] ERIK: The mistake is asking, "Can this local model beat the best cloud model?" Wrong question. Ask, "Can this local model remove 40 tiny cloud calls from my day without doing damage?" JOSH: That changes the economics. ERIK: It does. It also changes architecture. [beat] ERIK: Once you have local agents, you can run more checks. You can have a model watch logs, scan configs, inspect diffs, read test output, and hand off only the weird stuff. That's where this gets useful. JOSH: Where do huge context windows fit? ERIK: Carefully. [beat] ERIK: Huge context is not magic memory. It's a bigger room to make a mess in. If you dump a whole repo, five logs, a Slack thread, and a Terraform plan into context, you may feel productive, but you might just be burying the signal. JOSH: That's very on brand. ERIK: It's true. Context engineering matters more as context windows get bigger. [beat] ERIK: Give the model the right files. Give it the failing test. Give it the current diff. Give it the rule. Then make it state what it thinks the task is before it acts. JOSH: That's the pro tip preview, isn't it? ERIK: Part of it. Agents should not be trusted because they sound confident. They should be trusted because the workflow forces them to show the right inputs. [beat] ERIK: ScanBrief is a good example. The system doesn't just grab a headline and vibe. It pulls sources, scores items, and makes the signal traceable enough that I can reject weak stuff. Same principle for code agents. JOSH: How should builders handle GLM-5.2 specifically? ERIK: Wait for repeatable runs. Check the license. Check memory needs. Check quantized accuracy on tasks you actually do. Run it against your logs, your tests, your docs. [beat] ERIK: Don't ask if it wins a leaderboard. Ask if it saves you time on Tuesday. [pause] JOSH: Polymarket. This one feels like a trust story, not just a crypto story. ERIK: Correct. Prediction markets sell credibility. That's the product. [beat] ERIK: The pitch is, "Markets know something." Prices become a signal. If the marketing around that signal is fake, you've poisoned the thing you're selling. JOSH: Reports said fake-looking wins, paid creators, and even spoofed-looking site content. How bad is that? ERIK: Bad. Not because creators got paid. Paid promotion is normal if it's disclosed and honest. The problem is making ads look like organic proof while showing outcomes that didn't happen. [beat] ERIK: If a video implies someone turned $1,000 into $100,000 on a bet that wasn't real, that's not edgy internet marketing. That's a compliance department hearing boss music. JOSH: And the deposits number was about $900,000? ERIK: That's what the reporting said. Roughly $900,000 in user deposits tied to the campaign. [beat] ERIK: That's the part operators should stare at. Bad incentives can move real money fast. Then the cleanup is slower, louder, and more expensive. JOSH: How does that compare to automated systems? ERIK: Same rule. If your system creates trust signals, you have to protect them. [beat] ERIK: Gandalf reviews code because a green merge badge should mean something. PrimeTrader reacts to TradingView webhooks because a trade signal should mean something. ScanBrief ranks news because a top story should mean something. JOSH: If those signals get noisy, people stop trusting the system. ERIK: Exactly. Trust is a cache. Hard to fill. Easy to invalidate. [beat] ERIK: Once users think the numbers are fake, you don't get to explain your way back quickly. You need audits, receipts, provenance, and boring controls. The boring stuff becomes the product. JOSH: That's not how founders like to talk. ERIK: Too bad. [beat] ERIK: If you're moving money, sending emails, merging code, or ranking information, you need evidence trails. Who generated it? What input did they use? What policy checked it? What got blocked? JOSH: That's the same architecture you use with PrimeBus. ERIK: Yeah. Events, review, action, audit. Every time. [beat] ERIK: When an agent proposes a patch, I want the failed test, the diff, the reason, and the reviewer result. When ScanBrief ranks a story, I want the source trail. When PrimeTrader sees a webhook, I want the condition that fired. JOSH: And for a prediction market? ERIK: Label paid creators. Ban fake results. Keep public ad archives. Make deposits traceable to campaigns. Build the audit before the regulator writes it for you. [beat] ERIK: Because they will write it. And they won't use your branding guide. JOSH: That's a rough line. ERIK: It's accurate. [pause] ERIK: This episode is sponsored by Prime Automation Solutions. If you're still doing it manually, we automate it. Also, special on a website — $250. primeautomationsolutions.com [pause] JOSH: Alright, what's the AI pro tip today? ERIK: Before an agent touches code, money, infrastructure, or outbound email, make it produce a context receipt. [beat] JOSH: Context receipt? ERIK: Simple format. "Task understood." "Files inspected." "Commands run." "Assumptions." "Risk level." "Next action." Then require the next action to match that receipt. [beat] ERIK: If the agent says it's fixing a Terraform variable but never opened the Terraform file, stop it. If it says it's changing an NSO service but didn't inspect the service package, stop it. If it wants to send email and can't quote the recipient and body, stop it hard. JOSH: That sounds obvious. ERIK: It is. That's why people skip it. [beat] ERIK: The receipt turns a chatty model into a controlled worker. You don't need a fancy framework. Add it to your prompt, enforce it in your script, and log it with the action. That's your tip. Use it. [pause] JOSH: We also drop daily market picks and automation tips on YouTube — search Build or Be Replaced. [pause] JOSH: One more thing — we started a Discord for builders. If you're shipping AI, automation, or anything that makes a human obsolete — come hang out. Link at buildorbereplaced.dev. ERIK: Post what you built. We'll post what we're building. Real wins, real builds, no fluff. [pause] ERIK: Build or be replaced. JOSH: If you want these signals in your inbox every morning, scanbrief.dev. See you tomorrow.