Posted by david927 2 days ago
Ask HN: What are you working on? (September 2026)
I created https://getnoloop.com to block the feed on iOS
The systems engineering V-model provides us with a general-purpose approach to solving difficult problems. It comes with an array of proven and trusted standards and document-oriented processes.
Given the number and detail of these documents and processes, automating some realisation of V-model is almost trivial. Tools like Codex and Claude Code are hardly less reliable and trustworthy than human engineers, and the existing standards already contain ways of mitigating the impact of imperfect work performed by error-prone agents.
The generality of this "Autonomous Systems Engineer" gives it a genuine claim to be something approaching AGI. Certainly it enables us to tackle much bigger and more challenging problems than we could with only the LLMs on their own. (Yes, it's "just another harness-of-harnesses", but that doesn't mean that what it can do isn't significant).
In addition to providing automation of high-integrity engineering practices, my project also provides a disciplined communication layer that sits on top of A2A or other similar protocols, enabling small agent-first engineering organisations to exchange well-defined highly-assured documents and accelerate b2b collaboration - enabling "swarms" of small, agile businesses to take on larger and more demanding challenges than they would be able to individually.
The basic idea is that ticket (or chat) based workflows loose tons of context over time. During periods of rapid iteration, even the tickets themselves can’t always keep up with changes in the requirements. Goalpost projects are lightly structured documents. Due to that structure, it can easily give you a view of what changed in any particular update, or you can search or browse the overall up to date spec if you are just looking to get context on something.
There are some nice quality of life features. Changes live in batches which can (optionally) be subjected to customizable approval rules. Email notifications to stakeholders when requirements change. The ability to move changes to different batches, pre-approval.
Still WIP, but I’d love any feedback!
This was an interesting thought experiment for me, because I always loved reverse-engineering old games (Half-Life in particular) and restoring the original looks and properties of the code.
In this project I tried to use LLMs extensively to reverse the code for the first time to bring it back to its original potential look. Frankly, it worked and the code is now available to the public.
If there's a tool you'd like to see there, let me know and I'll add it.