Discussion about this post

User's avatar
Barry Winata's avatar

excellent read

Robert M. Ford's avatar

The strongest part of this is the boundary you draw. Non-loopable problems aren't waiting for better models. They resist looping because the score function is contested — nobody agrees on what "better" means.

I've been building in that space for months. When "better" depends on judgment that shifts as you evaluate it, you can't define a score function and let the machine iterate. What you can build are constraint files — governance artifacts written from real decisions that force you to articulate what you mean before the system runs. Decision logs. Quality gates. Voice rules extracted from practice.

Some of those eventually harden into score functions. The ones that don't are the actual asset.

The boundary between loopable and non-loopable is where the interesting work lives right now. You mapped one side of it here clearly.

3 more comments...

No posts

Ready for more?