> implied contractual obligations
What does this phrase mean? There is no way that any sound contract law will grant any weight to the term "implied". Either it is written (and agreed) or not. So, I would say anything that is not explicit is meaningless in term of contract law. (Again: I am only talking about jurisdictions with serious, mature contract law, not some banana republic.)
Sometimes what the contract says and what the contract _looks_ like it says to a layman can read very different.
- Granted $500k of stock on start, and then have it diluted as stock is added for new investors
- Hollywood accounting - net vs gross
There's lot of places where a contract can be represented as one thing, only to have it be far less than that.
Then it is a poorly written contract, and the party that agreed to it was tricked or poorly advised. Plain and simple. We see this often with "fast and loose" term sheets for some corporate and sovereign bonds on less reliable names. There is a whole podcast (I forget the name at this very moment) that does nothing but discuss dubious bond contracts. Frequently, the co-hosts will ask: "Who in their right mind would agree to such a contract? This clause is totally unenforceable / provides no protection against event X/Y/Z." And, yet, these contracts still exist in the wild.
Dumb question: Do you think the average dev in Silicon Valley pays a third-party employment contract lawyer to review the terms and conditions before agreeing? Sadly, I feel the answer is "no". Speaking personally, I would never agree to such complex employment compensation terms without third-party advice. Yes, I know it is not cheap (maybe 500 USD per hour), but the alternative looks much worse, and most people here facing these contracts can afford it.
> Then it is a poorly written contract, and the party that agreed to it was tricked or poorly advised.
Well, yes? I mean, we're talking about a situation where one of the parties involved in the contract isn't acting in good faith. And people frequently can't understand contracts. Is there anything surprising about the fact that someone was misled or "tricked" in such a situation?
> There is no way that any sound contract law will grant any weight to the term "implied".
Nobody is suggesting that any law would.
> Either it is written (and agreed) or not.
Yet you managed to infer things that weren't in the post.
> So, I would say anything that is not explicit is meaningless in term of contract law.
Again, where is anybody saying anything to the contrary?
If I say I'll give you 50% of the revenue we generate, and then the details of the contract allow me to bring on other people with the same deal of 50% of the revenue, and then you all share 50% it would likely feel unfair.
I'd say that phrase means 'consideration' in some cases, and in any case something like 'reasonable expectation', which would enter into the 'meeting of minds' prerequisite of contract law.
Banana republics like almost all countries with Civil Law rather than Common Law? And also, you know, some US states and the UCC?
The doctrine that anything not explicit is meaningless in contract law is also referred to as 'the four corners' referring to where you look to interpret the contract; this is considerably relaxed in many jurisdictions (and some situations in the US) where there is considerable information asymmetry and/or power imbalance between parties. With employment contracts in particular; to be a good coder for instance, why would you need to know how dilution of options works? Only to avoid being mislead by your prospective employer?
Conversely, in Civil Law jurisdictions, you see that corporations (rather than employees/consumers and sometimes small businesses) are mostly held to the four corners of the contract as they are professional parties that have legal departments and should be presumed to do their due diligence.