Skip to content

docs: resolver-path user-task assignment - #17

Open
delchev wants to merge 1 commit into
mainfrom
docs/assignee-path
Open

docs: resolver-path user-task assignment#17
delchev wants to merge 1 commit into
mainfrom
docs/assignee-path

Conversation

@delchev

@delchev delchev commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Renders the spec change proposed in IntentFile/intent-specification#18.

A user task's assignee now also takes a relation walk off the trigger record:

assignee: { path: employee.manager, fallback: manager }
  • /spec/processes — the construct under Task assignment: every segment a to-one relation, the walk ending at an identity-declaring entity, a cross-model relation only as the last segment, read-time hop validation, and the required fallback that leaves an unresolved walk's task to the candidate group instead of minting one nobody can see. Also notes it resolves when the task is reached, not when the process starts.
  • /spec/surfaces — the identity paragraph now names the walk beside assignee: personal.
  • /reference — index row added; the "Arbitrary resolver-path task assignment" planned entry removed.

Implementation: eclipse-dirigible/dirigible#6738.

A user task's `assignee` accepts a relation walk off the trigger record
beside a role name and the `personal` literal. Documents the walk grammar
(to-one segments, an `identity`-declaring terminal, cross-model only as the
last hop), the read-time hop validation, and the required `fallback` that
keeps an unresolved walk's task claimable rather than invisible.

Removes the matching entry from the reference's Planned list and adds the
index row.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant