Methodology
How CodingSubs handles subscription facts
This page describes the evidence rules and limits supported by the current directory. It does not claim automated vendor checks or live verification.
What the directory publishes
The directory currently publishes product and vendor names with official links. Inherited prices, quotas, conditions, and verification assertions remain Unknown until each individual fact has been reviewed.
A source URL, matching excerpt, or status copied from an imported record does not by itself establish that a commercial value is accurate.
Evidence and recorded dates
A reviewed fact should have supporting official-source evidence, a recorded observation date, and its relevant currency, billing period, and conditions. Evidence for one fact does not verify a different price, quota, or promotion.
Migration, building, and rendering preserve inherited records and timestamps; they do not independently verify claims or refresh verification dates.
Unknown values and price comparisons
Unknown is not zero, and an unpublished usage limit is not unlimited. Free software, free inference, and provider-billed usage are separate facts.
A numeric price comparison requires reviewed fixed amounts with compatible currency, billing period, billing unit, region, tax treatment, and eligibility. Missing or incompatible details make a price Not comparable; the directory does not convert currencies or rank mismatched billing periods.
Open the comparison page to compare product information. Unreviewed commercial values remain Unknown there.
Price history and charts
No price-history chart is currently published. Imported history is not treated as verified vendor evidence. Generated fallback history and seeded operational records are demonstration data, not production activity.
If a chart is published later, it must include an equivalent readable text or table view with amounts, units, dates, and provenance. Synthetic history must be clearly labelled as demonstration data.
Current operational limits
This project generates a static directory. It does not run a live crawler, extraction service, verification refresh, or authenticated review workflow. The admin destination is disabled; secure operations require a separately approved server-side architecture.