MurphyA/hacker-news huggingface dataset:
by zippolyon | 2026-03-11 13:52:56+00:00
The dashcam analogy is sharp. I'd extend it: most tools record what happened (tool X was called, output was Y), but not why the agent deviated from the plan. That's the gap that actually hurts during post-mortems.
In my experience, the useful question isn't "what did the agent do?" — it's "at step T, the agent's stated intent was Z, but it executed W instead. Was that a model drift, a context window issue, or a tool failure?" Without causal structure in the log, you're left correlating timestamps and guessing.
The DataTalks/Replit incidents both had this signature: the deviation was visible in hindsight from the logs, but no system caught the intent-execution gap in real time.
by sylwester | 2026-03-11 13:53:08+00:00
I’ve been working on a development environment for experimenting with DSP algorithms for synthesizers and audio effects.

The project is called dsplab. It’s a browser-based DSP lab built around the Vult language. The idea is to prototype oscillators, filters, envelopes, and other audio algorithms without having to build a plugin or embedded firmware project first.

You write DSP code in Vult and run it in an isolated AudioWorklet engine. The environment includes a set of tools for inspecting signals and internal state while the algorithm is running.

Currently it includes things like:

* dual-trace oscilloscope

* logarithmic spectrum analyzer

* logic analyzer for inspecting internal variables

* telemetry viewer for real-time parameter data

* signal generators and a small sequencer for testing patches

There is also an integrated LLM agent that can work on the DSP code. It can read compiler errors, write or modify functions, fix broken code, and iterate on implementations while observing telemetry and spectrum data from the running algorithm. The idea is that it can autonomously try improvements or fixes until the code compiles and behaves as expected.

The main goal is to use this as a sandbox for DSP ideas before moving them into hardware projects.

When an algorithm is finished it can be exported as C++ suitable for embedded targets such as Teensy, Daisy, or custom audio hardware.

Still evolving, but I’d be interested in feedback from people working on synths, plugins, or embedded audio DSP.
by ivan_gammel | 2026-03-11 13:53:14+00:00
I don’t think you understand it, if you cannot connect the dots. And of course “survival for reproduction” is oversimplification of what’s actually happening. Chances for survival to reproduce of some individuals are greatly influenced by survival of their relatives in the same group. The traits that help whole group to survive will win in natural selection, including those that extend survival beyond what’s necessary to reproduce to what’s beneficial for the group.
by _juli_ | 2026-03-11 13:53:21+00:00
I built skillfile, a declarative CLI tool for managing AI skills and agents (Claude Code, Gemini CLI, Codex, etc.) from multiple sources (GitHub, raw URLs, local files). Inspired by the same way I managed all the dotfiles. Think of it like a Brewfile / package manager for AI tooling - one manifest file (Skillfile) that:

* tracks what skills/agents you’ve installed
* pins to exact commits for reproducibility
* deploys into the directories your tools expect
* lets you pin local edits as patches so your customisations survive upstream updates (three way merge if necessary), so your modifications are also tracked too!

No more copy‑pasting URLs, running random one‑liners, several plugins from different hubs, or manually syncing. Just skillfile install, skillfile pin, and your AI toolchain stays organised.

It works across multiple platforms (Claude Code, Gemini CLI, Codex) and already has its first stable release. Would love feedback and contributions!

PS: a note on security:

Skillfile is a file manager. It downloads content from sources you specify and places it where your AI tools expect it. It does not analyze, verify, or sandbox the content it manages. review what you install. Risk profile is analogous to `git clone`.
by zippolyon | 2026-03-11 13:53:48+00:00
The topology graph and time-travel replay are genuinely useful additions — most tools in this space flatten agent runs into a linear trace, losing the branching structure entirely.
One thing I'd be curious about: how does AgentLens handle the difference between an agent that failed to execute vs one that executed but drifted from its stated goal? Execution traces capture the former well. The latter requires knowing what the agent intended before the tool call happened — which means you need to log the pre-action intent state, not just the post-action result.
This matters most for debugging silent failures — cases where all tool calls succeed and costs look normal, but the agent quietly pursued the wrong sub-goal.
by tptacek | 2026-03-11 13:53:57+00:00
No, Delaware does not in fact require corporations to "maximize shareholder value". That simply isn't a real thing.

