coulomb/secrets-engine
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record reproducible CLI release and exact native admission requirements
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a140c4-354a-7823-8f0d-8f717397f786
This commit is contained in:
tegwick 2026-10-16 18:44:05 +02:00
parent 4dd004a225
commit 3718e60d73
3 changed files with 104 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

47
docs/proposals/native-cli-admission/README.md
View file

@ -1,5 +1,52 @@
# Native CLI signer and consumer admission preparation
## Current release preparation — 2026-10-16 R2
Published canonical Secrets `4dd004a2250104ba56293b2d7b0d96f4e076ea99` was
built twice from an isolated clean checkout. Artifacts and deterministic bundle
manifest match exactly: manifest SHA256
`sha256:105dcebe6f03e9799f91ea75175e20500df2aa7f08b5e32d39c1c367593ca47e`,
fixed helper SHA256
`sha256:ed922b62533e4d33ae2d5f11175111f6f28e684a19e63ac704d43b63f0e0e12e`.
Disposable installation/help and empty native trust refusal pass; no native
prefix, trust/key, caller credential, protected effect or rollout was admitted.
Artifact integrity is not independent package admission. Full receipts and a
concrete probe/placement proposal are in Custodian `decision-native-preparation/r2/`.
Initial native scope remains the existing lifecycle pin and **0/11 protected
sites across10 handlers**. Runtime UID/release/config/catalog/stance/trust/evidence
and scoped caller/Approval delivery paths remain owner-unselected. A concrete
workstation candidate uses a new release prefix ending
`4dd004a22501-105dcebe6f03`; it is a proposal, not an installed/admitted path.
Only its exact future `bin/secrets-engine` wrapper is the effect entrypoint.
The current repo editable invocation and ambient demo/preflight fallbacks do not
constitute release admission. A local CLI does not automatically hold the named
ServiceAccount identity: existing docs describe separately authorized per-session
TokenRequest delivery, not a standing credential or pod identity grant.
Access's single offline signer-receipt tool is published at
`2b064eee510640224274ccdc7cefceb1ae13162e`; verified API/sign source matches this
consumer. Native producer rollout still awaits independent public kid/key/custody
and immutable candidate image/log/storage returns, including the Access owner's
separate durable-log hardening review. Published source alone is not that image.
The lifecycle pin stays v2/bd11c5fe...; task v2 is a separate unadmitted pin.
Source task correspondence is now implemented and cross-owner source-server
proved: fixed typed service mapping before issue, retained-registry signed-DENY
preapproval, original claim/context preservation, independent fresh source facts,
precise Approval CAS and independent confirmation/journal/native disposable proof.
This supersedes the historical source gaps below; it neither adds an execute-ccr
CLI command nor selects a real CCR/catalogue/Plan/grant/backend/journal runtime.
All native effect, caller/key/config and task-entitlement gates remain open under
existing WP14/WP13/WP8 records. `service-jwt` still refuses protected CLI work.
## Historical ff1a13d preparation (preserved)
The following draft records the earlier source/admission observations. References
to absent B2/B3/request/source-fact implementation are superseded by R2 above;
missing native keys, runtime placement and actual task inputs remain unresolved.
This proposal covers the existing lifecycle CLI authentication path under
SECRETS-WP-0014. It grants no installation, key retrieval, caller mint, approval
consume, OpenBao effect or task-policy activation. All native acceptance counts