Keep facts separate from guesses

Source chain#

Every Product record links to public Sources. A Source stores its URL, title, excerpt, source type, trust level, and fetch time; Evidence maps a field to a specific excerpt.

field_pathruntime.cloudflare_workerssourceofficial documentationexcerpt

A field-level excerpt explains where the fact came from.

How to read evidence#

When reading evidence, start with the field path, then inspect the source type, domain, excerpt context, and update time. Good evidence answers three questions: which exact field it supports, whether the source directly describes the behavior, and whether the information still applies to the current version and scenario.

Start with the fieldConfirm whether it supports a runtime, integration, pricing, or capability field instead of a general product description.
Then inspect the sourcePrefer official documentation, API references, or repositories, and read the context around the excerpt.
Finally check freshnessVersions, regions, plans, and permissions change; update time is a signal, and the official documentation remains the final authority.

Trust levels#

official=true means the source comes from the product domain or official repository; trust_level=primary means it directly describes product behavior.

primaryOfficial documentation, API references, and READMEs.

secondaryReliable product introductions or ecosystem material that should be paired with primary sources.

unknownThe source cannot be confirmed and should not support a final decision.

Unknown information#

Reuseio does not treat a missing field as false, and does not let AI fill in pricing, compatibility, runtime, or API capabilities from common sense. Unsupported information stays null or is explicitly marked unknown.

Important“No evidence found” means the current catalog has no evidence; it does not mean the product cannot support the capability.

Updates and revalidation#

Treat the source trail as a revalidation entry point, not a permanent promise. When a product releases a new version, changes plans, adjusts permissions, or moves documentation, reopen the official source and verify critical paths in your own integration tests.

Low-risk readsRead catalog data and Manifests according to your cache policy, checking freshness before use.

High-risk decisionsFor migrations, authentication, payments, compliance, or production permissions, return to official documentation and change records.

Preserve the judgmentRecord the source, version, and unresolved questions behind your choice for future review.

External fallback#

GitHub and npm Registry results expand candidate discovery but are not verified Reuseio records. The SDK preserves verified: false, so the caller must complete verification.