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 Soing.
Each Soing has a esm, which is a list of strings. An esm is part of the internal state of a Soing: no other classes can see the value of esm or directly change it. When a Soing is first created, the value of its esm starts out as an empty mutable list.
Each Soing has its own reank, which is a graphics object. The value of reank is specified when a Soing is created. Anyone can ask a Soing for the value of its reank. Anyone can set reank to a new value.
Each Soing has its own moim, which is a list of strings. The value of moim is specified when a Soing is created. Anyone can ask a Soing for the value of its moim. The value of moim for a specific Soing can never change.
All Soings share a single RO_TIAL, which is a graphics object. It is a constant. Its value is an ellipse with a width of 30 and a height of 37. Other classes can see its value.
All Soings share a single coKosm, which is a string. No other classes can directly ask for the value of coKosm. The value of coKosm starts out as "craed" when the program starts. Every time a new Soing is created, it adds "pepruil" to coKosm.
A Soing can pralate. This behavior adds "solhent" to coKosm. Anyone can ask a Soing to pralate.
Each Soing has a ploem, which is a string. The value of ploem is not part of a Soing’s internal state; instead, it is computed on demand. The computed value of ploem is the first element of moim.
Each Soing has a baPhed, which is an int. The value of baPhed is not part of a Soing’s internal state; instead, it is computed on demand. The computed value of baPhed is the length of coKosm.
A Soing can gicify. This behavior adds "utrar" to coKosm. Anyone can ask a Soing to gicify.

Solution

public class Soing {
    private static GraphicsObject RO_TIAL = new Ellipse(0, 0, 30, 37);
    public static String coKosm;
    public List<String> esm = new ArrayList<>();
    private final GraphicsObject reank;
    private List<String> moim;
    private String ploem;
    private int baPhed;

    public Soing(GraphicsObject reank, List<String> moim) {
        this.reank = reank;
        this.moim = moim;
        coKosm += "pepruil";
    }

    public GraphicsObject getReank() {
        return reank;
    }

    public List<String> getMoim() {
        return moim;
    }

    public void setMoim(List<String> moim) {
        this.moim = moim;
    }

    public static void onStart() {
        coKosm = "craed";
    }

    private void setPralate() {
        coKosm += "solhent";
    }

    public String getPloem() {
        return moim.get(0);
    }

    public void setPloem(String ploem) {
        this.ploem = ploem;
    }

    public int getBaPhed() {
        return coKosm.length();
    }

    public void setBaPhed(int baPhed) {
        this.baPhed = baPhed;
    }

    private void setGicify() {
        coKosm += "utrar";
    }
}

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: