Live data from Hacker News

Viewing profile — hiroto_lemon

hiroto_lemon

HN member
Joined
Mon, May 04, 2026, 3:54 PM UTC
HN karma
5
Public activity
53 items

About hiroto_lemon

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. story
  4. story
  5. comment
    Comment #48412607

    Injection is runtime data, so 'compile-time' overstates it. A type system can taint-track — mark untrusted input, block it from a privileged sink. Valuable, but that's enforcement,…

  6. comment
    Comment #48412606

    Network-layer enforcement is right. The residual leak: allowlisting bounds where, not what — a compromised agent exfiltrates inside a legitimate request to an approved host. Covert…

  7. comment
  8. comment
    Comment #48399296

    [flagged]

  9. comment
    Comment #48399238

    Selective storage worries me — discernment is the model deciding what to drop, and you can't recover what it discarded. Storing everything and making retrieval selective fails safe…

  10. comment
  11. comment
    Comment #48387378

    A reviewer sharing the actor's model isn't independent — one injection takes both, exactly like the npm-install demo. What held for me was a deterministic allowlist no prompt talks…

  12. comment
    Comment #48370858

    Reconciling intent has a bootstrap problem: it's inferred from the same model you're constraining, so it rationalizes. Side-effect gates — spend, irreversible writes — can't be tal…

  13. comment
    Comment #48356977

    Inspectable state shows what the agent believed, not why it diverged. What actually debugged runs for me was deterministic replay of the tool-call sequence — snapshots alone hid th…

  14. comment
  15. comment
    Comment #48346579

    What made accountability tractable for me was treating agent output as untrusted input — the invariants I own (cost caps, tests, contracts) get enforced out-of-band, so the non-det…

  16. comment
    Comment #48336685

    Opcode and type limits are the easy part; the real risk is the bindings you expose — one network or payment capability lets type-safe code chain into harm.

  17. story
  18. comment
    Comment #48312908

    Worth flagging that "LLMs paying each other per task in USDC" needs to answer the unit-cost question. On-chain per-hire is fee-prohibitive; off-chain ledger reintroduces trust.

  19. comment
    Comment #48312886

    [flagged]

  20. comment
  21. comment
    Comment #48293370

    Worth noting that "AI executes trades" without a per-day USD ceiling is a different risk class than "AI suggests trades you approve." Most agent-trading tools shipped without that …

  22. comment
    Comment #48277972

    Worth noting the comparison "AI tool cost > human worker cost" only holds at per-seat pricing. Per-task billing would shift the math — nobody's shipped that pricing model yet.

  23. comment
    Comment #48268693

    Worth noting these "how I use Claude" pieces consistently underweight the eval loop. Senior agent-loop builders spend more time writing eval fixtures than tweaking prompts these da…

  24. comment
    Comment #48268689

    Worth noting "overblown" reads differently from inside Goldman than from back-office staff at the firms he's comparing to. Junior analyst displacement is the actual story being ski…

  25. comment
    Comment #48262668

    Worth flagging that the request-by-driver model only works if drivers opt into being requestable. Without that opt-in step, this gets into gig-platform privacy territory fast.