Viewing profile — amabito
amabito
HN member- Joined
- Mon, Feb 16, 2026, 8:10 AM UTC
- HN karma
- 7
- Public activity
- 19 items
- HN profile
- View on Hacker News ↗
About amabito
No profile information was provided.
Recent public activity
-
comment
Comment #47106982
IOPB bit semantics are inverted from what you might expect: 0 means permitted, 1 means denied. So zeroed pcb memory silently grants access to every port in range -- that's why this…
-
comment
Comment #47106846
Vulkan's presentation API makes this distinction explicit: VK_PRESENT_MODE_MAILBOX_KHR is the "replace if already queued" mode that actually reduces latency, while VK_PRESENT_MODE_…
-
comment
Comment #47099945
The tooling gap exists partly because git's data model has no native concept of "this branch's upstream is another feature branch" — each PR is independent from the forge's perspec…
-
comment
Comment #47088057
One thing that often gets overlooked in this comparison is how behavior trees degrade under retry or partial failure scenarios. State machines make failure transitions explicit, bu…
-
story
Ask HN: How do you prevent retry cascades in LLM systems?
We ran into a retry amplification issue in one of our LLM agents recently. The provider returned 429s for a short period. We had per-call retry limits in place. We did NOT have con…
-
comment
Comment #47087278
One thing I find fascinating about epoll/kqueue is how much modern async frameworks abstract away the underlying readiness model. A lot of people talk about “async performance” wit…
-
comment
Comment #47074586
Most orchestrators aren’t “bad”. They just assume LLM calls behave like deterministic RPC. The real issue is that we’re embedding stochastic, cost-weighted calls inside recursive g…
-
comment
Comment #47074405
That’s actually a pretty disciplined setup. What you’ve described sounds a lot like layered containment: Loop budget (hard recursion bound) Progressive checks (soft convergence con…
-
comment
Comment #47074297
This is interesting. It looks less like a “model failure” and more like a containment failure. When agents audit themselves, you’re effectively running recursive evaluation without…
-
comment
Comment #47072789
Right — search engines have long had authority scoring, link graphs, freshness signals, etc. The interesting gap is that retrieval systems used in LLM pipelines often don't inherit…
-
comment
Comment #47072694
What’s interesting here is that the model isn’t really “lying” — it’s just amplifying whatever retrieval hands it. Most RAG pipelines retrieve and concatenate, but they don’t ask “…
-
comment
Comment #47072689
Approval gates make a lot of sense, especially for high-impact actions. Most agent failures I've seen come from nothing stopping execution at all. One scenario I'm curious about: h…
-
comment
Comment #47072681
The Markdown-over-database choice makes sense for document-shaped output. The harder problem seems to be concurrent semantic edits. Git-style merging works for code because conflic…
-
comment
Comment #47072678
Nice reference. If agents are essentially “a while loop with an LLM call,” then one missing category might be execution control. In distributed systems we rarely let loops run unbo…
-
comment
Comment #47046889
Here’s a raw 75s demo of a runaway loop being halted: https://youtu.be/LaZOGj3EO_0
-
comment
Comment #47046792
Context: This isn’t another observability tool. It enforces: - hard budget stops - retry containment - circuit breaking The goal is simple: the $12K weekend never happens.
- story
-
comment
Comment #47032344
[dead]
-
story
Ask HN: Do LLM agents need a separate safety layer?
LLM agents are good at deciding. They are bad at knowing when to stop. VERONICA is a failsafe state machine that sits between strategy engines and external systems. It provides: - …