Bootstrap one metered owner cycle against a pinned standalone runtime
Some checks failed
Governed runtime contract / contract (push) Failing after 23s
Some checks failed
Governed runtime contract / contract (push) Failing after 23s
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
parent
3e4c976090
commit
565b07716a
11 changed files with 664 additions and 2 deletions
|
|
@ -4,7 +4,9 @@ Source API: `rein_aharness.messages_owner.MessagesOwner`. The trusted host boots
|
|||
constructs it with an accepted immutable `MessagesPolicy` and an explicitly supplied
|
||||
provider key, then sets `OpsRunConfig.messages_owner`. This is an in-process owner
|
||||
capability, not a queue field, serialized profile or remote sandbox API parameter.
|
||||
The normal CLI does not acquire a key or construct an owner. Set
|
||||
The normal claim-loop CLI does not acquire a key or construct an owner. The explicit
|
||||
[metered-once bootstrap](owner-bootstrap.md) now supplies the one-cycle exec-env
|
||||
child path; native delivery still needs admission. Set
|
||||
`AGENT_HARNESS_REQUIRE_REQUEST_ADMISSION=1` in a future admitted service so a missing
|
||||
bootstrap refuses before claiming work. Parent spend admission must also be configured;
|
||||
provision the RequestLedger schema explicitly before dispatch. No live bootstrap or
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue