Skip to content
Hardcount
Run it locally
Pre-1.0 · one maintainer · Stripe and cards only · no SDKs (client libraries) yet · no production users yet. Docs describe v0.9.1 (29 Oct 2026) · What’s new →

Contributor docs

For people changing Hardcount itself. You do not need these pages to use or run Hardcount: the user and operator docs start at Hardcount docs.

Start here

Section titled “Start here”
  1. CONTRIBUTING: setup, tests, and what CI checks.
  2. Architecture: package layout and design rules.
  3. Money-path robustness playbook: required for any change to invoices, payments, credits, dunning, subscriptions or tax.
  4. How we test: which test to write, and how to run it. The release checklist holds the live checks run by hand before each release, and the Stripe end-to-end test has the step-by-step Stripe commands.
  5. OpenAPI workflow: changing the API contract.
  6. Writing a database migration: changing the database schema.
  7. Writing style: how to write docs here.
  8. Contributor glossary: words from the code, the database and the operations docs.
  9. AI coding agents start at Project rules at a glance.

Background

Section titled “Background”

Background for a decision, kept as written.

  • Architecture decision records (ADRs): one decision per file, with the reasons and the alternatives.
  • Design docs: the plan for each feature, written before it was built. Where a design doc and the code disagree, the code and the ADRs are the current record.
  • Records: dated audits, reviews, plans and benchmark run journals, kept as written.
  • CHANGELOG: every change, by date.