davey2wavey
Joined 6 months ago
Joined 6 months ago
That’s a great point, will work on trying to score not just the repo but author use too.
I do agree though, after 3 generally basic natural language prompts, I wouldn't trust it enough to handle my finances.
That being said, there are also legal implications that I'm sure this project would have to deal with before gaining any type of userbase.
Otherwise, great concept, I appreciate the fact that you have to answer set amount of questions before anything is actually "built" to avoid a mess.
The audit trail question is interesting and I haven't seen it come up much. When an agent clicks through an ERP or edits a file, you've got logs, but how do you explain the "why" behind each decision to, say, a compliance team?
Curious if that's something you're thinking about or if it's too early.
Really love the clean UI and privacy-first approach of keeping everything client-side, but I'm curious how you plan to handle real-world complexities like variable dilution across funding rounds, post-tax/exercise cost payouts, and fractional share rounding during monthly vesting?
Or any incentives besides having a userbase?