GIOS Studioalpha · read-only
Broker authorized
Broker decision — HOW is this authorized request brokered? Fail-closed verification of the ApprovalToken, capability plan, BINDING policy allow, vault references, and scope binding. A single-use grant is issued only on brokered; it authorizes nothing to execute here — only the future Provider Execution runtime (V4) consumes it.
brokeredbinding: truetoken consumed0 vault refsgrant issued#fd754ec0
approval token:apptoken:appr-evidence-okbinding policy:policy:eval-research-allowcapability:capperm:emb-a-fs
Verification reasons (fail-closed)
brokeredpass
authorized token valid + unexpired + unconsumed; binding policy allow matches the plan profile; vault refs releasable; scope bound — execution brokered to the Provider Execution runtime (V4)
Broker grant & provider handoff (V4 readiness only)
BrokerGrant
idbrokergrant:brk-authorized
approval tokenapptoken:appr-evidence-ok
scope hash4219ad7d
binding / single-usetrue / true
issued / expires (ordinal)100 → 105
executed / dispatchedfalse / false
ProviderExecutionHandoff → V4
ownerfuture-provider-execution
capability kindsfilesystem
vault release refs—
steps (planned, undispatched)1
provider refdeferred
The grant is what the future Provider Execution runtime (V4) requires before any provider executes. It is single-use, scope-bound, binding, and unexecuted — it is not execution.
Request inputs
execution reasonbroker brk-authorized
consumed approvalappr-evidence-ok
binding policy ref (M41)policy:eval-research-allow
execution intent (M50)—
brokered at ordinal100