THE AI PULSEMAY 22, 2026EN

The Pulse — May 22, 2026

The signals that entered our radar, organized with sources and context to understand what changed.

Analyze with my AI Send this Pulse on WhatsApp ↗Get the next edition

ModelsAgentsHardware

LISTEN TO THIS EDITION

The audio script is ready; narration will appear after voice generation finishes.

01Notion Blog / Releases
Notion’s Developer Platform (Workers + CLI + webhook triggers)
WHY IT ENTERED THE RADAR
Notion is turning into an “agent runtime”: you can deploy deterministic code (Workers) in Notion’s sandbox, sync external data sources into Notion DBs, and trigger workflows via inbound webhooks—without hosting your own infra. This is exactly the kind of glue layer creators will demo, but the upstream story is about hosted runtimes + governance for agents.
SUGGESTED EDITORIAL ANGLE
“Notion quietly became an agent platform: Workers are the missing piece between MCP and real production automations.” (Show 3 real use cases: nightly PDF→Notion ingestion, CRM sync, PR-merged webhook → task close.)
Open original source ↗
02Thinking Machines Labs blog
Thinking Machines Labs: “Interaction Models” research preview (micro-turn, multi-stream real-time)
WHY IT ENTERED THE RADAR
This is a concrete architectural pitch for “real-time interactivity scales with intelligence” via micro-turn multi-stream design and a split between an always-present interaction model + asynchronous background model for deep tool use.
SUGGESTED EDITORIAL ANGLE
“The next interface war isn’t agents vs chat—it’s turn-based vs continuous models.” Compare this with multi-stream LLM papers (below) and current realtime harnesses (VAD etc.).
Open original source ↗
03arXiv
Multi-Stream LLMs (parallel streams for thoughts / inputs / outputs) + code
WHY IT ENTERED THE RADAR
Argues that the “single chat stream” is the bottleneck and proposes training models for parallel streams, not just bolting harnesses on top. Claimed benefits: parallelization/efficiency, separation-of-concerns (security), monitorability.
SUGGESTED EDITORIAL ANGLE
“Why your agent can’t read while it writes—and the training fix.” Do a visual: 3 lanes (INPUT / THINK / OUTPUT) with causal dependency across timesteps.
Open original source ↗
04arXiv
CODA: rewrite Transformer blocks as GEMM+epilogue programs (cut memory-bound ops)
WHY IT ENTERED THE RADAR
Most training time is increasingly eaten by memory-bound “surrounding ops” (norm/activation/residual/reductions). CODA proposes a constrained kernel abstraction so these run while GEMM tiles are still on-chip (before writing to global memory).
SUGGESTED EDITORIAL ANGLE
“The next 2× training speedups won’t come from new GPUs—they’ll come from fusing the boring stuff.” Explain GEMM mainloop + epilogue primitives in plain language.
Open original source ↗
05OpenAI News
OpenAI: model disproves Erdős unit distance conjecture (AI math milestone)
WHY IT ENTERED THE RADAR
Claim: first time an AI autonomously resolved a prominent open problem central to a subfield (combinatorial/discrete geometry), using ideas from algebraic number theory. This is “AI as researcher” content with actual mathematical meat.
SUGGESTED EDITORIAL ANGLE
“This isn’t ‘AI solved math’ clickbait—the surprising part is the cross-field transfer: number theory machinery → Euclidean geometry.”
Open original source ↗
06Reddit (r/LocalLLaMA RSS) → upstream Qwen blog
LocalLLaMA: Qwen 3.7 hype + upstream announcement link (fetch failed)
WHY IT ENTERED THE RADAR
Open-weight releases are still the “internet accelerant” for agents and local workflows. Even without parsing details (site fetch didn’t extract the article body), the upstream link is where early specs/weights/licensing details typically appear.
SUGGESTED EDITORIAL ANGLE
“What to watch for in Qwen 3.7 (before the benchmarks): license, context length, tool-use format, and whether it ships good small checkpoints (4B–8B) for edge agents.”
Open original source ↗
07Reddit (r/MachineLearning RSS) → upstream NuExtract blog
NuExtract3: open-weight 4B VLM for OCR/Markdown/structured extraction (fetch failed)
WHY IT ENTERED THE RADAR
Document extraction is a huge “agents in the real world” bottleneck: invoices, screenshots, PDFs, tables. If this is genuinely self-hostable with good quantizations (as claimed in the Reddit post), it’s a practical alternative to paid OCR+LLM stacks.
SUGGESTED EDITORIAL ANGLE
“Your agent is only as good as its document ingestion.” Show a pipeline: PDF → images → NuExtract → JSON schema → agent action.
Open original source ↗
08YouTube RSS (Matt Wolfe / Y Combinator)
Creator-watch (new uploads) → use as “signals”, but go upstream
Open original source ↗

PROMPT.md

I want to analyze this edition of The RegusciLabs Pulse:
The Pulse — May 22, 2026
https://reguscilabs.com/en/blog/pulse/2026-05-22

