docs: confirm Anthropic key custody and remaining runtime gates
All checks were successful
ci / validate (push) Successful in 2m3s
All checks were successful
ci / validate (push) Successful in 2m3s
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0726e-5232-73f2-aaca-2c05ceb62efb
This commit is contained in:
parent
39e9562802
commit
13027544f4
3 changed files with 29 additions and 2 deletions
|
|
@ -93,8 +93,11 @@ selection. Authentication lane, credential delivery/revocation, provider egress,
|
|||
pinning the Claude executable, and deployed profile review remain open. The
|
||||
credential catalog has no matching Anthropic/Claude workload lane; the user selected a dedicated Anthropic workload API key. See
|
||||
[the concrete custody proposal](../docs/anthropic-workload-key.md) and owner
|
||||
CCR-2026-0016 (in flight). Organization/budget, protected custody writer and
|
||||
verified machine binding remain outstanding; no key has been created.
|
||||
CCR-2026-0016 (in flight). Organization/key metadata is supplied and the user saved the key in OpenBao.
|
||||
A metadata-only owner check confirmed live version 2 on 2026-09-05, without
|
||||
reading the value. Custody handoff is complete. Verified machine binding,
|
||||
protected runtime delivery, workspace scope/budget and provider egress remain
|
||||
outstanding; provider authentication has not been tested.
|
||||
See docs/local-profile-acceptance.md.
|
||||
|
||||
## Review and validate the versioned Glas proof candidate
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue