Protocol documentation · v0.9
The protocol,
in the open.
Working documentation for the Colombo pilot. Written for drivers, passengers, regulators and anyone who wants to check the machinery rather than trust the mood board.
01 / ARCHITECTURE
Architecture, at a glance
Lemon is an event-sourced ride protocol. The interface is thin; the invariants and the ledger do the real work. A ride is a state machine with a public receipt at every transition.
2D invariants
Rules enforced at match and settlement time. The fee cannot become a function of the fare.
Event tape
Hash-chained, guardian-tagged events. No state change is silent.
Settlement conservation
Passenger debit equals driver credit plus transparent pass-through costs.
Observation port
The Observatory reads through a provider port; panels do not depend on the engine.
02 / WHITEPAPERS
The thinking underneath
Lemon is built on the Dimensional Ontology Framework (DOF-v2), a systems framework for keeping human sovereignty visible across economic and technical design.
03 / DRIVER WELFARE
Colombo driver welfare guidelines
No loss-making dispatch. The metabolic floor is a hard constraint. Fuel, depreciation, maintenance and a living wage are covered before any offer is made.
Rest is free. An inactive day costs LKR 0. There is no shift, quota, streak or minimum-hour requirement.
Refusal is not a metric. The data model does not contain an acceptance-rate or cancellation-rate variable. There is nothing to punish.
Settlement dignity. LankaQR/CEFTS payouts are direct. A 7-day grace period exists if cash is short; access to the tool is not held hostage.
Compassion is allowed. The Good Samaritan waiver settles a ride at LKR 0 and is logged as a community gift, never as a penalty.
04 / PASSENGER CHARTER
What a passenger can expect
A fair, upfront fare
The price is shown before request, built from real operating costs. No mystery multiplier.
Safety by default
Plate match, live trip sharing and a one-tap SOS — not paid add-ons.
Every rupee accounted for
The receipt shows the driver's share, any surplus, and exactly what Lemon keeps.
The gift is real
If a driver waives a fare in an emergency, it is a logged act of solidarity, not a glitch.
05 / SAFETY
Safety & SOS policy
Safety is a protocol concern, not a growth funnel. The pilot ships with verified plate matching, in-trip sharing and a one-tap SOS path to the emergency contact and local response partners. Trip data is minimised, access-logged and retained only as long as needed for safety and audit.
Emergency note · if you are in immediate danger, call Sri Lanka emergency services on 119 (Police) or 1990 (Suwa Seriya ambulance). Lemon's SOS is a supplement, not a replacement.
06 / REPOSITORY
Repo status
The pilot codebase is currently maintained in a private working branch while identity and settlement integrations are hardened. Public protocol artifacts and invariant audit surfaces are exposed through the Observatory. A public mirror is planned after the Colombo cohort security review.
07 / FRAMEWORK
Dimensional Ontology Framework
DOF-v2 is the design grammar behind Lemon: a way of keeping substance, metabolism, rules, configuration, dialectics and reflexive practice legible in one system. In practice, it means the fare cannot be separated from the human cost of producing it, and the books cannot be separated from the people who live with the consequences.
The framework is not a brand. It is a constraint against the usual shortcut: optimising the interface while hiding the extraction.
08 / STATUS
Colombo pilot status
09 / PRIVACY & TERMS
Privacy, plainly
This marketing site does not send registration data to a server. The registration preview stores your details in your browser's local storage so you can see how the pilot onboarding flow works. The production pilot will use a separate, consent-based registration process.
Pilot terms. Lemon is in pre-launch. Fares, fees and availability described on this site reflect the Colombo pilot design and may change before general availability. The protocol invariants are the non-negotiable part; the rest is operational detail.
Documentation v0.9 · last reviewed 12 Nov 2026
Inspect the books
Documentation v0.9 · last reviewed 12 Nov 2026