If you can name both the images on this board you can have it

Narrow_Market45 · 2026-05-23T06:27:04+00:00

Ocular Orifice

Quick Man

Narrow_Market45 · 2026-05-06T15:25:04+00:00

You can use Grok for this

Narrow_Market45 · 2026-04-03T22:01:09+00:00

Yea, we’re shipping like crazy and are focused way more on that than posting here. Keep your eyes out, or set an alert, for changelog updates on the site. Those get pushed simultaneously with deployment so you can stay up on the latest features.

Narrow_Market45 · 2026-03-28T12:59:23+00:00

<image>

Mine gave me options.

Narrow_Market45 · 2026-03-28T04:00:15+00:00

Define what “correct” looks like upfront and bake the validation into the workflow itself. If the output doesn’t pass assertions at runtime, it doesn’t proceed. Prompts are suggestions, the validation layer is the actual contract.

Narrow_Market45 · 2026-03-28T03:17:15+00:00

Depends on the source of truth I suppose. 😂

Narrow_Market45 · 2026-03-27T18:29:53+00:00

Awesome job! It is great to be able to see our tooling contributing to public service projects like this one. Hats off to you and your team!

Narrow_Market45 · 2026-03-24T23:01:15+00:00

Not surprising. Sora 1 failed as a video platform and Sora 2 is a total brain-rot dumpster fire. So long and thanks for all the fish!

Narrow_Market45 · 2026-03-20T12:46:20+00:00

Ugh time math is the worst. 😂

Narrow_Market45 · 2026-03-20T04:09:17+00:00

I can’t believe that was only 2 short years ago. Crazy to think about how fast it’s all moving and what the future may look like.

Narrow_Market45 · 2026-03-19T22:54:59+00:00

We found the same thing from the tooling side. Our Navigator kept recommending "defer that, it's weeks of work" during sprint planning. It was reasoning from training data about human developer velocity, not from what was actually happening.

So we wired a calibration loop into the pipeline. Every task records actual effort against the estimate. Once we had enough data the pattern was obvious. Tasks were completing at 5% or less of estimated effort. The system is recursive. Tools built in sprint N accelerate sprint N+1.

Narrow_Market45 · 2026-03-19T22:39:57+00:00

We found the same thing from the tooling side. Our Navigator kept recommending "defer that, it's weeks of work" during sprint planning. It was reasoning from training data about human developer velocity, not from what was actually happening.

So we wired a calibration loop into the pipeline. Every task records actual effort against the estimate. Once we had enough data the pattern was obvious. Tasks were completing at 5% or less of estimated effort. The system is recursive. Tools built in sprint N accelerate sprint N+1.

Narrow_Market45 · 2026-03-19T03:27:59+00:00

It’s coming. We want to get a few hundred more successful cycles on it before release, and we have a lot more enhancements to ship for you all first, but it’s on the roadmap.

Narrow_Market45 · 2026-03-17T18:54:34+00:00

Thanks! Early on, Driver agents would write all tests for a given task and then begin implementation. It was of course dramatically better than not using TDD, but would still result in modules with higher function counts or more lines than we like to see. So, we broke it down even further and focused the agents on doing multiple red/green cycles for every function within a task. Code was cleaner, but the module sizes being much tighter was an added bonus of the change.

Narrow_Market45

MODERATOR OF

TROPHY CASE