"Fiduciary duty" is a duty to operate in good faith, without self-dealing, in whatever (1) you believe to be (2) the best interests of the company. Both (1) and (2) are totally subjective. You can believe the best interests of your company reside with employee welfare, or with customer satisfaction. You will not find a Delaware case that says otherwise.

So far as I know, the only time the actual value of a company's equity comes into the picture is if there are multiple competing offers to acquire the company.
by zippolyon | 2026-03-11 13:54:10+00:00
The IAM framing is a good starting point but I think it undersells the core difficulty: IAM assumes the identity of the actor is stable and legible. With agents, the "actor" at step 15 of a multi-step run may have meaningfully different context and effective goals than at step 1 — same session, different behavior.
Policy enforcement at runtime has to grapple with this. A rule like "don't write to production DBs" is easy. A rule like "don't proceed if your current action contradicts the intent you stated 3 steps ago" requires the agent to have exposed its intent in a queryable form throughout the run — which most don't.
Auditability is the easier problem. Runtime intervention based on goal drift is where I think the field is genuinely unsolved.
by Thorrez | 2026-03-11 13:54:46+00:00
>The frequently cited "0.002mm tolerance" is misleading without context. LEGO's actual mold precision is 10 microns, but different features have different critical tolerances.

The article never mentions what piece has a 0.002mm tolerance. Is there any such piece? If there's no such piece, then "0.002mm tolerance" is not just "misleading without context", it's straight up false.
by g947o | 2026-03-11 13:54:50+00:00
The parent comment does not appear to be supportive of what's happening regarding Roblox ("mindless").

If they are not interested in making the situation any different, but just want to vent, I think it's a waste of everybody's time.

> antagonize people

You can potentially antagonize anyone in any situation on an online forum even with the nicest words. I don't see how it matters. If the person is not receptive, I couldn't care less.
by jacquesm | 2026-03-11 13:54:53+00:00
This is not an abstract argument, you are showing a willingness to do the wrong thing in spite of being told not to, repeatedly, by many other participants here. I see only two things here:

(1) you would lie

(2) you fundamentally don't understand the concept of consent

The fact that other people would lie is besides the point: those other people would get the exact same treatment if found out. Whether or not they would be found out is moot, it is the act of lying and ignoring consent that makes this what it is: asshole behavior. By extension anybody that practices this behavior is an asshole as well and by extension of that tying your own rep to people that would behave like that makes you an asshole and I highly doubt that that was your intention.

So now you've - over endless comments - shown that you fundamentally don't get this very important concept. Yes, people lie. But there are mechanisms for dealing with liars. Misrepresentation and fraud are serious things. Lawsuits, fines and in an extreme case jail, but on a more immediate level ostracizing. It makes you as a person into an undesirable. It also makes the world as a whole a worse place to live in, which is why such behavior is strongly discouraged, even if it is possible.

That's why we don't structurally go around clubbing old ladies over the head as a revenue model, not because we can't do it or because it would be acted upon by the law (that's for the few who don't get it) but because it is simply a bad thing to do. It is a matter of ethics. That's why if an open source project has a 'No AI' policy you either abide by the policy or you can expect massive backlash.

To think that you could do this and even should do this to make the point is as stupid as walking out and grabbing some old lady's hand bag to prove that it can be done: you are hurting an innocent to prove your point and it will cause a reaction that is at a minimum proportional to what you did and worst case you will be made an example of. This can be the proverbial career ending move. If you are Elon level rich and your inner asshole seeks a way out then yes, you could probably do it. But for normal folks such behavior is highly discouraged. Actions usually have consequences.

