Respond to human effects

A workflow creates an explicit human wait with human.confirm, human.choice, or human.form. There is no generic button that marks an arbitrary effect or transaction complete.

Respond

1. Open the waiting effect on the run page.
2. Review its frozen title, description, audience, options, or form schema.
3. Confirm that earlier effect evidence still supports the action.
4. Submit the response.

txcast records the responder, timestamp, value or option, optional note, and whether an admin override occurred. The workflow resumes with that immutable result.

Eligibility and admin override

The authored audience can be the run starter, workflow owner, any seated member, or an explicit member list. The responder must still have current organisation access. An organisation owner/admin may override another audience when the UI clearly identifies the override and the actor accepts it.

Agents cannot submit human responses, even if they can author or start the run.

Transaction recovery is separate

A transaction effect succeeds only from verified chain evidence. For an EOA wallet broadcast whose hash was not recorded, use the dedicated confirmed-hash recovery action. There is no user-supplied “external completion” escape hatch.