EOLScope

Trust model

How EOLScope handles lifecycle data

Source first

Every material lifecycle claim should trace to a stored source. Official vendor lifecycle portals, bulletins, policies, and staff-authored technical documentation are preferred.

Unknown beats guessed

If a vendor has not announced a lifecycle date, EOLScope stores that state rather than estimating a date and presenting it as fact.

Freshness is visible

Every record has a last-verified date. Aging records display a warning rather than silently appearing current.

Standard vs extended support

Risk bands use standard EOS. Extended EOS is displayed separately because eligibility can depend on product designation, entitlement, or support policy.

Automation is conservative

Source monitors can detect changes automatically, but ambiguous lifecycle changes should enter a review path before changing public facts.