Creating a session answers the same row the list publishes
A client can insert a creation response straight into its list without re-fetching, which is what makes one shared row shape load-bearing rather than tidy.
The rule
Normative: this is the rule
- Creating a session answers
201and reading one answers200, both under{success, data}, and in both casesdatais exactly the row the session list publishes in itsdata[]:id,workflowId,name,status,createdAt,updatedAt,metadata,executions,owner, in that order. owneris exactly{id, name}.createdAtandupdatedAtare ISO 8601 strings, never numeric timestamps.executionsis an empty list, not null, for a session that has never run.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · PLAY-2 · changed in spec 1.0