Bootstrap one metered owner cycle against a pinned standalone runtime
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:
tegwick 2026-09-09 22:56:38 +02:00
parent 3e4c976090
commit 565b07716a
11 changed files with 664 additions and 2 deletions

View file

@ -765,3 +765,29 @@ protected runtime/CLI artifact, Railiance host/profile/consumer/custody/recovery
admission, live provider compatibility and accepted bounds/tariffs/FX, then G0 and
natural model/queue evidence. No protected runtime was installed or promoted,
no existing CCR changed, no secret read or paid execution took place.
### Explicit one-cycle owner bootstrap and installed-candidate proof — 2026-09-09
Implemented `metered-once` with exact private policy/runtime/profile pins, explicit
exec-env key consumption outside bwrap, environment scrubbing, one claim cycle,
nonzero refusal and bounded receipt output. `--check` never claims or fetches a key.
Nineteen synthetic bootstrap tests cover invalid/changed config/artifact/schema,
missing/mixed authentication, exactly one empty/success/refused cycle and sanitized
exceptions. The existing cancellation/lease lifecycle remains in MessagesOwner.
Runtime selection passes through the trusted ephemeral sandbox binding.
The worker's source suite retains 392 passing non-native cases; the four native
cases use the exact proved 2.1.266 binary/digest. The workstation alias has advanced
to 2.1.267, which correctly fails the existing pin check; this is not a migration.
SAND-WP-0015 now supplies packaged owner definitions and a frozen-lock build mode.
Run `scripts/prove-metered-runtime.py` using the candidate's isolated interpreter;
source/receipt details live in docs/owner-bootstrap.md and the project's
`evidence/2026-09-09-owner-bootstrap.json`.
T05 remains progress and T06 wait. This supplies executable bootstrap source, not
native delivery acceptance. SECRETS-WP-0009-T03 must admit the changed credential
holder and fixed child command through the existing action/consume/backend gates.
The current catalog/CCRs, live credentials, profile readiness, host service and
factory queue remain unchanged. Protected placement, provider bounds/tariffs/FX,
G0 and natural execution remain. Per-run acquisition for a future continuous worker
is retained here; a delivered key must not authorize an unbounded daemon lifetime.