Hacker Newsnew | past | comments | ask | show | jobs | submit | wferrell's commentslogin

You might try Decisionlayer.ai

We built a way to make contracts enforceable and resolve disputes without the high cost of litigation. Specifically, by adding our arbitration clause to your contracts or using our "case by consent" you can get AI driven court-enforceable arbitration decisions in 7 days for a $500 flat fee - no lawyers required. This compares to the $30k or $40k you would otherwise spend on a lawyer+ JAMS/AAA arbitration fees. For your HOA, I suspect the case by consent would be the best approach - two parties come to the website, both agree to use DecisionLayer to resolve the dispute and then present the issue and each side's argument.

We have free case simulator on our site. Check it out at https://www.decisionlayer.ai/simulate


I'd rather arbitrate by coin toss.

Can you share the warning? I made a public page and would say it was not clear to me this was a consequence of doing that. The warning as I remember it (a month ago) makes it sound like the information on this page is going to be public -- not - oh yeah the email addresses of everyone who edited this page will also be leaked.

When you start contributing to a page you see this:

https://cleanshot.com/share/trYdqYFZ

This is pretty meh. We will deploy more explicit messaging while we mitigate this properly.


The warning is too vague. “May become visible” kind of sounds like Notion doesn’t know whether they will become visible or not.

It's definitely weasel wording. And moreover, it's honestly tiring to constantly have these weasel words carrying such weight, and then jackasses getting bent out of shape that they aren't given the benefit of the doubt anymore.

Just following up that we've made it more explicit while we work on this:

https://cleanshot.com/share/8yFpGVDQ


Also, to me, "anyone who can view this page" sounds like "anyone _in this workspace_ that can view this page", not "anyone _on the public web_".

Please also especially clarify that IDs of contributors will be public. Meh is good, but this was a bit too simple.

There is a way to mitigate this. Re-hash and cache the page to be meta-less for public URLs. I guess that requires a huge amount of coding for a team that has not built the product from the ground up. But I feel like a "copy and paste" could fix that (remove author data).


Great post. Thank you.

How/where did you find your suppliers/factories?


Do you plan to offer an image service?

Great write up!


Our business model is focused on providing VLEO systems (satellites, buses, and full mission services). But future customers may be provide image services :)

Thank you!


Looking forward to more launches! Thank you


So...oai or google?


Yahoo. They're due for a comeback


Hey, maybe he has morals.


Really nice release. Excited to see this out in the wild and hopeful more companies leverage this for better end user privacy.


Not a public company.


Ah my mistake


@simonw

Great post. I've thought about what I want for better Vibe Engineering:

Each agent needs to deliver a fully working App/URL/Build so the functionality can be tested & verified.

Today AI IDEs deliver the diff + an explanation. Excellent. But give me the full build, a build I can share. A build that represents what it would be like shipped. When it comes to user facing functionality, a real build is how product owners verify a feature is complete.

Learn from Vercel -

A key part of Vercel’s magic is the automatic deployments for each branch. When working on a project with per branch vercel deployments - a team gets the immediate value of:

Shareable work - now others can see/test/give feedback on the great new feature you’ve developed - and their only work is to click a link (not git pull a branch and attempt to run locally)

No more “it works on my machine”. It either works or it doesn’t.

Confidence that if released, you know exactly what the user will experience. Give me automatic deployments for each agent, for each PR. And keep them available to spin up / re-use later.

I want to be able to re-launch it 3 months later and it just works. The reason we don’t do this today is the cost of the engineering - but with docker et al + AI agents, the cost of the eng work drops 99%

Deliver the deployment in such a way that immediate feedback to the AI could be given. This way minor tweaks can be executed immediately by the AI meaning that I can just wait for the minor tweak, review and then merge. This means the PR gets shipped NOW.


I think a key skill is knowing what level of complexity a single run can realistically achieve, which is often only a small task and not a fully working build.


Out of interest, what is the thinking behind sending a physical mailer to what feels like a large fraction of San Francisco?

Both why send it and why send it with very little info included on the page?


Did you get one? :) This was a part of our Series B raise to help get our name out


I did. Were you trying to get VCs to know about you? Or more like a twilio billboard that just said ask your devs?


The postcards were part of a dev-focused campaign to get people curious enough to check us out. We kept it minimal to stand out amongst other mail.


Wait, they sent out physical spam?


Nice André!


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: