TASK → RESULT → ACCEPTANCE
They said “done”.
Check the outcome.
The executor reports. The customer checks. The outcome is accepted. Try the journey, then define acceptance criteria for your own task.
Restore internet in the office
Product prototype- Work
- Result
- Acceptance
Viewing asExecutor
The executor says “done”
Can a task be closed on that statement alone? Try it.
Checks represent a person’s decision. NEXUS does not automatically establish that the report is true.
Action feedback will appear here
Write your own result
Actions in this tab
- No actions yet
How this relates to NEXUS Core
This public example runs locally and is not connected to Core. The server acceptance implementation exists separately. P-204 explains shared process state and transition rules; it does not share an operational session with this example.
P-204 technical scenario ↗Define your own task
Specify a different executor and reviewer, and 1–6 acceptance criteria. Data stays in this tab.