Trust model

Drupal Knowledge is useful only if you can tell what kind of claim you are reading. Seven kinds exist, and exactly one of them is trusted knowledge.

The distinction is not pedantry. A security advisory published by the Drupal Security Team is authoritative about Drupal — but it is a statement the Security Team made, not a rule Drupal Knowledge reviewed and adopted. A fix that was verified on one site is real, and it is still one site. Flattening those into a single list of "things Drupal Knowledge says" would make the whole thing worth less than the sources it reads.

Why some conclusions are refused

Several states you might expect are deliberately absent. There is no passed, no secure, no compliant. Absence of an adverse observation is not a conformance verdict, so there is no passing state to reach for.

Not observed means a search did not find something within a scope that is stated alongside it. Where that scope is bounded — a code scan that read some files, a rule set that covers nine checks — absence proves nothing, and the record says so rather than letting silence imply safety.

Unknown is a real answer and is never collapsed into no. A contributed project with no registered release feed is unknown, not compatible. A deprecation with no stated replacement records that the annotation was silent rather than inventing advice.

How something becomes trusted knowledge

By a person deciding it should, and editing the repository to say so. There is no automatic promotion at any point: a source that changed creates review work, a corroborated community observation creates review work, and a solved case that recurred creates a proposal awaiting review. None of those paths ends in a record changing itself.

The classes, and which one is trusted knowledge

Every record Drupal Knowledge can return carries exactly one of these.
LabelRecord type Trusted knowledgeWhat it means
Finding finding no Produced by applying a reviewed rule or authoritative record to this project's evidence. Its strength is whatever its state and evidence say.
Project Observation project-derived evidence no Observed in this repository at this revision. It is a fact about this project and never a rule about Drupal.
Internal Proven Solved Case solved case no Proven in the project context it was captured from. It is not universal Drupal truth and widening it requires review.
Reviewed Drupal Knowledge trusted knowledge, reviewed by a human against authoritative sources yes A human reviewed this against registered authoritative sources. It states something about Drupal, not about any one project.
Reviewed Implementation Rule reviewed rule evaluated against project evidence no A reviewed rule whose authority is a pinned authoritative source. It says what to look for; it says nothing until evidence settles it.
Authoritative Drupal Source Record source-derived authoritative record no Projected verbatim from an official Drupal source snapshot. It is authoritative evidence about Drupal, but it is not a Drupal Knowledge rule.
Untrusted Discovery Signal discovery signal no An untrusted ecosystem observation awaiting corroboration and review. It may not be acted on as Drupal Knowledge.

What this site deliberately does not publish

Drupal Knowledge holds more than it publishes. These domains are excluded by name so that a missing section reads as a decision rather than an oversight.

  • discovery_signal — Discovery signals are untrusted community observations awaiting corroboration and review. Publishing them beside reviewed knowledge would make untrusted material look like an answer, so this release publishes none of them.
  • finding — A finding is a rule applied to one project's evidence. Publishing it would turn one project's state into a claim about Drupal.
  • implementation_finding — A finding is a rule applied to one project's evidence. The reviewed rule behind it is published instead.
  • migration_work — Migration work items name files and lines in one project. The authoritative deprecation records behind them are published instead.
  • project_evidence — Evidence describes one repository at one revision. It answers a local question and is never global Drupal content.
  • remediation_plan — A remediation plan is computed for one project's installed versions. The advisories behind it are published instead.
  • upgrade_assessment — An upgrade assessment is bounded by one project's evidence and is not a statement about Drupal.