"Will this be done Thursday?" If you answer with a confident "yes" you're going to learn the cost of commitment when an unknown bites you in the ass.
It's always about degrees of probability.
You said all knowledge is inductively reached, why didn't you say "probably"?!
From a mission perspective, overflowing with data is a good place to be. From a computer perspective, overflowing with data is a problem that needs management.
People work as a team - in fact often teams of teams - yet we assign blame to individuals.
Needless to say, that company bled a lot of high quality developers as a result, somehow turning a likely success to likely failure.
Startups should beware of such behavior - it is a great way to cause the company to self-destruct when you are not giving all stakeholders adequate say on deliverables.
Unrelated, note how difficult it is for people to accept 100% responsibility for a problem. For example:
> Did we (the JPL team) make an error in assuming how the select/pipe mechanism would work ? Yes, probably.
There's no "probably"! A mistake was clearly made.