Match each source and date to the claim it can support
The public Wage101 editorial policy describes the reader-facing editorial boundary; this guide explains how source states affect work/pay content.
| State | Meaning | What it does not prove |
|---|---|---|
| Access date | When the source was retrieved or checked | That the rule is effective now |
| Effective date | When a sourced rule says it applies | That Wage101 reviewed or published it |
| Review date | When claim and evidence were assessed | Publication approval |
| Publication approval | A separate gated decision | Complete or permanent currentness |
Trace claims and respond to review triggers
- Identify the exact claim and the source scope that supports it.
- Trace the dependency to affected methodology, tool and article surfaces.
- Review when an effective date approaches, an official change appears or a source fails.
- Investigate redirects, evidence-hash mismatches and disagreement with the owning engine.
- Treat source review and publication approval as separate gates.
Fail closed and retain successor history
Missing, stale or ambiguous load-bearing evidence blocks the dependent local claim or surface. The workflow does not fill the gap with a Global default, an old number or an implied zero.
When evidence changes, a successor record preserves chronology and the new review binds to that successor. Historical evidence is retained rather than silently overwritten.
Separate stable methodology, registry-owned DataHubs and deferred coverage
A stable arithmetic example can remain visible in the Effective Hourly Wage methodology while a changing local policy dependency follows its own evidence lifecycle.
Locale DataHub links are emitted only when the current public policy-data registry has published entries for that locale. This page does not hard-code an empty or deferred hub, and the absence of a hub does not mean that a rule is zero, irrelevant or covered elsewhere.
- Link a locale DataHub only when its registry-owned route is public and renderable.
- Label deferred markets and topics as uncovered rather than assuming a value.
- Correct the owning evidence and dependent surfaces without rewriting historical approval.
- Avoid completeness and “always current” language.
Frequently asked questions
- Does a reachable official source prove a Wage101 claim is current?
- No. Source scope, effective date, claim binding, review and publication approval must still agree.
- Does a missing locale DataHub mean there is no applicable rule?
- No. It means Wage101 is not exposing a public registry-owned hub for that locale state; uncovered or deferred topics remain explicit.
- Does every source use one fixed refresh cadence?
- No. Reviews are driven by source risk, effective dates, dependency needs and detected changes.
Sources checked
- Wage101 editorial policy — Wage101 (accessed 2026-07-28): Public editorial and correction boundary.
- Effective Hourly Wage methodology — Wage101 (accessed 2026-07-28): Public example of a stable methodology surface distinct from changing local policy.