I am well aware that this set is infinite, while the set of what IS included is at most as long as the code, which in bounded delivery time is probably bounded too.
But yeah, you get it. A couple of pointed examples could go a long way.
Probably not a good idea. A list of features that are not part of the agreement suggests that things outside said list can be expected. It's probably tricky one way or another unless you can reduce it to something nearly mathematical, like a set of functions, but projects are rarely like that.
Yes but the existence of a supplement implies the need for said supplement, meaning the list of features that are included must be an inclusive list rather than an exclusive one.
Especially if legal action occurs (e.g. because the client refuses to pay), this might just come back to bite you in the ass. OTOH, I am not a lawyer, and different countries have different rules. You should probably be able to state explicitly that the "non-feature list" does not detract from the exclusivity of the "feature list" in some way.
Again though this sounds like a huge clusterfuck to me as there is no way to exactly state which features are part of the offer without extensive (unpaid!) work.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Are specs really possible?
What is a detailed enough spec but the implementation itself? Or at worst a test suite.
How about specifying which things will NOT be in the project? That might work in a "spirit of the law" kind of way to curb similar requests.
"so, flying unicorns are outside of the scope of the project and so are these N billions possible features"
But I love the idea! :)
I am well aware that this set is infinite, while the set of what IS included is at most as long as the code, which in bounded delivery time is probably bounded too.
But yeah, you get it. A couple of pointed examples could go a long way.
Probably not a good idea. A list of features that are not part of the agreement suggests that things outside said list can be expected. It's probably tricky one way or another unless you can reduce it to something nearly mathematical, like a set of functions, but projects are rarely like that.
It's more of a supplement. Can even come paired with the things on the list of what you will do as part of this price/time estimate.
E.g:
or
Yes but the existence of a supplement implies the need for said supplement, meaning the list of features that are included must be an inclusive list rather than an exclusive one.
Especially if legal action occurs (e.g. because the client refuses to pay), this might just come back to bite you in the ass. OTOH, I am not a lawyer, and different countries have different rules. You should probably be able to state explicitly that the "non-feature list" does not detract from the exclusivity of the "feature list" in some way.
Again though this sounds like a huge clusterfuck to me as there is no way to exactly state which features are part of the offer without extensive (unpaid!) work.