Whether a node resolves without a caller: yes — engine machinery alone
(the cascade plus the host's effect drain/ticker) gets it there; no —
someone outside the engine must act (a caller fires an action, an editor
writes a field or content); conditional — it may resolve either way
depending on values the analysis can't see (start-time seeds, mixed
alternative routes, unresolvable children, cyclic gates).
yes still leans on the host: effects settle only if a drain runs, and
time only passes for a ticker. A cascade-fired action's roles pin is a
DEPENDENCY, not an assumption — the runtime leaves a pinned trigger armed
until a capable token cascades, and whether the deployment's tokens fulfil
the pin is configuration the analysis can't see, so a pinned trigger
reports conditional with the pin as its wait.
Whether a node resolves without a caller:
yes— engine machinery alone (the cascade plus the host's effect drain/ticker) gets it there;no— someone outside the engine must act (a caller fires an action, an editor writes a field or content);conditional— it may resolve either way depending on values the analysis can't see (start-time seeds, mixed alternative routes, unresolvable children, cyclic gates).yesstill leans on the host: effects settle only if a drain runs, and time only passes for a ticker. A cascade-fired action'srolespin is a DEPENDENCY, not an assumption — the runtime leaves a pinned trigger armed until a capable token cascades, and whether the deployment's tokens fulfil the pin is configuration the analysis can't see, so a pinned trigger reportsconditionalwith the pin as its wait.