Finally: open source is a massive gift to society. The whole reason you can use AI in the first place is because that gift got abused in a way that open source contributors did not anticipate. If you're going around to pollute open source with AI contributions to effectively karma farm you have to wonder why you are so intent on doing that. Is it your purpose to destroy open source? Or is it just because you enjoy destroying stuff in general? I don't see any other options, this is a pathology and it would do you good to introspect on this for a bit instead of to respond with yet another ill conceived reply digging yourself in further. You've gone from 'mildly annoying' to 'wouldn't work with this person for any amount of money because they are a liability' in the space of 15 comments. I hope it was worth it to you.
by PowMan | 2026-03-11 13:54:57+00:00
I built this because I kept seeing the same problem: customs brokerage and trade compliance software teams maintaining scrapers against USITC or downloading CSV dumps manually — then scrambling every time the tariff schedule changed.
The US HTS schedule has 32,295 records. Canada's Customs Tariff has 22,461. Both are updated on an ongoing basis from official sources (USITC REST API and CBSA releases). With Section 232 actions accelerating and US-Canada tariffs actively moving right now, "we'll update it next sprint" is no longer an option for teams whose customers care about duty rates.
TradeFacts ingests both schedules nightly, diffs every record, and serves it as clean JSON. Three endpoints: lookup by code, keyword search, and changes since last update. Auth is one header. No scraping, no schema surprises.
$199/mo. 30-day free trial, no credit card. Happy to answer questions about the data pipeline or the USITC API quirks — there are a few.
by garrickhgan | 2026-03-11 13:55:01+00:00
I started this because I wanted to push structured swim workouts from my training platform to my goggles without paying for another subscription. Ended up spending an afternoon decompiling the APK, running mitmproxy, and mapping the full BLE GATT profile.
The protocol uses custom protobuf schemas over BLE with MITM-protected pairing — the goggles display a 6-digit passkey on the HUD during bonding. Sync is a chunked file transfer with CRC validation.
Full protocol documentation is in PROTOCOL.md in the repo. Happy to answer questions about the RE process.
by GorbachevyChase | 2026-03-11 13:55:07+00:00
The most benign answer would be that they don’t want to further support an emerging competitor to OpenAI, which they have significant business ties to. I think the more likely answer which you hinted at is that the utility of the model falls apart as scale increases. They see the approach as a dead end so they are throwing the scraps out to the stray dogs.
by wholinator2 | 2026-03-11 13:55:08+00:00
Yes, i was thinking just this. Having been prescribed multiple immunocompromisers, turning up my immune system sounds terrifying. There's all these supplements and things that talk about boosting your immune system and i get probably most are unrelated, i don't have the time to get a degree in immunology to find out. Zinc does well enough for me, thanks. But if any immune boost started to increase my tnf-alpha or il-23 i'd be on the long and painful road to a terrible death. Or yet another high side effect medication.
Show HN: MIDI Visualizer
by decompiled_dev | 2026-03-11 13:55:19+00:00
I wanted to make a music visualizer that would show all of the notes and show what chord is playing. To make the analysis easier and accurate I stuck to MIDI only input.

The main presets are:
- Warp: A kaleidoscopic view
- Stars: Shows the notes spiral away
- Clock: Reveals the music analysis mechanisms
- Piano: The standard MIDI visualizer view

The menu allows for the compositor layers to be mixed and matched so you can explore and experiment. I'd recommend trying the "Feedback" and "CRT" overlays first.

I used Claude Code to generate all of the code, but it still took quite a bit of time to get it to look the way it does.

I wrote a post reflecting on my experience building it as well: https://decompiled.dev/blog/fractured-jukebox/
by dmos62 | 2026-03-11 13:55:25+00:00
You should care how much maths and encryption you use [0][1], because this is not only possible, but there are multiple approaches.

[0] https://satoss.uni.lu/members/jun/papers/CSR13.pdf

[1] https://fc16.ifca.ai/voting/papers/ABBT16.pdf
by zesterer | 2026-03-11 13:55:49+00:00
A thing that shocked me as I was working on the text editor was how capable modern terminal emulators are when you account for ANSI extensions. First-class clipboard access, mouse events, precise text styling, focus tracking, system notifications, key press/release events, etc. are all possible with a modern terminal emulator. There's not really anything else you need to build a very competent, ergonomic editor UI.

