Bill Splitter
Split a euro bill equally among numbered people, distributing leftover cents in order.
Selected release bill-splitter-v1 · Spec v1.0.0 · App details (JSON)
What it supports
- Bill amount in euros from 0 to 1,000,000 inclusive. Use ASCII digits, an integer part, and optionally a dot followed by one or two digits.
- Number of people from 1 to 100 inclusive, written as an integer with ASCII digits.
- An integer part starts with 1 through 9 or consists of the single digit 0. Reject blank values, extra leading zeros, whitespace, signs including negative zero, exponents, grouping and decimal commas.
- Display one ordered share per person as Person N: € followed by the amount with exactly two decimal digits, a dot and no grouping.
- Use exact integer cents. Divide the total cents by the headcount, give the quotient in cents to everyone, then add one cent to each of the first remainder people. The total is preserved and no two shares differ by more than a cent.
Examples
- 10.00 euros and 3 people → Person 1: €3.34, Person 2: €3.33, Person 3: €3.33
- 0.02 euros and 4 people → Person 1: €0.01, Person 2: €0.01, Person 3: €0.00, Person 4: €0.00
- 0 euros and 2 people → Person 1: €0.00, Person 2: €0.00
Exclusions
- Unequal shares
- Currencies other than euros
- Accounts and saved bill history
Declared data handling
Amounts and headcounts are used in the current browser view. The app does not persist input or transmit it. The hosting provider receives requests for static assets.
Release evidence
Artifact 89a235258956b8a3d727459605319b692f3cea3a1d41c57f6525b63ee787e2de
Full spec (JSON) · Artifact manifest (JSON) · Source code (restricted repository access)
- Behaviour tests – passed
- Built app browser cases. .
Covers the listed cases. Results are scoped to this artifact. Behaviour tests record (JSON)
Tools: node 24.22.1, playwright 1.65.1, chromium 153.0.8010.0
- Local built-byte observations only; hosting and security review are unassessed
- Hosted observation – passed
- Hosted browser cases, bytes, headers and routing. .
Point-in-time observations for this deployment. Hosted observation record (JSON)
Tools: node 24.22.1, playwright 1.65.1, chromium 153.0.8010.0
- Public served bytes, effective policy and browser cases only. Deployment metadata is operator-observed.
- Dependency review – not_assessed
- No dependency review is included.
- Source and data-flow review – not_assessed
- No source or data-flow review is included.
- Provenance – maintainer_reported
- Recorded source and contract commits. . Recorded identities do not provide independent attestation. Provenance record (JSON)
Requirement results
- BILL-INPUT Provide editable text fields with the accessible names Bill amount (€) and Number of people, and a button named Split bill. Preserve the submitted field text for validation, with no silent trimming, rounding or rewriting. – passed (BILL-01, BILL-05, BILL-06, BILL-08, BILL-11)
- BILL-VALIDATION Validate both fields on submission using the documented grammar and bounds. For an invalid field, expose its invalid state and associated guidance explaining its accepted format and range. Announce a visible error identifying the field. – passed (BILL-06, BILL-07, BILL-08, BILL-09, BILL-10)
- BILL-CENTS Produce one share per person in an accessible ordered HTML ol list in a region named Split result. Each list item identifies that person and their exact share. Follow the cent allocation and display constraints. – passed (BILL-01, BILL-02, BILL-03, BILL-04, BILL-05)
- BILL-SUBMIT Show results only after a valid submission. Editing alone does not recalculate. An invalid submission clears the previous result, and a corrected valid submission clears the error and shows the new result. – passed (BILL-10)
- BILL-ACCESS Allow keyboard navigation from amount to people to Split bill and button activation from the keyboard. The form and results fit a 360 CSS pixel viewport without horizontal scrolling. – passed (BILL-11, BILL-12)
- BILL-LOCAL Only static assets load on navigation. Editing, submitting and viewing results do not cause network requests, store data in browser persistence, or require names or account details. Reloading clears the form and results. – passed (BILL-13)