SIGNALS
1. Notion’s Developer Platform (Workers + CLI + webhook triggers)
Source: Notion Blog / Releases
Original link: https://www.notion.com/blog/introducing-developer-platform
Why it matters: Notion is turning into an “agent runtime”: you can deploy deterministic code (Workers) in Notion’s sandbox, sync external data sources into Notion DBs, and trigger workflows via inbound webhooks—without hosting your own infra. This is exactly the kind of glue layer creators will demo, but the upstream story is about hosted runtimes + governance for agents.
Editorial context: “Notion quietly became an agent platform: Workers are the missing piece between MCP and real production automations.” (Show 3 real use cases: nightly PDF→Notion ingestion, CRM sync, PR-merged webhook → task close.)

2. Thinking Machines Labs: “Interaction Models” research preview (micro-turn, multi-stream real-time)
Source: Thinking Machines Labs blog
Original link: https://thinkingmachines.ai/blog/interaction-models/
Why it matters: This is a concrete architectural pitch for “real-time interactivity scales with intelligence” via micro-turn multi-stream design and a split between an always-present interaction model + asynchronous background model for deep tool use.
Editorial context: “The next interface war isn’t agents vs chat—it’s turn-based vs continuous models.” Compare this with multi-stream LLM papers (below) and current realtime harnesses (VAD etc.).

3. Multi-Stream LLMs (parallel streams for thoughts / inputs / outputs) + code
Source: arXiv
Original link: https://arxiv.org/abs/2605.12460
Why it matters: Argues that the “single chat stream” is the bottleneck and proposes training models for parallel streams, not just bolting harnesses on top. Claimed benefits: parallelization/efficiency, separation-of-concerns (security), monitorability.
Editorial context: “Why your agent can’t read while it writes—and the training fix.” Do a visual: 3 lanes (INPUT / THINK / OUTPUT) with causal dependency across timesteps.

4. CODA: rewrite Transformer blocks as GEMM+epilogue programs (cut memory-bound ops)
Source: arXiv
Original link: https://arxiv.org/abs/2605.19269
Why it matters: Most training time is increasingly eaten by memory-bound “surrounding ops” (norm/activation/residual/reductions). CODA proposes a constrained kernel abstraction so these run while GEMM tiles are still on-chip (before writing to global memory).
Editorial context: “The next 2× training speedups won’t come from new GPUs—they’ll come from fusing the boring stuff.” Explain GEMM mainloop + epilogue primitives in plain language.

5. OpenAI: model disproves Erdős unit distance conjecture (AI math milestone)
Source: OpenAI News
Original link: https://openai.com/index/model-disproves-discrete-geometry-conjecture/
Why it matters: Claim: first time an AI autonomously resolved a prominent open problem central to a subfield (combinatorial/discrete geometry), using ideas from algebraic number theory. This is “AI as researcher” content with actual mathematical meat.
Editorial context: “This isn’t ‘AI solved math’ clickbait—the surprising part is the cross-field transfer: number theory machinery → Euclidean geometry.”

6. LocalLLaMA: Qwen 3.7 hype + upstream announcement link (fetch failed)
Source: Reddit (r/LocalLLaMA RSS) → upstream Qwen blog
Original link: https://www.reddit.com/r/LocalLLaMA/comments/1tjvz6l/waiting_for_qwen_37_open_weight_the_new_king_has/
Why it matters: Open-weight releases are still the “internet accelerant” for agents and local workflows. Even without parsing details (site fetch didn’t extract the article body), the upstream link is where early specs/weights/licensing details typically appear.
Editorial context: “What to watch for in Qwen 3.7 (before the benchmarks): license, context length, tool-use format, and whether it ships good small checkpoints (4B–8B) for edge agents.”

7. NuExtract3: open-weight 4B VLM for OCR/Markdown/structured extraction (fetch failed)
Source: Reddit (r/MachineLearning RSS) → upstream NuExtract blog
Original link: https://www.reddit.com/r/MachineLearning/comments/1tkejqr/nuextract3_released_openweight_4b_vlm_for/
Why it matters: Document extraction is a huge “agents in the real world” bottleneck: invoices, screenshots, PDFs, tables. If this is genuinely self-hostable with good quantizations (as claimed in the Reddit post), it’s a practical alternative to paid OCR+LLM stacks.
Editorial context: “Your agent is only as good as its document ingestion.” Show a pipeline: PDF → images → NuExtract → JSON schema → agent action.

8. Creator-watch (new uploads) → use as “signals”, but go upstream
Source: YouTube RSS (Matt Wolfe / Y Combinator)
Original link: https://www.youtube.com/shorts/E6kQi65PKNc

Help me:
1. Summarize the three most relevant signals.
2. Separate verified facts, provider claims, and editorial inferences.
3. Explain what could change for my company, team, or role.
4. Suggest three concrete actions and one question we should investigate.
5. Cite the original sources and flag any uncertainty.

Before answering, ask about my role, industry, and objective so you can tailor the analysis.

Notion’s Developer Platform (Workers + CLI + webhook triggers)

Thinking Machines Labs: “Interaction Models” research preview (micro-turn, multi-stream real-time)

Multi-Stream LLMs (parallel streams for thoughts / inputs / outputs) + code

CODA: rewrite Transformer blocks as GEMM+epilogue programs (cut memory-bound ops)

OpenAI: model disproves Erdős unit distance conjecture (AI math milestone)

LocalLLaMA: Qwen 3.7 hype + upstream announcement link (fetch failed)

NuExtract3: open-weight 4B VLM for OCR/Markdown/structured extraction (fetch failed)

Creator-watch (new uploads) → use as “signals”, but go upstream

Continue the analysis where you already work.