You can even use tools like trolley to wrap the entire application up in a ghostty-powered shim that presents the application as a native UI application: https://github.com/weedonandscott/trolley
by freedomben | 2026-03-11 13:56:11+00:00
> Please don't make excuses for literal evil pdophile megacorporations.*

I hate Roblox with the fiery passion of a thousand burning suns, and wish they and their business model to be utterly destroyed.

But allowing our emotions to override our objectivity is not the solution. It's important to be as fair and objective as possible if we want our arguments to be taken seriously.
by MarsIronPI | 2026-03-11 13:56:13+00:00
Anecdote here: I was given a computer at age 4, and I didn't really have any limits on how long I could use it. On the other hand, I wasn't allowed to register any accounts and I had to ask before visiting sites I had never been to before. >75% of my time on the computer at that age was spent on hacking with Scratch. I learned a lot and developed my love of computers at that age. I'm absolutely glad that I didn't have "screen time", but I can also see that if I didn't have the limits I did I could have ended up pretty badly.
by MattConfluence | 2026-03-11 13:56:17+00:00
> There is a theory which states that if ever anyone discovers exactly what U+237C is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.

-- Paraphrased from The Restaurant at the End of the Universe by Douglas Adams
by ivanjermakov | 2026-03-11 13:56:23+00:00
I went the same path of writing a text editor from scratch. There are a lot of moving parts, so I tried to outsource as much features as possible - LSP for intellisense, tree-sitter for highlighting and syntax-aware features, fzf for search and file handling, etc. I also tried to design it so that it can be tweaked to one's needs with simple code changes, suckless-style.

It was indeed a pain using it for the first few weeks, where every 5 minutes I found some bug and had to go back and fix it, instead of steadily working on some other project. Good news is more bugs you fix, less bugs is left.

https://github.com/ivanjermakov/hat
by fluffet | 2026-03-11 13:56:53+00:00
It's kind of bespoke for me tbh.

For a co-pilot inside an app that could answer product questions, I looked at ~2000 or so support emails. I asked one LLM to dig out "How would you formulate the users question into a chatbot-like question from this email thread" and "What is the actual answer that should be in the response from this email thread", then just asked our bot that question, and have another LLM rate the answer like SUPERIOR | ACCEPTABLE | UNKNOWN etc. These labels proved out to be a good "finger in the wind"-indicator for altering the chunks, prompt changes or model updates.

For an invoice procesing app processing about 14M invoices/year, it was mostly doing fuzzy accuracy metrics against a pretty ok annotated dataset and iterating the prompt based on diffs for a long time. Once you had that dataset you could alter things and see what broke.

