Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0
jadpo
ReferenceErrors

ErrorsEntities, stores and migrations · rule

data.lifecycle_transition_name

Transition is named like another operation or a field.

Area 5, Entities, stores and migrations; not declinable; the next step is usually the agent's.

A transition is an operation of its entity, so it can't take another operation's name or a field's:

example
entity Todo {    id: Uuid    archived_at: Instant?    lifecycle: {        transitions: {            update: {                set: {                    archived_at: clock.now                }            }        }    }}
jadpo checkcheck failed: 1 error, 1 file

error A transition can't be called update

--> main.jadpo:7:13

  |7 |             update: {  |             ^^^^^^ name in use
reason
Todo.update is already an operation every entity has, so a transition can't take its name; delete is the one a transition may take over.
next
Name the transition after the change it makes, such as archive (agent)
rule
data.lifecycle_transition_name
help
https://jadpo.dev/docs/errors/data.lifecycle_transition_name

Markdown for agents: /docs/errors/data.lifecycle_transition_name.md.Built from Jadpo main at aee2e8f.