FTRCRP Editorial Standards

Version: 1.0 Effective: 2026-01-26 Review Date: 2027-01-26

Purpose

These standards ensure all FTRCRP publications maintain accuracy, fairness, and ethical integrity. They apply to all content published under the FTRCRP name.

Core Principles

1. Accuracy First

• Verify before publish. Every factual claim requires a source.
• Distinguish fact from opinion. Use clear language: “evidence shows” vs “we believe.”
• Acknowledge uncertainty. “Appears to,” “suggests,” “alleged.” Use appropriate qualifiers.
• Correct errors promptly. Issue corrections publicly with changelog documentation.

2. Fair Representation

• Present all relevant sides. Include perspectives that challenge our conclusions.
• Steelman, don’t strawman. Represent opposing views at their strongest.
• Right of reply. Contact subjects for comment before publication when practical.
• No personal attacks. Criticize actions and systems, not individuals’ character.

3. Transparency

• Disclose conflicts of interest. Financial relationships, personal connections, prior involvement.
• Show methodology. Explain how we reached our conclusions.
• Cite sources. Enable readers to verify independently.
• Open to correction. Welcome challenges to our findings.

4. Proportional Response

• Punch up, not down. Prioritize investigating power, not individuals.
• Consider impact. Will publication cause disproportionate harm to the subject vs public benefit?
• Privacy by default. Minimize personal information unless directly relevant.

Citation Requirements

Sourcing Standards

Archive Protocol

All web sources should be archived to prevent link rot:

# Wayback Machine submission
curl -s "https://web.archive.org/save/[URL]"

Include both original URL and archive link in citations.

Citation Format

Use numbered references:

CryptoEasily claims FCA authorization [1], however no registration exists in the FCA register [2].

With footnotes:

[1] CryptoEasily.com, "About" page, captured 2026-01-15
    Archive: https://web.archive.org/web/20260115000000/https://cryptoeasily.com/about
[2] FCA Register search, "cryptoeasily", accessed 2026-01-15
    https://register.fca.org.uk/s/search

Language Guidelines

Factual Tone

Use:

• “The evidence shows…”
• “According to [source]…”
• “Analysis indicates…”
• “Documents reveal…”

Avoid:

• “Shockingly…”
• “It’s obvious that…”
• “Everyone knows…”
• “The truth is…”

Qualifier Usage

Characterizing Subjects

Legal Considerations

Defamation Prevention

Before publishing, verify:

• All factual claims have sources
• Opinion is clearly labeled as opinion
• Subjects have been contacted for comment (where practical)
• Language uses appropriate qualifiers
• Public interest outweighs privacy concerns

Fair Comment Defense (Opinion Pieces)

Opinion is protected when:

• Based on true or privileged facts
• Clearly identifiable as opinion
• On a matter of public interest
• Made without malice

Right of Reply

For investigation pieces involving specific entities:

1. Attempt contact before publication
2. Allow reasonable response time (48-72 hours minimum)
3. Include response or note that contact was attempted
4. If no response: “FTRCRP contacted [entity] for comment. No response was received.”

Content Categories

Investigations

Requirements:

• Minimum 3 independent sources for key claims
• All regulatory claims verified against official registries
• Evidence preserved (archived URLs, screenshots, local copies)
• Methodology section explaining how research was conducted
• Assessment of uncertainty and alternative explanations

Checklist:

• Primary claims have 3+ sources
• Regulatory status verified against official records
• Web evidence archived (Wayback Machine)
• Subject contacted for comment
• Legal review for defamation risk
• Public interest clearly established

Analysis

Requirements:

• Data sources documented
• Methodology explained
• Limitations acknowledged
• Counterarguments addressed

Checklist:

• All data sources cited
• Sample size and scope disclosed
• Alternative explanations considered
• Uncertainty quantified where possible

Guides

Requirements:

• Tested on specified platforms
• Security implications noted
• Troubleshooting section included
• Version/date-specific (will need updates)

Checklist:

• Instructions tested before publication
• Prerequisites clearly listed
• Security considerations included
• Version dependencies noted

Opinion

Requirements:

• Clearly labeled as opinion
• Evidence for arguments cited
• Counterarguments acknowledged
• Author identified

Checklist:

• “Opinion” or “Commentary” label visible
• Thesis clearly stated
• Supporting evidence cited
• Best counterargument addressed

Pre-Publication Checklist

All Content

• Accuracy: All factual claims sourced?
• Fairness: Opposing views represented?
• Transparency: Conflicts disclosed, methodology explained?
• Proportionality: Benefits outweigh potential harm?
• Ethics: Would we stand behind this if challenged publicly?

Sensitive Content

Additional checks for investigations or pieces naming specific individuals/entities:

• Legal: Defamation risk assessed?
• Right of reply: Subject contacted?
• Privacy: Personal info minimized?
• Evidence: Archived and preserved?
• Cool-off: 24-hour waiting period (for high-stakes pieces)?

Post-Publication

Corrections Policy

Minor errors (typos, formatting):

• Fix silently or note in changelog

Factual errors (incorrect data, wrong attribution):

• Issue correction at top of article
• Update text with strikethrough showing original
• Note in changelog with explanation

Significant errors (undermines core argument):

• Consider retraction
• Issue prominent correction
• Notify readers who may have shared

Correction Format

**CORRECTION (2026-MM-DD):** This article originally stated X.
The correct information is Y. We regret the error.

Changelog Maintenance

All articles include a version history:

| Version | Date | Changes |
|---------|------|---------|
| 1.1 | 2026-02-15 | Corrected FCA registration status |
| 1.0 | 2026-01-26 | Initial publication |

AI Assistance Disclosure

When AI tools are used in research or drafting:

• Disclose AI usage in methodology section
• Human verification of all AI-generated claims required
• AI suggestions treated as starting points, not conclusions
• Final editorial judgment always human

Disclosure format:

*Research assistance: AI tools were used to [specific purpose].
All claims were independently verified by human researchers.*

Appeals & Disputes

Subjects of FTRCRP coverage may request:

1. Clarification. Explanation of methodology or conclusions
2. Correction. If factual errors are demonstrated
3. Right of reply. Publication of their response

Requests should be submitted to HAL0zum@proton.me with:

• Specific claims disputed
• Evidence supporting their position
• Desired remedy

FTRCRP commits to:

• Acknowledge receipt within 48 hours
• Respond substantively within 7 days
• Publish corrections promptly when warranted

Standards Enforcement

These standards are self-enforced through:

1. Pre-publication checklist. Mandatory before publishing
2. Peer review. Second pair of eyes for investigations
3. Post-publication review. Periodic review of past content
4. Reader feedback. Corrections welcomed and addressed

Document History

These standards are a living document. Suggestions for improvement are welcome.