20
Scored criteria
across three pollution types
platform · 2025 · client unnamed
A formal pollution-scoring instrument turned into an API: georeferenced water, air and land contamination cases scored against a defined criteria set.
20
Scored criteria
across three pollution types
4 states
Case workflow
reviewed, not deleted
The problem
An environmental body assessed pollution incidents on paper using a structured scoring instrument with different criteria per contamination type. The instrument was well designed and entirely offline, so nothing could be aggregated, triaged or compared across cases.
The approach
Transcribed the instrument faithfully rather than redesigning it. The assessment is polymorphic by pollution type with three mutually exclusive criteria blocks, twenty scored criteria in total, each carrying its original name inline so the mapping between the client form and the API is never lost. Four-state case workflow where a rejected case is a reviewed case rather than a deleted one.
Architecture
Polymorphic assessment document with three embedded value-object criteria blocks, discriminated by pollution type. The criteria counts are asymmetric because the three instruments were designed independently by the domain owner.
Each with what it cost
A decision without a stated tradeoff is a preference.
01
Why
Gaseous waste is scored under water pollution because it affects water. That is a domain distinction, not a modelling mistake, and flattening the three blocks into a uniform criteria set would destroy the meaning the instrument carries.
What it costs
Three asymmetric blocks are harder to aggregate across than one uniform set, the cost of keeping the domain intact.
Outcome
The client scoring instrument works as a system: cases are filed with evidence photographs and location, then triaged through an explicit review workflow.