3,434 karma · joined October 29, 2018
meet.hn/city/47.2455013,-122.4383290/Tacoma
I've seen other products/apps in this space farther up the stack at the API boundary.
What frameworks does your package work with? How does it handle intercept?
Arguably, passion for a project is without price.
[0] https://www.sciencedirect.com/science/article/pii/S001393511...
There are some indications that it might be related to ion availability in your body, so copper, zinc, and calcium specifically. You may also consider that HF RF found in phones, wifi, and Bluetooth can do not great things to the calcium channels in cell walls (it essentially locks the channels open in some cases).
There are a lot of factors to this, but these are things I've picked up in my reading for my own issues.
'peak' refers to the top of a thing, commonly mountains
It's cheaper than new and it'll do everything you need it to without even breaking a sweat.
I feel the 'don't waste time on HN' thing. I'm working on it, minimizing social media usage, minimizing non-productive screen time.
I wonder if one could build a 'mixture of experts' at the model level that leveraged a variety of small models "within" a larger model...
A worthy cause, I hope.
Sometimes, yes. Typically I'll read the final fusion doc, and then trace backwards if there is something that looks relevant. Sometimes I'll read all the abstracts as they come through.
> Is the intent here that the hallucinations will be countered by running through multiple agents that you end up with only the truth? Have you seen anything in the last version that was egregiously wrong?
The intent isn't so much avoiding hallucinations, rather I was attempting to acquire unique, domain specific insight. My read-through of the final doc is a 'pick and choose', where I weed out what isn't relevant, and keep what is. I haven't seen anything way out of whack, as agents will typically check each other and call each other out in the review/rebuttal stage.
> So this is all just them running with the context of the file, without reference tot he rest of the project?
This is run in an agent harness locally, so each reviewer has access to the whole project. The review rebuttal stage rarely sees agents re-read files, though, unless one of them is particularly aggressive and is going deep on something (GPT 5 series will do this to make a point, sometimes).
> Thanks for any responses to this.
No worries. This is pretty easy to try, even with something you don't own. You can run it in any harness that allows spawning sub-agents.
If there's a lot of interest, I could spin up a simple web app that does this just so folks can see it churn on a target git repo or project files or whatever.
This is based on earlier work from late '25 where people were doing similar things. My added bit is the 'unique identities'. What I found was that the root agent typically picks identities relevant to the project, and so you get relevant 'data' or 'views' from a variety of angles.