Currently, I work on an app with a pretty sophisicated prompt chain flow. Depending on bugs etc we kind of do tests against _behaviour_, like intent recognition or the correct sql filters. As long as the baseline is working with the correct behaviour, whatever model is powering it is not so important. For the final output, it's humans. But we know immediately if some model or prompt change broke some particular intent.
by brohee | 2026-03-11 13:57:23+00:00
Sorry, the manufacturing learning curve. The most widgets you make, the cheapest they get. The effect was absolutely stunning for batteries and solar panels (https://ourworldindata.org/grapher/price-of-lithium-ion-batt...).

We make too few nuclear power plants for them to have a noticeable learning curve, and recently each subsequent one ends up more expensive than the latest, notably because of safety regulation. Korea and I think China had the best success in that regard (and France in the 80s) by being able to make real series, but you don't really see those now except maybe China.

More here: https://ourworldindata.org/learning-curve
by friendlymatthew | 2026-03-11 13:57:23+00:00
Hi, I wrote a snapshotable wasm interpreter. You can pause a running wasm program mid-execution, serialize its entire state, and resume it exactly where it left off

There's a demo running Conway's game of life. You can snapshot the simulation mid-tick, fork it into a new process, and watch both diverge from the same state!
Show HN: AgentSign – Open-source zero trust engine for AI agents
by AskCarX | 2026-03-11 13:57:42+00:00
Hi HN. This week Meta acquired Moltbook (agent social network), OpenAI acquired Promptfoo (agent testing), and Mandiant's founder raised $190M for Armadin. Agent infrastructure is clearly where things are heading.

We built AgentSign -- a zero trust engine for AI agents. The problem: agents are operating without any identity infrastructure. Moltbook went viral for fake posts because there was zero verification on who or what was posting.

AgentSign gives every agent a cryptographic identity certificate, signs every action into an execution chain, and runs runtime code attestation before anything executes. There's also an MCP Trust Layer for agent-to-MCP server verification, and a Stripe-powered Trust Gate for agent payments.

5 subsystems: identity certs, execution chain verification, runtime code attestation, output tamper detection, and cryptographic trust scoring.

Free and open source. Built in London.

SDK: https://github.com/razashariff/agentsign-sdk

Happy to answer questions.
by rrr_oh_man | 2026-03-11 13:58:08+00:00
> it's one of the areas where LEGO is generally superior to the similar types of bricks

Imho, this is, objectively, not true (anymore).

Pantasy with GoBricks are superior in coloring and fit; Cobi are excellent for things that should not be taken apart anymore (like tank models); Lumibricks are excellent in fit and have amazing illumination solutions that are lightyears (haha) ahead of lego.
by zozbot234 | 2026-03-11 13:58:19+00:00
> Let’s say AI comes along and forces 25% of the white collar workers out of a job

Yeah, this is not going to happen. New job positions will open up instead, and white collar workers will be well placed to fill them since supervising an AI agent swarm is not that different from supervising the work of other humans - which is what white collar workers do as their job.
by cardanome | 2026-03-11 13:58:39+00:00
The problem is that with generative AI, I have no means of protecting my work from being stolen.

It does not matter what license I put up. It doesn't even matter if I make it publicly available or not. LLMs have been trained on pirated material, they don't even have the decency to buy a copy. Even if I show my project to no one and just have a private repo of Github the code might still be used to train LLMs.

Your GPL licensed library? Yeah, we used claude to rewrite it and released it under MIT.

Now that wouldn't be so bad. One could argue copyright has long held back progress in certain areas. The problem is, the rules only apply one way. The rent seeking oligarchs of the tech industry can steal everything but I can't.

They can just eat the cost of a lawsuit, I can't. They can just decide to make a special deal with Disney to use their copyrighted material, I can't.

Sure the days of free markets capitalism are long gone. A few monopolists controlling the market has long been the norm. But AI makes it even worse. So much worse.
by Joker_vD | 2026-03-11 13:58:53+00:00
> This is primarily because core is primarily a teaching ISA.

That doesn't necessarily make it all that great for industrial use, does it?

> One of the best parts about RiscV is that you can teach a freshman level architecture class or a senior level chip building project with an ISA that is actually used.

You can also do that with Intel MCS-51 (aka 8051) or even i960. And again, having an ISA easily implementable "on a knee" by a fresh graduate doesn't says anything about its other technical merits other than being "easily implementable (when done in the most primitive way possible)".
by rwmj | 2026-03-11 13:59:58+00:00
FWIW I wrote this article a while back all about RISC-V extensions and how they work at a low level: https://research.redhat.com/blog/article/risc-v-extensions-w... page 22 in this PDF: https://research.redhat.com/wp-content/uploads/2023/12/RHRQ_...
by butILoveLife | 2026-03-11 14:00:44+00:00
After working in automotive, this is less impressive than it appears.

Tons of dimensions on 100k/yr injection molded(and otherwise) parts have similar dimensions. (Although admittedly, after testing in pre-production, I don't know if they are tested again and have drift)

Lego has been making the same parts for decades and their parts are extremely simple. I imagine their 1-off parts for intellectual property based sets do not have this requirement.

I think Lego has a huge incentive to promote this idea that they are high quality to justify the enormous price of decades old technology.
by lqet | 2026-03-11 14:00:45+00:00
> A 2x4 LEGO brick manufactured in 1958 will snap perfectly onto a brick molded this morning in Denmark, China, Hungary, Mexico, or the Czech Republic.

In the late 90ies, I regularly played with my uncle's old LEGOs from the 60ies and 70ies. They were stored in an unheated attic for 25 years. I remember that some of the old bricks didn't snap at all anymore to my newer bricks.