Refine stewardship evidence and specify owner preparation handoffs
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e782-9f45-7382-afff-77ad665b88ec
This commit is contained in:
parent
fdbf8bf9d1
commit
3bd576990b
12 changed files with 708 additions and 40 deletions
|
|
@ -100,3 +100,18 @@ precheck, **not the whole G6 gate**. Before G6, extend it with reviewed per-loca
|
|||
historical dispositions and the accepted runtime/package inventory, then prove
|
||||
GitOps recovery and fresh pulls/reschedules under the owner execution records.
|
||||
Do not change `g1_complete` or `approved` merely to obtain a green check.
|
||||
|
||||
## Follow-up review
|
||||
|
||||
[Owner evidence contract](owner-evidence-contract.md) specifies the sanitized
|
||||
export needed from an authorized forge owner. [Owner follow-ups](owner-followups.md)
|
||||
link stable work-record IDs, the 52-row workload review queue and all 326 excluded
|
||||
source items. Four pinned submodules still reference the old forge endpoint;
|
||||
wiki/issue-facade identity reconciliation remains open.
|
||||
|
||||
A further consecutive pair also failed stability: hub-core changed between runs.
|
||||
`stability-retry.json` records hashes and the changed fields as a diagnostic
|
||||
receipt; temporary full retry outputs were not retained as accepted evidence.
|
||||
The original full snapshots and comparison remain unchanged. No credential retry
|
||||
was made after the policy denial; the existing owner records explain where to
|
||||
resolve caller binding without substituting another workload's identity.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue