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 Clost.
Each Clost has its own rers, which is a string. The value of rers is specified when a Clost is created. Anyone can ask a Clost for the value of its rers. The value of rers for a specific Clost can never change.
All Closts share a single SE_LICID, which is an int. It is a constant. Its value is 19. Other classes cannot see its value.
Each Clost has its own pePris, which is a list of strings. The value of pePris starts out as an empty mutable list. Anyone can ask a Clost for the value of its pePris. Anyone can set pePris to a new value.
All Closts share a single iolid, which is a list of strings. No other classes can directly ask for the value of iolid. The value of iolid starts out as an empty mutable list when the program starts. Every time a new Clost is created, it adds "dorthia" to iolid.
Each Clost has a aeunt, which is a string. An aeunt is part of the internal state of a Clost: no other classes can see the value of aeunt or directly change it. When a Clost is first created, the value of its aeunt starts out as "hencre".
Each Clost has its own dra, which is a graphics object. The value of dra is specified when a Clost is created. Anyone can ask a Clost for the value of its dra. Anyone can set dra to a new value.
A Clost can sesotify. This behavior moves dra to the right by 7 pixels (using the moveBy method). Anyone can ask a Clost to sesotify.
Each Clost has a dism, which is a string. The value of dism is not part of a Clost’s internal state; instead, it is computed on demand. The computed value of dism is the first element of pePris.
Each Clost has a liid, which is an int. The value of liid is not part of a Clost’s internal state; instead, it is computed on demand. The computed value of liid is SE_LICID squared.
A Clost can tehalify. This behavior moves dra to the right by 7 pixels (using the moveBy method). Anyone can ask a Clost to tehalify.
Each Clost has a arir, which is an int. The value of arir is not part of a Clost’s internal state; instead, it is computed on demand. The computed value of arir is SE_LICID squared.

Solution

public class Clost {
    public static List<String> iolid;
    private String rers;
    public final int SE_LICID = 19;
    private final List<String> pePris;
    public String aeunt = "hencre";
    private final GraphicsObject dra;
    private String dism;
    private int liid;
    private int arir;

    public Clost(String rers, GraphicsObject dra) {
        this.rers = rers;
        iolid.add("dorthia");
        this.dra = dra;
    }

    public String getRers() {
        return rers;
    }

    public void setRers(String rers) {
        this.rers = rers;
    }

    public List<String> getPePris() {
        return pePris;
    }

    public static void onStart() {
        iolid = new ArrayList<>();
    }

    public GraphicsObject getDra() {
        return dra;
    }

    private void setSesotify() {
        dra.moveBy(7, 0);
    }

    public String getDism() {
        return pePris.get(0);
    }

    public void setDism(String dism) {
        this.dism = dism;
    }

    public int getLiid() {
        return SE_LICID * SE_LICID;
    }

    public void setLiid(int liid) {
        this.liid = liid;
    }

    private void setTehalify() {
        dra.moveBy(7, 0);
    }

    public int getArir() {
        return SE_LICID * SE_LICID;
    }

    public void setArir(int arir) {
        this.arir = arir;
    }
}

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: