Don't worry. Someone will come along and run the same 1000 lines on a Docker container using ECS Fargate launched with Step Functions under the watchful eyes of Cloud Watch all glued up with Lambda and stick everything behind IAM roles and a parem store and charge 100x more...then it can fit your definition.
its not about the cost or complexity of the solution, its just about the info density.
```The result after running 20 parallel agents on this for ~2 days:```
That's basically saying 'yeah, me and my 20 coworkers figure everything out of your company'. There is just nothing innovative apart from hoping the AI to magically just work.
Hey, OP here!
I agree the idea here is pretty simple. The main insight is just allowing the agents to figure out the unfiltered truth about a company (the good, bad, and ugly). I tried many variations of this before but they all failed because it simply captured "intended process" instead of the ground truth.
Still have a lot of hard problems to figure out like how to maintain RBAC and scale this solution!
But you can't just hire one, you have to hire functional consultants (who tell you your flow is wrong and you have to adjust that to how SAP does things) and then implementation consultants who don't know how the process works, but can actually implement that integration. And then again after the next release because the integration broke.
And the customer being cheap doesn't pay for the proper modules and thus everything gets mapped to PSP elements -- to keep the same old garbage piles that get pushed around.
Yes, but they definitely have a vested interest in scaring people into buying their product to protect themselves from an attack. For instance, this attack requires 1) the victim to allow claude to access a folder with confidential information (which they explicitly tell you not to do), and 2) for the attacker to convince them to upload a random docx as a skills file in docx, which has the "prompt injection" as an invisible line. However, the prompt injection text becomes visible to the user when it is output to the chat in markdown. Also, the attacker has to use their own API key to exfiltrate the data, which would identify the attacker. In addition, it only works on an old version of Haiku. I guess prompt armour needs the sales, though.
Not quite, Polymarket is decentralized so they are even more removed from the outcome. When a dispute happens like this, a vote happens in the UMA DAO, essentially a decentralized "democratic" vote. What people are complaining about is UMA whales skewing votes.
Out of nowhere Cognition with a banging product. Probably not 100% yet but the idea is so good I'll be surprised if within 6 months all the other IDEs aren't copying.
reply