---
title: How ChowChirp keeps numbers trustworthy
description: Why every figure traces to a stamped entry, why corrections never overwrite, why the product says what a number is based on, and why it refuses to guess.
order: 1
updated: 2026-09-16
keywords: trust, audit trail, append-only, confidence, honesty, corrections
---

Restaurant software lives or dies on whether the owner believes the numbers. ChowChirp is built around four habits that make a number defensible.

## 1. Every fact is a stamped entry

When someone approves an invoice, counts a shelf, clocks a shift or logs a fridge reading, ChowChirp records an entry with the person, the time and the details. Screens are built by reading those entries. That is why every figure is a link: click it and you reach the entries behind it, and behind them the invoice photo, the count or the person.

## 2. Nothing is edited in place

Entries are append-only. A correction is a new entry that references the one it corrects, and the screen shows the corrected value with its history. This is the opposite of a spreadsheet, where a cell can be changed by anyone with no trace. It also means "what was true on the 14th, and who changed it" is a question the product can answer directly.

## 3. Every number says what it is based on

A stock balance shows a confidence badge: high, medium, low or unknown. Open it and it explains itself: last physical count three days ago, recipe mapping 91%, and which count would raise it. An export declares its renderer version, its confidence basis and the fields it redacts. A forecast shows a range, not a single line, and appears only once there is enough history. When the product does not know, it says _unknown_ rather than showing a blank or a guess.

## 4. The product refuses to guess

Several places deliberately show nothing rather than something plausible:

- The dashboard sales tile shows a figure only when the outlet declared ChowChirp's own counter as the source of sales. It will not infer sales from an external POS export.
- An action's outcome is named for the fact that happened: _Kitchen accepted_, _Receipt printed_. It never says _Success_ when it only knows _request sent_.
- Food-safety readiness lists the specific gaps to close, so a summary number never stands in for the work.
- Finance screens say _recorded_ when something was recorded and _sent_ when it was sent, and never label a submission _validated_ unless the authority validated it.

## What this means for you

You can hand a number to your accountant, your partner or an inspector and show where it came from. You can find out who changed what without an investigation. And when the product is unsure, you will know, which is the moment to count, check or ask.

## Related

- [Trace a number in the audit explorer](/docs/how-to/trace-a-number)
- [Statuses and outcome labels](/docs/reference/statuses-and-outcomes)