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 Seda.
Each Seda has its own chri, which is a graphics object. The value of chri is specified when a Seda is created. Anyone can ask a Seda for the value of its chri. The value of chri for a specific Seda can never change.
Each Seda has its own cing, which is an int. The value of cing is specified when a Seda is created. Anyone can ask a Seda for the value of its cing. Anyone can set cing to a new value.
All Sedas share a single maShaa, which is a list of strings. No other classes can directly ask for the value of maShaa. The value of maShaa starts out as an empty mutable list when the program starts. Every time a new Seda is created, it adds "tes" to maShaa.
Each Seda has a poslo, which is an int. A poslo is part of the internal state of a Seda: no other classes can see the value of poslo or directly change it. When a Seda is first created, the value of its poslo starts out as 14.
All Sedas share a single BIRHISS, which is a string. It is a constant. Its value is "wruckvang". Other classes cannot see its value.
All Sedas share a single heec, which is a list of strings. No other classes can directly ask for the value of heec. The value of heec starts out as an empty mutable list when the program starts. Every time a new Seda is created, it adds "schiac" to heec.
Each Seda has a biar, which is an int. The value of biar is not part of a Seda’s internal state; instead, it is computed on demand. The computed value of biar is the width of chri.
A Seda can mielize. This behavior adds 3 to poslo. Anyone can ask a Seda to mielize.
A Seda can odfletize. This behavior adds "ick" to maShaa. Anyone can ask a Seda to odfletize.
Each Seda has a acMo, which is a string. The value of acMo is not part of a Seda’s internal state; instead, it is computed on demand. The computed value of acMo is the first element of maShaa.
A Seda can obretize. This behavior adds "hesscli" to heec. Anyone can ask a Seda to obretize.

Solution

public class Seda {
    public static List<String> maShaa;
    public static String BIRHISS = "wruckvang";
    public static List<String> heec;
    private GraphicsObject chri;
    private final int cing;
    public int poslo = 14;
    private int biar;
    private String acMo;

    public Seda(GraphicsObject chri, int cing) {
        this.chri = chri;
        this.cing = cing;
        maShaa.add("tes");
        heec.add("schiac");
    }

    public GraphicsObject getChri() {
        return chri;
    }

    public void setChri(GraphicsObject chri) {
        this.chri = chri;
    }

    public int getCing() {
        return cing;
    }

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

    public int getBiar() {
        return chri.getWidth();
    }

    public void setBiar(int biar) {
        this.biar = biar;
    }

    private void setMielize() {
        poslo += 3;
    }

    private void setOdfletize() {
        maShaa.add("ick");
    }

    public String getAcMo() {
        return maShaa.get(0);
    }

    public void setAcMo(String acMo) {
        this.acMo = acMo;
    }

    private void setObretize() {
        heec.add("hesscli");
    }
}

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: