Question about new version of Content Moderation with workflow component

@timmillwood - regarding your comment in #2: "Although, I'm really confused as to the use case of having a published draft state, and also don't you think to states with the same label would get awfully confusing?"

I'm not saying I want a published draft state.
I'm saying I want one draft state (unpublished) flagged as the default revision, and one draft state (unpublished) NOT flagged as the default revision. Both of those states would have a label of Draft, but they would have different machine names.

The only question I had was for the ability to edit the machine name of a state. I was under the impression that you could NOT edit the machine name when you created a state. As long as I can edit that machine name when I create it, then I'm good. :-)

And just for clarification regarding what I'm doing, I have the following scenario - very close to what @alexpott is talking about in his example #3, but I DO need both draft states. I need both draft states, because once an item is published, I need the ability to either create a new draft while keeping the published version published, or un-publish that item and return it to draft because it was published prematurely. Here's how I've defined the states and transitions:

States
Draft (draft_default): unpublished, default revision = yes
Draft (draft_not_default): unpublished, default revision = no
Published (published): published, default revision = yes

Transitions
Keep in draft (keep_in_draft_default): From Draft (draft_default) To Draft (draft_default)
Keep in draft (keep_in_draft_not_default): From Draft (draft_not_default) To Draft (draft_not_default)
Publish (publish_default): From Draft (draft_default) To Published (published)
Publish (publish_not_default): From Draft (draft_not_default) To Published (published)
Keep published (keep_published): From Published (published) To Published (published)
Create new draft (create_new_draft): From Published (published) To Draft (draft_not_default)
Unpublish, return to draft (unpublish_return_to_draft): From Published (published) To Draft (draft_default)

It's those last 2 transitions that cause me to need 2 draft states. And since we're displaying the state of an item in various places, I want the state's label to say Draft, regardless of whether it's the default revision or not; hence the duplicate state labels.

I hope that clarifies my question (can you edit the machine name?). Sorry for any confusion.

@alexpott, I'm sorry, you misunderstood me.
In my original question, I said "...I didn't see the means by which you can edit the state's machine name when you add a state.".
I was under the impression that you could not change the machine name at the time you create that state.

I was wrong - you can.
I don't need to edit it once it exists.

Regarding my use case, can you please show me an example of how, when an item is published, I can have a choice of either creating a new draft or unpublishing an item if I only have 1 draft state.

Thanks!

@alexpott, so what you're saying is that the ability to do what I need doesn't exist at the moment.
I need it to exist in 8.2.x.
And that is why I need 2 draft states. Unless someone is planning on building some other way for me to indicate that one transition from draft to published creates a new draft, while another transition from draft to published un-publishes it and makes draft the default revision, I can only accomplish my goal by having 2 draft states.

@Sam152, I don't know what you mean by "make things easier". I don't want different terminology. As an end user, when an item is in the state labelled Draft, I don't care whether it's an unpublished version of a published item, or if it's an unpublished item that was either never published, or had previously been published and got "un-published". I want it to be called Draft.

I can "unpublish" a published item at different times during its workflow. I can also create a new draft while keeping the item published. Regardless of whether I want to create a new draft or unpublish it and put it back into a draft state, I want that state to be labeled Draft.

But let's run with your suggestion. Let's say that my "normal" workflow has these states:
Draft, In Review, Ready to Publish, Published

In your example, what states would I have?
Draft (unpublished, not the default revision)
In Review (unpublished, not the default revision)
Ready to Publish (unpublished, not the default revision)
Published (published, IS the default revision)
Recalled (unpublished, IS the default revision)

When I transition from Published to Draft, it creates a new draft while leaving the item published, because Draft is not the default revision.
When I transition from Published to Recalled, it un-publishes the item and puts it an unpublished state, because Recalled IS the default revision.
So now that i have an unpublished version in a state of Recalled, what does my workflow look like to get it published? I still need to take it through In Review and Ready to Publish before I publish the thing. But I'll need versions of those unpublished states that ARE the default revision in order to get it through the workflow. So how is your suggestion making things easier? I would have to have state labels something like "Recalled - Draft", "Recalled - In Review", "Recalled - Ready to Publish". Our users would find that very confusing. Again, they don't care whether something was previously published and then became un-published. All they care about is what state it is in at a given time: Draft, In Review, Ready to Publish, or Published.