what happens when the semantic layer is uncertain or unavailable?
For payments, “LLM could not decide” is itself a policy case. Failing open is risky, failing closed may create too much friction and routing everything uncertain to HITL can become noisy fast.
I think the valuable part here is the audit trail behind it: why this spend was allowed, blocked or escalated.
The vast majority were downloaded. A few I got when I exchanged compilation DVDs with someone in Finland in 2006 and 2009 (I uploaded the images on those to BetaArchive back then and they've made their way onto various other sites). The only ones that I have that were installed from images I dumped from original media that hadn't been previously shared were LynxOS 4.0 and MaxOS Linux (not to be confused with macOS, it was an obscure early-2000s commercial Slackware fork from a company that was semi-local to me; the CD was given to me back then by somebody at a long-defunct local computer store).
top model changes every other month between Claude, GPT and gemini. but its dominated by GPT overall. Claude has taken lead in coding task but GPT 5.5 has come stronger. gemini was good in between. but its dominated by GPT 5.5 and claude overall. Coding is the area where disruption is hardest. Opencalw early this year was a major breakthrough in agentic AI and it is still making noise and becoming more mature and going toward enterprise. Agentic coding is still in adoption phase where teams are trying it , trying to make sense out of it, running it and not beleving it and eventually it is discussion point over tea. it is still in adoption phase but needle has moved from being alient to being something real which team started discussing and using it like a champ.
accurate memory estimation is key here. it will crash if that accurate and it cant be generic for all local llm. each local llm has different context estimates.
I think the valuable part here is the audit trail behind it: why this spend was allowed, blocked or escalated.