How Brazilians spend crypto: research report + cost comparator
The spec for an evidence-based report ranking the five channels Brazilians use to spend crypto, plus an interactive cost comparator with transparent, editable assumptions.
Product artifacts
This is the process layer behind bitsARK's data products - the working documents behind each feature, published as they're written: problem statements, discovery evidence, acceptance criteria, decision logs, changelogs. These are the actual specs, revision history and all, sitting in git next to the code they describe.
Spec before code, retro after - no exceptions
Every substantial feature on this site starts as a written spec: the problem it solves, the evidence behind it, what shipping looks like, how success gets measured. I publish those documents so the reasoning stays checkable after the fact - if what shipped doesn't match what the spec promised, that gap shows up in the diff.
The git history mirrors the process. The PRD is committed before the feature exists, updated as discovery lands, and flipped to Shipped when the feature goes live. The changelog inside each document maps one-to-one to the commits that built it.
Published artifacts
One entry per feature. Status moves from Draft to Shipped; the document stays up afterwards as the feature's living record.
Context
Who writes these documents?
bitsARK is built solo by Ricardo Delfino. The research that feeds these specs is published on the site as well.