Transparency / Code provenance
Our code.Our development history.
Questions have been raised about the relationship between Sagefire's Discord bots and the original TornWatch project. I reviewed Sagefire's development records and compared the code. Here is what the evidence shows, and what it does not.
Evidence review
The review at a glance
- Current Python files checked for identical complete-file copies
- 780
- Archived TornWatch Python files used as the comparison set
- 21
- Identical complete files found in the current repository trees
- 0
- Active modules examined with a targeted source-code comparison
- 126
What the evidence shows
A factual response, grounded in code.
The available technical evidence does not substantiate a blanket claim that the current Sagefire bots simply reproduce TornWatch source code. The review also confirmed that older TornWatch files were retained in a private Sagefire repository.
Distinct implementations
In the reviewed modules, notable matching sequences were primarily conventional Discord.py interactions, Torn API patterns and common URLs. The review did not establish a convincing wholesale reproduction of distinctive TornWatch application logic in those modules.
A documented development trail
Sagefire's War Bot, armoury and market implementations were recorded in Git history in August 2026, before the TornWatch backup was uploaded to our separate WatchTower repository on 18 September. This does not establish when access to TornWatch first occurred.
Historical material acknowledged
Older TornWatch source was retained in a historical repository, quarantined from the rebuilt runtime and later removed from the current repository tree. Git history retains the record. A September activity-reporting pull request also explicitly credited inspiration from TornWatch's reporting behaviour.
How the review was conducted
What was compared, and how.
The review examined the current Python files across four Sagefire repositories and 21 Python files from an archived TornWatch snapshot. All 780 current Python files were checked for exact, complete-file matches against that historical comparison set. None were identical.
A targeted selection of 126 current modules was also compared at source level for matching sequences of Python code. Longer similarities were inspected in context to distinguish standard framework patterns from potentially distinctive application logic.
The source-level comparison was a targeted lexical review, not a complete independent forensic or legal audit. It did not examine every historical revision, independently obtain the original TornWatch project or determine ownership or permission rights.
Recorded milestones
A development history we can account for.
- Initial Sagefire Bots repository history includes War Bot, armoury and market components.
- Faction supply-purchasing backend development documented.
- A TornWatch PebbleHost backup first appears in the WatchTower repository.
- The Sagefire activity reporter is introduced, with its pull request acknowledging the TornWatch reporting concept.
- Historical TornWatch source is quarantined from the active development structure.
- The legacy directory is removed from the current tree; the historical commits are preserved.
Dates describe recorded GitHub events, not definitive dates of original authorship or first access. The underlying repositories are private, so this page does not expose source code or confidential development records.
What remains unresolved
The limits of a code comparison.
Finding no identical complete files does not rule out copied fragments, adapted code, earlier historical versions or similarities that a lexical comparison cannot detect. The 126-module review was a targeted screen, not an exhaustive manual or independent forensic review of every version.
Technical differences also cannot decide who owns historical TornWatch code, or whether retaining or adapting it was authorised. The review did not independently verify the original author's complete source repository, contractual arrangements or any specific disputed code references.
Those questions remain open. I will preserve the relevant evidence and review credible new information.
An open invitation
To the original TornWatch developer
I respect the work involved in creating software, including the original TornWatch project.
If you believe Sagefire contains protected source code reproduced without permission, please identify the specific files, functions or implementations involved, along with the relevant versions, dates and basis for the ownership claim.
I will investigate substantiated concerns fairly and take appropriate action if an issue is confirmed. I ask that discussion of the projects remains professional and supported by evidence.
Contact Sagefire about code provenanceProfessional standards
Protecting my reputation.
Good-faith criticism and evidence-based questions are welcome. However, I will not hesitate to seek legal advice and, where appropriate, take legal action in response to repeated false and defamatory allegations that seriously harm my reputation or Sagefire.
Our commitment
Transparent records. Respect for creators.
I am committed to maintaining accurate development records, respecting third-party intellectual property and resolving specific concerns through evidence. I will correct this statement if new, verified findings warrant it.
Anth Richardson
Reviewed 30 October 2026. This is a summary of a static technical review, not a legal determination of copyright ownership, infringement or permission. The private detailed report and source code are not published here.