Challenges & revisions
Contesting a finding produces a new revision, never an edit.
A conclusion that cannot be contested is not credible. Every resolved case can be challenged with new evidence.
The lifecycle
SUBMITTED → CONSENSUS_PENDING → RESOLVED
RESOLVED → CHALLENGED → CONSENSUS_PENDING → RESOLVED (revision N+1)Revisions are append-only
A challenge creates revision N+1. Revision N is never overwritten or deleted, and both remain readable forever. The history is the point.
Stale challenges are refused
A challenge must reference the current revision. A challenge racing another challenge is rejected rather than silently overwriting it.
What a challenge needs
- A stated reason: what the analysis missed.
- Bounded supporting evidence: commits, paths, a declared parent.
- A wallet signature. ForkReason's server holds no key that can act for you.
Challenge evidence is treated as inert data, exactly like everything else a repository contains.