Why this page exists
Every other page on this site tells you something about tax. This one tells you how to judge whether to believe it.
That matters because tax content about digital assets ages badly and travels far. A confident sentence written for one country in one year gets quoted for another country in a later year, loses its qualifiers along the way, and ends up in a return. The result looks authoritative and is wrong.
So the method is published, and it is the same method whether the answer is convenient or not.
Rules are data, not prose
Every material tax proposition on this site exists as a structured claim before it exists as a sentence. The claim carries its jurisdiction, its tax year or effective date, its risk level, and its verification state.
Page text references that claim rather than restating it independently. Translations reference the same claim unless the jurisdiction itself differs — a translation may not quietly change a deadline, a rate, an exception or a conclusion.
The practical effect: when an authority changes, one claim changes, and every page referencing it changes with it. Content that is not tied to a claim cannot be maintained, only rewritten.
Evidence stays attached to the claim
Each claim carries a proof bundle recording, where applicable: the primary source and its URL; the source title and citation; the exact locator — the section, paragraph, question number, line, or form instruction; the effective date or tax-year scope; the strength of the evidence; the publication risk; the date and outcome of the last authority recheck; the question put to a reviewer; and the human verification state with the reviewer's identity.
A jurisdiction bibliography does not satisfy this. "Per HMRC guidance" is not a locator. The claim must be traceable to the specific place in the specific document that actually says it.
Two rules follow from this that are worth stating explicitly.
Secondary commentary is never primary authority. Professional blogs, including those of partners and reviewers, are useful for identifying what users are confused about and what questions deserve research. They cannot establish a rule, satisfy the proof requirement, or override a current government source.
A URL that still resolves is not evidence that the guidance is still operative. Rechecks are dated, and a stale recheck is treated as stale.
Verification is a human act
Research does not create verification. An AI system can find the authority, extract the locator, draft the claim and prepare the packet. It cannot approve it.
Approval happens through a review workflow that binds a reviewer's decision to a cryptographic fingerprint of the exact claim and proof snapshot they saw. If the wording or the authority changes after the packet was prepared, the approval cannot be applied — the process stops and the review must be redone. That check is not bypassed.
Reviewers are approved for defined jurisdictional scope, and that scope is verified independently. A person's public professional profile establishes who they are. It does not establish authority to approve a claim in every region someone has assigned to them.
Publication is not a status field
A page becomes publicly indexable only when its jurisdiction is live, the page is mapped to canonical claims, every mapped material claim is publication-eligible, review and freshness requirements pass, and no release gate blocks it.
Until then, draft pages remain excluded from indexing, from the sitemap, and from public claim manifests. The system is designed to fail closed: if eligibility cannot be proven, nothing publishes. A release that shows red because no claim has yet been approved is the system working, not a defect to route around.
What "high risk" changes
Some pages can cause a reader to take or miss a legal action: notice response deadlines, disclosure decisions, limitation periods, irreversible elections, residence and expatriation, foreign-account reporting with material penalties.
For those, current primary authority is mandatory, document-specific deadlines are qualified rather than generalised, uncertainty is stated rather than smoothed, and the reader is routed to a qualified professional where their facts materially affect the result.
You will notice the pattern across this site: no universal response period is stated for any tax authority letter. The document you received sets your deadline. A general article that gives you a number is giving you someone else's number.
What we will not do
- Use "verified" as decoration. The word appears only where the review actually happened.
- State a rate, threshold or deadline without a jurisdiction and a year attached.
- Manufacture urgency from penalties to drive contact.
- Imply guaranteed savings.
- Present a contested position as settled because the settled version reads better.
- Let a commercial relationship affect a treatment, a ranking, a confidence state, or a source selection.
What you should expect to see on a page
Where a page is doing its job, you should be able to find: a direct qualified answer near the top; the jurisdiction and the tax year; the verification state, stated honestly; what changes the answer; the primary authority, visible and adjacent to the claim; and a calm next step.
Where you cannot find those, on this site or any other, treat the content as a starting point for research rather than as a basis for a filing position.
Current state, stated plainly
At the time of writing, this site's tax content is in a pre-publication state. Claims exist, proof bundles exist, and human approvals do not yet. Every article carries a working status for that reason.
That is an uncomfortable thing to publish and the right thing to publish. A site that told you its content was verified before the verification happened would have failed the first test it set itself.
Related HolderTax pages
- Recordkeeping that survives an examination
- Reconstructing basis when exchange history is gone
- The regional guides, each carrying its own claim status
Evidence note
This page describes editorial and verification process only. It states no tax rule and requires no primary authority, because it makes no claim about the law. Everything it describes about the workflow is implemented in the publication system rather than asserted as a policy aspiration.