Reconcile completed evidence and block remaining external acceptance
Some checks failed
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Has been cancelled

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e72b-466d-75c0-b550-2474a3be5f36
This commit is contained in:
tegwick 2026-09-28 10:43:27 +02:00
parent dda7aa6a46
commit 62192028d6
8 changed files with 454 additions and 16 deletions

View file

@ -4,12 +4,12 @@ type: workplan
title: "Adopt concrete OpenBao credential lanes from ops-warden"
domain: infotech
repo: secrets-engine
status: active
status: blocked
flavor: implementation
owner: codex
topic_slug: custodian
created: "2026-08-21"
updated: "2026-09-27"
updated: "2026-09-28"
state_hub_workstream_id: "31f7f8ea-7f73-516c-8877-f03a13f1db82"
---
@ -436,3 +436,13 @@ SECRETS-WP-0008-T02 are now closed against that real evidence and current
regression coverage. T05 remains open for the other lanes; T06 retains
per-lane routing/proxy retirement and the npm custody discrepancy. No broader
recipient, proxy retirement, or production action is inferred from that receipt.
## Loose-end review — 2026-09-28
Reviewed all remaining tasks against the native OpenRouter acceptance and current
Glas receipts. T05 still requires acceptance for the other catalog lanes; T06
still requires owner-agreed proxy retirement and platform custody disposition
of the npm pointer. No remaining task is independently completable in this repo.
Both tasks remain wait; the workplan is now blocked. Existing accepted actions
are not authority for other lanes or routing changes.

View file

@ -4,12 +4,12 @@ type: workplan
title: "Production-safe provisioning, authorization, and lifecycle hardening"
domain: infotech
repo: secrets-engine
status: active
status: blocked
flavor: implementation
owner: codex
topic_slug: custodian
created: "2026-08-23"
updated: "2026-09-27"
updated: "2026-09-28"
state_hub_workstream_id: "68a39be1-bd9c-5133-ad64-e7bca892aaf3"
---
@ -814,3 +814,12 @@ T04 is done. T07 stays wait because its per-lane acceptance includes routing and
proxy retirement, and the receipt covers only the exact OpenRouter key-check
recipient. Other lanes and cross-owner cutover remain SECRETS-WP-0006-T05/T06;
this workplan is not finished merely because the engine gate is complete.
## Loose-end review — 2026-09-28
T01–T06 implementation is complete. T07 retains the per-lane acceptance and
routing retirement in SECRETS-WP-0006-T05/T06. The shared approval service and
requester chain have already been exercised natively; those historical serving
prerequisites are resolved. Remaining gates are exact lane authority, attended
acceptance and owner-agreed cutover. T07 remains wait; workplan now blocked.

View file

@ -4,12 +4,12 @@ type: workplan
title: "Evolve the Lifecycle engine to the accepted security layer model"
domain: infotech
repo: secrets-engine
status: active
status: blocked
flavor: implementation
owner: grok
topic_slug: custodian
created: "2026-08-29"
updated: "2026-09-27"
updated: "2026-09-28"
state_hub_workstream_id: "9c9e5164-b2f5-5ea2-a557-5368d65e9fe0"
---
@ -526,3 +526,17 @@ owner records the bounded essentials review in
live registration/custody, provisioning and native refusal/revocation evidence.
No new task or workplan was created. Warden's npm no-rotation hold remains;
factory records now consume the completed generic approval and companion returns.
## Loose-end review — 2026-09-28
Closed the stale conformance-record question above by reading GH-DEC-2026-020
§4 and the published ops-warden reference. The existing checker already prints
VALIDATED_AGAINST and SCOPE before loading declarations and implements the
GH-DEC-2026-021 version detector. No durable per-repo conformance record is
required. No further implementation is needed for that note.
T06 still depends on RPF-WP-0035-T02, whose current file remains wait for live
platform service registration/custody and scoped JWT provisioning plus native
login, denial and revocation evidence. Source tenant corrections are complete.
The workplan is now blocked; no new task or workplan was created.

View file

@ -8,7 +8,7 @@ status: blocked
flavor: implementation
owner: codex
created: "2026-09-05"
updated: "2026-09-27"
updated: "2026-09-28"
state_hub_workstream_id: "40ccc3b4-d046-5a58-8649-e7935f45c974"
---
@ -49,7 +49,7 @@ synthetic exec-env transport proof passed; no real secret was read.
```task
id: SECRETS-WP-0009-T03
status: wait
blocking_reason: "Exact-profile review found installed context/output/beta mismatches. Corrected owner candidate and source catalog pin prepared with six unapproved action requests; exact Sonnet 5 synthetic target proof passes. Await reviewed host config/source installation, proof budget and FX/tariff acceptance, then attended per-lane approvals/apply/verify/delivery/revocation."
blocking_reason: "Native apply/verify and credential delivery/revocation completed; owner attempt failed on runtime launchers. Await corrected artifact admission/pins, owner reconciliation of the held EUR 10 reservation and unknown billing, and separate retry authority under REINAH-WP-0003-T05/T06."
priority: high
state_hub_task_id: "f8069c8a-ad6b-5d0b-9a36-c2326699437d"
```
@ -552,3 +552,47 @@ approval creation/consume, native apply or paid run occurred.
Validation for this correction: 498 tests passed in the full Secrets Engine suite;
the finalized exact-profile Railiance proof passed and records its script SHA-256.
### Approved installation and tool-session proposal — 2026-09-27
The user approved the configuration/code update and separately requested preparation
of the €10 tool-session proposal. Installed Secrets Engine `11cc0d5` and corrected
owner `e0d3fb84` on Railiance; exact path/hash checks, substituted-command refusal,
standalone companion refusal and backend-free owner check pass. Standing worker,
spend limits and existing ledger are unchanged; no credentials read or paid calls.
Deployment receipt: `docs/evidence/2026-09-27-metered-owner-deployment.json`.
Actual pinned CLI/profile 1.1.1/runtime b6e4e8a4 passes a synthetic two-request Bash
tool/result exchange and zero-forward underfunded refusal, with teardown and
unchanged artifact. Receipt: `../rein-aharness/docs/evidence/2026-09-27-sonnet5-tool-session-proof.json`.
The inactive proposal is `../prj-helixforge-factory/operations/metered-tool-session-proposal.md`:
EUR 10 run cap, USD 10 liability, EUR/USD 1.00 treatment, existing native USD 5
threshold/daily EUR 20/total EUR 500 retained. Two USD 4.64 holds fit. Installed
0.87 FX is below the latest observed 0.876962 reference; fresh validity/FX acceptance
is required. No new grant or paid execution is authorized by proposal preparation.
Remaining owner tasks retain their waiting status: fresh spend grant/window,
accounting continuity and replacement recipient pins; attended native per-lane
approval/delivery/revocation; then natural queue/model/tool/commit/recovery proof.
This return supersedes earlier installation-pending statements, not those gates.
## Loose-end review — 2026-09-28
The final attended outcome in
[the replacement-window packet](../docs/proposals/glas-metered-tool-renewal-20260927/README.md)
supersedes the installation and approval waits above. Reviewed the owner receipts
`rein-aharness/docs/evidence/2026-09-27-metered-terminal-delivery.json`,
`2026-09-27-metered-postflight.json` and `2026-09-27-metered-native-resume.json`.
All six exact decisions were consumed; both apply/verify lanes passed and both
exec sessions were established and successfully revoked. The owner claimed the
single queue job and closed failed at attempt 1. The runtime launchers referenced
a deleted build directory. No successful model/tool/commit acceptance is claimed.
T03 remains wait for corrected runtime admission and recipient pins, owner
accounting reconciliation (EUR 10 parent reservation held; observed billing
unknown), and separate authority for another attempt. REINAH-WP-0003-T05/T06
owns the runtime/accounting return. Previously consumed approvals must not be
replayed; absence of request rows does not prove no billing occurred. The workplan
remains blocked. Installation and native credential delivery are completed
portions of this existing task, not new work items.