Madrigal's "Failures as Eval Suites" Pattern and How Flow Already Provides the InfrastructureMadrigal Pharmaceuticals turned production failures into their evaluation pipeline. They built this custom on LangSmith. Flow gives you the same feedback loop as infrastructure.8 min read·blog.rynko.devMay 6
How We Built a Three-Layer Code Review Pipeline with Rynko FlowYour ESLint config catches 200 rule violations. Your tests pass. Coverage is above 80%. And the PR still has a function that does four things, catches generic errors, and string-concatenates a SQL query. Rules caught the mechanics. Nobody caught the architecture.9 min read·blog.rynko.devApr 15
Extract Your Documents, Validate Against Your Data: Introducing Rynko Extract and Lookup Tables An AI agent receives a trade document. It needs to extract the HS codes, verify them against the Harmonized Tariff Schedule, check the vendor against an approved list, and flag anything that doesn't match. Before today, that was three systems and a lot of glue code. Now it's one pipeline with one API call.12 min read·blog.rynko.devApr 1
Microsoft's Agent Governance Toolkit and Where Rynko Flow Fits InMicrosoft open-sourced a runtime governance platform for AI agents. It's the most comprehensive behavioral governance framework I've seen. Here's how Flow complements it by adding output validation to the pipeline.9 min read·blog.rynko.dev12IMar 22
IBM's $11 Billion Confluent Acquisition, AWS + Cerebras, and Where Output Validation Fits InIBM is solving real-time data for agents. AWS is solving inference speed. Both are foundational. Here's how Rynko Flow adds an output validation layer to complement what they're building.8 min read·blog.rynko.devMar 18