The books
are open.
On purpose.
This is the audit surface of the Lemon protocol. Drivers, passengers and regulators can inspect the rules, the fee logic and the invariant checks that decide what a ride can cost.
5 / 5
invariants passing
protocol-wide
100%
fare retained
per completed ride
LKR 2,400
monthly fee ceiling
never exceeded
0
algorithmic penalties
no rate exists
01 / The constitution
Rules before
revenue.
Every invariant is enforced in code at the point of a transaction, not displayed as a promise on a marketing page. A violation cannot be settled around.
Read the fee policyMetabolic floor
PassEvery ride is checked against fuel, depreciation, maintenance and a living wage before it can be offered.
F_offer ≥ F_floorCapped utility fee
PassThe protocol fee is a flat subscription with a hard monthly ceiling. It cannot grow with the fare.
RΠ = min(100 × days, 2400)Fee decoupling
PassNo fare argument exists in the fee function. The fee is not a percentage of driver labour.
∂RΠ / ∂F = 0Attention conservation
PassThe data model contains no acceptance-rate or cancellation-rate variable. There is nothing to punish.
acceptance_rate = not foundSurge pass-through
PassAny stress payment added by a passenger is routed in full to the driver who accepted the trip.
platform_share = 0%02 / The ledger
Follow every rupee.
Preview dataset · seeded pilot data
not live passenger records.
| Event | Route | Fare | Driver | Lemon | Hash |
|---|---|---|---|---|---|
| ride.completed | Fort → Nugegoda | LKR 420 | LKR 420 | LKR 0 | 0x7f2a…e31c |
| gift.waived | Nugegoda → National Hospital | LKR 0 | LKR 0 | LKR 0 | 0x91be…7a20 |
| ride.completed | Pettah → Kollupitiya | LKR 365 | LKR 365 | LKR 0 | 0xb042…c9d1 |
| fee.charged | Active day · 18 | — | − LKR 100 | + LKR 100 | 0x3d8f…0b6a |
| ride.completed | Bambalapitiya → Dehiwala | LKR 510 | LKR 510 | LKR 0 | 0xc71a…4f92 |
Hash-chained · append-only · guardian-tagged
all entries consistent03 / Audit it yourself
Trust is a
reproducible result.
You should not have to believe us. Start with a fare, follow the arithmetic, and check the invariant. The protocol is designed to survive the question.
Step 01
Pick any completed trip
Start with the fare, the distance, the time and the driver's operating profile. All inputs are part of the receipt.
Step 02
Recompute the floor
Fuel + depreciation + maintenance + living wage. If the fare is below that number, the match should never have existed.
Step 03
Check the settlement
Passenger debit should equal driver credit plus any pass-through costs. Lemon's commission on the fare should be exactly zero.
The invitation