Unclear parent step

In the code below it is unclear to me why I would need a parent step after can-delete since it seems to me we’re still on the same node:

'Data voor VWS': stategroup = switch .'Soort verkoop' (
	|'Partij'        as $ => switch $ .'Partijtoekenningen'* .'Data voor VWS'?'Ja' (
		| nodes => 'Ja' ( )
		| none  => 'Nee' ( )
	)
	|'Niet-voorraad' => 'Nee' ( )
) @hidden (
	'Ja' { }
	'Nee' { }
)
'Is eerste regel': stategroup (
	'Ja'
		can-delete: ^ .'Data voor VWS'?'Nee' // <-- Why ^ ?!
	{ }
	'Nee' {
		can-update: ^ .'Data voor VWS'?'Nee' // Clear! Jumping out of node with state 'Nee'

		'Vorige regel': text -> ^ sibling in ( 'Volgorde regels' )
	}
)

I understand the confusion - we welcome any suggestions for improvement.
Deletion permissions may depend on values from a state node. For example:

'Is eerste regel': stategroup (
	'Ja'
		can-delete: user is ( >'State creator' )
	{
		'State creator': text -> ... .'Users'[]
	}
	'Nee' { ... }
)

The curly braces ({}) belong to the state node type, whereas can-delete belongs to the state type.
Therefore, we cannot simply move can-delete between the braces; on the language level it would not make sense.

An alternative would be a special means to navigate to the state node:

		can-delete: user is ( state-node >'State creator' )

However, this comes at the cost of a new/additional keyword that currently has no other uses in the core Alan languages.

What about:

'Is eerste regel': stategroup (
	'Ja'
		can-delete: user is ( ?'Ja'>'State creator' )
	{
		'State creator': text -> ... .'Users'[]
	}
	'Nee' { ... }
)

This corresponds with already used notation in ordered graphs:

'Order': ordered-graph .'Is first' ( ?'Yes' || ?'No'>'Next' ) // <-- ?'Yes' and ?'No'

So than my code snippet could become:

'Is eerste regel': stategroup (
	'Ja'
		can-delete: .'Data voor VWS'?'Nee' // <-- No ^ !!
	{ }
	'Nee' {
		can-update: ^ .'Data voor VWS'?'Nee'

		'Vorige regel': text -> ^ sibling in ( 'Volgorde regels' )
	}
)