Madrigal's "Failures as Eval Suites" Pattern and How Flow Already Provides the InfrastructureA blog post on LangChain's site about how Madrigal Pharmaceuticals built their multi-agent AI platform caught my attention this week. Not because of the architecture — orchestrator routing, parallel aMay 6 · 8 min readblog.rynko.dev
How We Built a Three-Layer Code Review Pipeline with Rynko FlowWhen a customer asked me last week how to build an automated code review pipeline using Rynko Flow, my first instinct was to explain our business rules engine — expression-based rules that evaluate stApr 15 · 9 min readblog.rynko.dev
Extract Your Documents, Validate Against Your Data: Introducing Rynko Extract and Lookup Tables Until now, Rynko Flow assumed that agents would submit structured JSON for validation. And many do — when the data starts out structured. But a large number of real workflows start with a PDF, a scannApr 1 · 12 min readblog.rynko.dev
Microsoft's Agent Governance Toolkit and Where Rynko Flow Fits InMicrosoft just open-sourced the Agent Governance Toolkit, a runtime governance platform that covers all 10 risks in the OWASP Agentic Top 10. I've spent the morning reading through the architecture, b12IMar 22 · 9 min readblog.rynko.dev
IBM's $11 Billion Confluent Acquisition, AWS + Cerebras, and Where Output Validation Fits InTwo announcements in the same week paint a clear picture of where enterprise AI infrastructure is headed, and both of them are exciting. IBM closed its $11 billion acquisition of Confluent, the Kafka-Mar 18 · 8 min readblog.rynko.dev
