Define local motion at canonical location scale
This commit is contained in:
parent
3e8eaf4abf
commit
468aa84e16
4 changed files with 19 additions and 0 deletions
|
|
@ -186,6 +186,14 @@ canonical constituent reference set, including active reachable migration
|
|||
destinations. Scheduler slicing and wave admission consume that same
|
||||
derivation; the scheduler's private migration-destination helper was deleted.
|
||||
|
||||
That fix let the next strict run commit its preflight. In a sustained wave the
|
||||
effect verifier then called two faithful local activities reversals because
|
||||
their prose included walking to an embankment or nearby cove. The verifier now
|
||||
receives the missing spatial contract: incidental motion within the supplied
|
||||
canonical location belongs to the activity and creates no topology or arrival;
|
||||
only movement to a different supplied canonical location requires a movement
|
||||
effect.
|
||||
|
||||
The multiresolution body is deployed on Starfire. Typed health matched the
|
||||
immutable release, DeepSeek was ready, and the disposable live strategic-cell
|
||||
smoke committed three offscreen events plus three accessible news items without
|
||||
|
|
|
|||
|
|
@ -128,6 +128,11 @@ permission, or notifies an unnamed ordinary role. Both admit ordinary texture
|
|||
without inventing a listener, response, acceptance, discovered fact, or target
|
||||
agency.
|
||||
|
||||
Activity effects operate at canonical-location granularity. Incidental motion
|
||||
around unnamed local features remains part of the source-attributed attempt
|
||||
and does not create topology or assert arrival. A different supplied canonical
|
||||
location or population destination still requires the exact movement path.
|
||||
|
||||
Salient dormant members have their own `member_activity` path for ordinary
|
||||
local attempts. It uses the same bounded verbs, the member's exact location,
|
||||
their current leaf plus explicitly related or exactly co-located targets, and
|
||||
|
|
|
|||
Loading…
Reference in a new issue