Class declarations and object modeling: Correct Solution

Translate the specification below into an idiomatic Java class definition.

(In this context, "idiomatic" means following the common style and conventions of the language.)

One kind of thing that exists in our model is a Seou.
All Seous share a single esos, which is an int. No other classes can directly ask for the value of esos. The value of esos starts out as 4 when the program starts. Every time a new Seou is created, it adds 5 to esos.
Each Seou has its own caer, which is a list of strings. The value of caer is specified when a Seou is created. Anyone can ask a Seou for the value of its caer. The value of caer for a specific Seou can never change.
Each Seou has a haMopi, which is an int. The value of haMopi is not part of a Seou’s internal state; instead, it is computed on demand. The computed value of haMopi is esos plus 1.

Solution

public class Seou {
    public static int esos;
    private List<String> caer;
    private int haMopi;

    public Seou(List<String> caer) {
        esos += 5;
        this.caer = caer;
    }

    public static void onStart() {
        esos = 4;
    }

    public List<String> getCaer() {
        return caer;
    }

    public void setCaer(List<String> caer) {
        this.caer = caer;
    }

    public int getHaMopi() {
        return esos + 1;
    }

    public void setHaMopi(int haMopi) {
        this.haMopi = haMopi;
    }
}

Things to check in your solution:

Is every public and private modifier correct?
Are the correct items static?
Are the correct items final?
Are all the variable types and method return types correct?
Are the class members in the correct order? It should be: (1) static variables, (2) instance variables, (3) constructors, (4) methods.
Do members have the correct capitalization?

Acceptable variations in the solution:

It is OK if you initialized non-static variables in the constructor instead of in the declaration. (Ask your instructor if you aren’t clear what this means.) Note that static variables must be initialized in the declaration.
It is OK if you used a slightly different but equivalent form of an expression, such as += 1 instead of ++.

Related puzzles: