NDO creation
Creating an NDO commits the Layer 0 identity anchor. Three of its four choices are permanent, and the form is the only place a participant is told what they mean.
Why creation is group-scoped
The hierarchy is Lobby → Group → NDO. A group is a cloned DNA cell with its own DHT; an NDO created inside one is soft-linked from that cell. A global create flow would have nowhere to put the result.
So /ndo/new exists only to redirect: if a group is
selected it bounces there, and otherwise it explains. In production the explanation is
almost never seen, which is why the current app replica always renders it.
Permanent versus mutable
| Field | After creation | Why |
|---|---|---|
| Name | permanent | It is how the network refers to the object. |
| Property regime | permanent | It constrains which governance rules are valid at all. |
| Resource nature | permanent | Rivalry and governance defaults follow from it. |
| Lifecycle stage | transitions | The only field the object is meant to move through. |
| Description | editable | Prose, not identity. |
Open question
Nothing in the form says the first three fields are permanent. The regime hint explains what Commons means, not that you cannot change your mind. A duplicate name is a warning; an irreversible regime is silent.