Principle
Warrant: Derivation
Access to the record is conditioned on contributing to it.
Nobody free-rides on trust generated by data they declined to supply. The condition is written into the relationship at the start, where it is a term, rather than raised later, where it is a favour.
01 · Why the question is structural
A record is worth querying because of what other parties put into it.
What makes a record worth consulting is not the skill of whoever keeps it. It is the breadth of what has been fed in. A record assembled out of one party's own history tells that party what it already knew. A record assembled out of many tells each of them something none of them was in a position to observe.
That is the entire source of the value, and it settles what kind of question access is. Who may draw on the record is not a commercial question about tiers and entitlements. It is a structural question about what keeps the thing worth drawing on at all.
Stated the other way round: every query answered against the record spends something somebody else supplied. If queries can be spent by parties who supply nothing, spending and supply come apart, and the record thins in the way a commons thins. Not through anyone behaving badly. Through arithmetic.
So access is governed by a rule about contribution, not by a rule about payment. What is paid, and by whom, is a separate decision, settled separately at who pays.
02 · The condition, as a term
Warrant: Foundation
Agreed at the start, where it is a term, never asked for afterwards, where it is a favour.
The condition is short enough to state in one line. A party that draws on the record contributes real outcomes back to it. Not summaries. Not the cases that reflect well. Not an extract prepared for the purpose. The outcomes as they occurred, on the deployments the record was queried about.
Where that condition sits in the relationship decides whether it survives. Placed at the start, it is a term of participation: priced into the arrangement, agreed between parties whose interests are still symmetrical because nothing has happened yet. Placed afterwards, once the record has been useful and a bad outcome has arrived, it is a request, and a request arriving at that moment asks a counterparty to volunteer the one thing they would most prefer to keep. The wording does not change. The position in time changes everything.
It goes in the contract, in plain language, alongside the other two decisions this firm makes before an engagement rather than during a dispute: who bears the cost of a wrong answer, and how liability is allocated when one arrives.
- 01 Access is conditional, not purchased The right to put questions to the record is a term of the relationship, not a product bought separately from the obligation attached to it.
- 02 What is contributed is outcomes What actually happened on the deployment the record was consulted about, in the form it happened, at the point it is known.
- 03 Unflattering outcomes are in scope A contribution filtered down to the successes is not a contribution. It is advertising, and the record has no use for it.
- 04 The term is fixed before outcomes exist Written at the start, while both parties are still deciding, and not renegotiated once results begin to arrive.
03 · The outcomes nobody volunteers
The crews that performed, and the ones that did not.
A record of successes is a brochure. What makes a record load bearing is the presence of the deployments that went badly: the crew cleared for work it then struggled with, the qualification that did not survive contact with the plant, the estimate that proved optimistic under conditions nobody had written down. Those cases carry more information per observation than any success, because they are the ones where the prior was wrong, and a body of evidence that cannot see where it was wrong has no mechanism for becoming right. They are also the cases nobody volunteers. Which is exactly why supplying them is a term rather than an appeal to good citizenship.
A record containing only what its contributors were content to send is a record of what they were content to send.
04 · A shared record is not a rating
One is an opinion sold to whoever will buy it. The other collapses the moment it can be taken from without being added to.
The two get confused constantly, and the confusion matters here because they fail in opposite directions. A rating is an opinion about a subject, formed by one party and sold to another. Its integrity problem sits on the payment side: a rating paid for by the party being rated has its incentive running the wrong way, which is the argument at who pays. Its supply side is unremarkable, because the party forming the opinion needs no cooperation from the subject in order to keep publishing.
A shared record has the opposite profile. Nobody has to buy a flattering answer to break it. It is enough that the parties who could feed it decide, individually and quite reasonably, to consume rather than contribute. The failure is depletion, not flattery, and depletion has no villain in it.
- A rating
-
An opinion about a subject, formed by one party and sold to another. It is worth exactly as much as the independence of the party forming it, which is why the payment relationship decides its value.
Bayswater is not one, and the reasoning is at seven classifications, refused.
- A shared record
-
An accumulating body of checked outcomes that many parties draw on and many parties supply. Its worth is set by what has been put into it, so its failure mode is exhaustion rather than corruption.
Fixed here, and used in this sense throughout the site.
- Free-riding
-
Drawing on trust generated by observations somebody else supplied, while withholding your own. Rational at every individual step, and fatal to the record in aggregate.
The condition in section 02 exists to make it structurally unavailable rather than merely discouraged.
05 · Withholding runs one way
The parties with the worst outcomes have the strongest reason to withhold them.
If withholding were random it would cost the record precision and nothing more. It is not random. The reason to withhold is strongest exactly where the outcome was worst, because that is where it is most embarrassing, most likely to be contested, and most likely to be read as an admission by somebody with an interest in reading it that way.
The consequence is not a record with gaps in it. It is a record with a bias whose direction is known in advance. It is most confident precisely where it has been least tested, and least accurate precisely where inaccuracy costs the most: the deployments that go wrong, the conditions nobody anticipated, the failures where somebody is hurt or a programme is ruined. Wrong in the middle of its range, a record is a nuisance. Wrong at its edges it is dangerous, and the edges are the first thing selective contribution removes.
Which is why the condition cannot be softened into an aspiration or a best-efforts clause. A best-efforts obligation to contribute is honoured most faithfully by the parties with least to hide, and that reproduces the same bias one degree removed, wearing better manners.
| The outcome | Reason to withhold it | What the record then says |
|---|---|---|
| The deployment that went well | None. It reflects well and it is easy to send | Confident, and correct |
| The deployment that went badly | Contested, uncomfortable, and possibly evidence | Silent, where it was needed most |
| The near miss with no consequence | Nothing formally happened, so nothing is reported | Blind to the conditions that precede a failure |