How Sumivo calculates

01 / Overview

A method before a page

A calculator is not complete because a form renders. Its method defines input semantics, normalized units, formula, output meaning, limits and error behavior before it can move through publication.

input semantics → normalized units → formula → result model → display formatting

02 / Sources

Sources are versioned records

A source record identifies the document or URL, publisher, version or date, relevant jurisdiction, applicability and exclusions. A search result or a competing calculator is not a source.

03 / Fixtures

Expected values are independent

Fixtures are derived manually, calculated in an independent reference, or reconciled against an authoritative example. The same implementation under test does not generate its own expected values.

04 / Tests

Boundaries and invariants matter

Tests cover invalid inputs, unit equivalence, monotonic relationships, round trips and display boundaries—not only a single happy path.

capacity increases ⇒ runtime cannot decrease
load increases ⇒ runtime cannot increase
meters → feet → meters ≈ original value

05 / Review

Claims require evidence

Labels such as reviewed, verified, popular or trusted require a structured claim tied to evidence. Without that record, the label does not appear.

06 / Publication

One persistent publication state

The stored vocabulary is draft, qa, published and retired. Robots behavior and other publication outputs are derived with the shared content schema rather than copied into route templates.

draft

Work in progress; not ready for a production route.

qa

Preview and validation state; not eligible for indexing.

published

Eligible for normal publication outputs after gates pass.

retired

Withdrawn from active publication.

07 / Change control

Method versions remain inspectable

The interface exposes a concise method name and status. Controlled records retain the method version, source records, revision and evidence needed to evaluate a change.