Akron records its view of active features, policy classifications, overrides, and proof settings so a reviewer has more context.
What Akron records
Proof-oriented metadata can include:
- Visible policy classification (Goldberry/Hardlist clear, Normal clear, or Cheat) and attempt status. A new or reset attempt can be Unclassified.
- Active-feature list.
- Pause counts and paused duration.
- Map and loaded-module version context (via Map Version Stamp).
- End Screen Helper settings.
- Proof Recorder Guard state (whether recording or replay buffering is armed).
- Journal Snapshot/Compare output.
What Akron does not prove
Akron does not:
- Certify a run as accepted by a leaderboard or event.
- Replace moderator review.
- Prove the absence of all external integrations.
- Make Cheat features acceptable for clean submissions.
- Hide or erase feature use by disabling a tool later.
Proof metadata is context, not a verdict. Use the target community’s submission rules as the authority for whether a run is accepted.
Submission Mode
Submission Mode enables proof-oriented guardrails and metadata without changing gameplay. Akron classifies it as Goldberry/Hardlist clear because its behavior is limited to records and warnings.
Related proof helpers include Proof Recorder Guard, End Screen Helper, Pause Tracker, Map Version Stamp, Golden Start Helper, Lag Pauser, and Journal Snapshot/Compare. Each helper carries its own policy classification; enabling Submission Mode does not make every helper Goldberry/Hardlist clear.
For path redaction in Akron-owned UI, see Streamer Mode.
Proof workflow
For the steps to prepare, capture, and review a proof-oriented attempt, use Capture and recording. 