1. Add a non-forwarding `get_domain_override` query with no default implementation. 2. Give meaning to the `get_scheduler` query by requiring that an operation be started on an execution agent associated with the scheduler from the environment of the receiver used to create the operation. 3. Tweak the definitions of *`SCHED-ATTRS`* and *`SCHED-ENV`* to avoid forwaring the `get_domain` query. 4. Simplify the definition of the exposition-only *`completion-domain`* helper, which no longer needs a configurable default. 5. Specify that `get_domain_override(get_env(schedule_from(sch, sndr)))` returns the domain of `sch`. 6. Specify that `get_domain_override(get_env(continues_on(sndr, sch)))` returns the domain of `sndr` (if it has one). 7. Specify that `get_domain_override(get_env(starts_on(sch, sndr)))` returns the domain of `sch`. 8. The expression *`get-domain-late`*`(sndr, env, def)` should be equivalent to: 1. `get_domain_override(get_env(sndr))` if that expression is well-formed. 2. Otherwise, `get_domain(env)` if that expression is well-formed. 3. Otherwise, `get_domain(get_scheduler(env))` if that expression is well-formed. 4. Otherwise, `def`. 9. Specify that `sync_wait` and `sy