Version everything
Readings, mappings, tariffs, methods, estimates, approvals and corrections remain effective-dated and replayable.
Trust and methodology
A result is only useful if it can be explained, replayed and challenged.
The product is designed around evidence boundaries: what was measured, what was assumed, who approved it, what changed and which party was responsible.
Use exact arithmetic
Money uses decimal or integer minor units. Energy uses fixed precision. Rated charges never depend on binary floating point.
Separate preparation and release
Four-eyes approval protects live billing runs. The maker cannot approve their own sensitive result.
Keep estimates visible
Fallbacks are pre-approved, scoped and disclosed. Late actuals produce linked corrections rather than silent replacements.
Minimise private data
UnitCurrent uses opaque account and unit references where possible, with private objects and short-lived audience-bound access.
Name partner responsibility
Metering, vending, collections, field work and professional opinions remain attributed to their contracted providers.
Responsibility stays explicit
One workflow does not mean one party owns every act.
Scheme / property authorityMethod, tariff posture, release and resident authority
UnitCurrentQualification, reconciliation, workflow, evidence and contracted operations
Named partnersMeter APIs, vending, collections, installation and field response
Professionals / authoritiesLegal, regulatory, metrology and engineering determinations
Pre-launch boundary