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 Flunt.
All Flunts share a single naVioc, which is a list of strings. No other classes can directly ask for the value of naVioc. The value of naVioc starts out as an empty mutable list when the program starts. Every time a new Flunt is created, it adds "ehex" to naVioc.
All Flunts share a single CHIOC_SPLE, which is a list of strings. It is a constant. Its value is ["derbe", "tispra"]. Other classes cannot see its value.
A Flunt can esocate. This behavior adds "criocpre" to naVioc. Anyone can ask a Flunt to esocate.

Solution

public class Flunt {
    public static List<String> naVioc;
    public static List<String> CHIOC_SPLE = List.of("derbe", "tispra");

    public Flunt() {
        naVioc.add("ehex");
    }

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

    private void setEsocate() {
        naVioc.add("criocpre");
    }
}

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: