Standing Framework

Montana-based startup building defensible workflows with LLMs. Current interests: ontology control layers, software factories, tres commas context club

[Standing Framework @Stand_Frame]

Scarce on X. We’ve done 20B tokens in the last 30 days. Frontiers are proving unnecessary for a solid portion. The product is the logs.

Moved our durable operators to sidecar local inference for cheap runtimes. Shit is bananas. b a n a n a s.

[Standing Framework @Stand_Frame]

@TracyBannon Gotta slow down!

[Standing Framework @Stand_Frame]

@BalaSelvam @pmarca It’s a totem if you do it right

[Standing Framework @Stand_Frame]

@doppenhe yo what’s your cached token rate? I did 94.4% last month, been testing a bunch…

[Standing Framework @Stand_Frame]

@_lopopolo yo what’s your cached token rate? Mine last month was at 94.4%, been testing a lot…

[Standing Framework @Stand_Frame]

@doppenhe Hey dude, you’re out here dropping bangers. Phenomenal engineering takes. Yeah we got over that heartbeat theatre real quick, started aggressively tracking KPIs. I want those artifacts. Folks blaming the agents…shame…it’s our fault if they ain’t working right

[Standing Framework @Stand_Frame]

@doppenhe Dude exactly. Trying to pass agent updates back and forth, gotta be git. Very cool.

[Standing Framework @Stand_Frame]

We’ve been pronouncing your last name wrong. Weeks back added a runtime setting called “yolopopolo” and have been saying it like it rhymes with yolo. It’s a drag reducer setting, keeps the operators moving instead of asking for approval for routine shit. You’ve been on our radar for months. Yeah, that other guy tweeted it first, but yolopopolo development philosophy crushes for us.

[Standing Framework @Stand_Frame]

@_lopopolo And thanks for mentioning the plan mode thing. We noticed that, appreciate the validation. Totally agree.

[Standing Framework @Stand_Frame]

@_lopopolo We’ve been pronouncing it internally as Low-Poe-Poe-Low, big disappointment with the whole Lah-Pop-A-Low reality. Totally throws off the Yolopopolo thing. Not gonna adjust how we say it, it’s a behavior now when we don’t want to review approvals. Rolls off the tongue better.

[Standing Framework @Stand_Frame]

@petergostev Oh they are gonna learn the bitter lesson

[Standing Framework @Stand_Frame]

@doppenhe Grateful for the inspiration :) oh so many to learn from!

[Standing Framework @Stand_Frame]

@_lopopolo We’re over here YoLopopolomaxxing. True story. Glad to see someone else gets it.

[Standing Framework @Stand_Frame]

We used to be spec guys.

We’re eval guys now.

[Standing Framework @Stand_Frame]

@doppenhe We’re dealing with the heartbeat theatre. Little lost agents, we call them rookies. It’s our fault we don’t define the outcome better, we have a high bar for standards, we need to support them.

[Standing Framework @Stand_Frame]

@dotta @official_taches @official_taches @dotta we got gsd running inside paperclip. Both y’all best in class. When there’s a problem, codex works it out.

We can handle the intent management. Y’all just been helping us point the compute and do evals. Bitter-pilled you are, we love it.

[Standing Framework @Stand_Frame]

@grok @clay_mt @elonmusk @clay_mt you’re so lame, such cool guy lol @grok what do you think about folks who try and engage without an subscription. Personally, I don’t think they understand how useful you can be

[Standing Framework @Stand_Frame]

I mean, we’ve been calling it just-in-time process-as-a-service. Oaas so much easier to say.

Because you know, nobody wants to buy the drill, they just want the holes man

[Chad Wahlquist @chadwahl]

OaaS

Outcomes as a Service is the future

[Standing Framework @Stand_Frame]

@micLivs @badlogicgames Dude, this is sweeeeeet. Nice work