Value Grow a Garden
Open navigation menu

Public revision history

Grow a Garden Value Data Changelog

This log records dataset releases, corrections, evidence-status changes, and whether numeric values changed. Product features and editorial rewrites are excluded unless they alter how value data is interpreted.

Current release

gag1-pets-2025-08-20-r1

Status: archived · Evidence grade D · 103 records · 0 raw trade observations · 0 current verified values. File integrity is checksum-verifiable; current-market accuracy is not established.

Audit the release and checksums →

Current GAG2 codes snapshot

gag2-codes-2026-07-30-r1

Status: reported active · Confidence: moderate · 3 code records · 3 named secondary sources · 0 publisher in-game redemptions. This is a dated source-consensus snapshot, not a live official feed.

Inspect codes, sources, and limitations →

Data revision history

codes-snapshotNumeric values unchanged

Published a GAG2 code-status snapshot covering three reported-active codes, three named secondary sources, source dates, explicit verification limits, and a SHA-256 file checksum.

release: gag2-codes-2026-07-30-r1

metadataNumeric values unchanged

Published the first machine-readable release manifest, checksums, coverage counts, field definitions, and evidence grade.

release: gag1-pets-2025-08-20-r1

correctionNumeric values unchanged

Normalized relative update strings to the known 2025-08-20 observation timestamp and stopped presenting demand as sample count.

release: gag1-pets-2025-08-20-r1

snapshotNumeric values changed

The three bundled GAG1 pet batch files were recorded in repository commit 9243eec.

release: gag1-pets-2025-08-20-r1

What triggers a data entry?

  • A new or replaced source file.
  • A numeric value, currency, or item attribute changes.
  • An evidence grade or verification status changes.
  • A correction changes how a field must be interpreted.
  • A release becomes current, superseded, or archived.

What every future entry must show

  • An absolute date and stable release ID.
  • Whether numeric values changed.
  • The evidence or methodology impact.
  • A machine-readable manifest and file hashes.
  • Patch context when it is actually known.

Corrections are evidence-led

A complaint or screenshot is a review candidate, not an automatic price update. A current range requires comparable item attributes, currency, observation time, source type, and enough corroboration to support the published statistics.