stage: expose resource targets to model harnesses
This commit is contained in:
@@ -2,8 +2,10 @@
|
||||
|
||||
Stage `resources` declarations now accept exactly one of `exclusive` or `pool`.
|
||||
Pool stages wait on the named pool, then receive the selected concrete member and
|
||||
bounded metadata through explicit runtime context. The model input remains
|
||||
unchanged and capability tokens remain private to the store. Retained control
|
||||
bounded metadata through explicit runtime context. Model execution serializes that
|
||||
server-granted context as a separate `resource_target` runtime field for both
|
||||
native and plain harnesses; the task input map remains unchanged and cannot select
|
||||
the target. Capability tokens remain private to the store. Retained control
|
||||
evidence records the concrete target; queued run state names the pool while an
|
||||
active owner names the selected member.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user