Editorial policy
How scores are set, what counts as evidence, and how a vendor can send a correction.
How we score and correct
How scores are set. The rubric is published on the rubric page before any score is shown. Each criterion has a written definition of three statuses: documented, partial and not documented. Each status has a score band: 8.0 to 9.5, 5.0 to 7.9 and 2.0 to 4.9. A reviewer reads the vendor's pages, picks the status the evidence supports, and records the score, the reason, the source URL and the read date. Totals are then computed from the weights file. The build refuses to publish if the weights do not sum to 100 or a total does not equal the sum of its parts.
What counts as evidence. We read documentation, product pages, release notes, pricing pages and the vendor's own announcements. A secondary source can be recorded, but it is labelled and it caps the criterion at partial. A page we could not read, for example one that returned HTTP 403 or 404, is recorded as unreadable and scored as not documented, with the reason shown. We do not treat a customer logo as a customer reference, and we do not cite a customer's quote as a measurement.
Containment coverage. An action counts on the scorecard when the vendor's own documentation lists it as a shipped action for at least one named product in that domain. A generic HTTP request step, a custom script, a community pack the vendor does not list, or the statement that a platform integrates with a product does not count. The scorecard method page gives the full catalogue of 25 actions.
Vendor claims. When a vendor states a figure about itself, we print it as a vendor claim with the page and the date. We do not repeat a vendor's adjectives as our own judgement. Where a vendor is behind on a criterion, the profile says so in plain words, and where a vendor leads, the profile says what the lead rests on.
Corrections and payment. Send corrections to editor@timetocontain.com. We log each accepted correction with its date on the corrections page. A vendor cannot pay to change a score, add a feature to a page, or remove a finding. A vendor can send us a documentation link we missed, and we will read it and update the score if it supports a higher status.
Updates. Pages carry the date the evidence was read. Vendor pages change, so a score is a statement about the pages on that date. When a vendor changes its documentation or ownership, we add a dated note and rescore the affected criteria.