f3e8bf3ab4
`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.
Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.
The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
71 lines
2.3 KiB
Markdown
71 lines
2.3 KiB
Markdown
---
|
|
id: RAIL-HO-WP-ADHOC-2026-08-22
|
|
type: workplan
|
|
title: "Attend repository owner requests"
|
|
domain: financials
|
|
repo: railiance-infra
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: repository-owner-requests
|
|
created: "2026-08-22"
|
|
updated: "2026-08-22"
|
|
---
|
|
|
|
# Attend repository owner requests
|
|
|
|
## Review the RAILIANCE-WP-0024 host recovery contract
|
|
|
|
```task
|
|
id: RAIL-HO-WP-ADHOC-2026-08-22-T01
|
|
status: done
|
|
priority: high
|
|
```
|
|
|
|
Review the final hash-bound railiance-infra owner assertions, run the named
|
|
read-only checks, and submit the procedure-only decision without authorizing a
|
|
live reboot window.
|
|
|
|
Result: approved contract digest
|
|
`f86d418f951f829f075de04dd825c6e2e185e577019ee23d6da1fa9040302d62`.
|
|
Focused unit tests and node-reboot preflight passed read-only; receipt message
|
|
`9bbf986c-7385-42de-964f-9040eebdfee4` records that no secret values were
|
|
observed. No live window or reboot was authorized.
|
|
|
|
The durable, repository-authoritative form is
|
|
`reviews/RAILIANCE-WP-0024-T03-railiance-infra-approval.json`. State Hub
|
|
messages are notification references only; the generic review projection can
|
|
be rebuilt from the contract and this receipt file.
|
|
|
|
## Resolve the ADR publication cleanup packet
|
|
|
|
```task
|
|
id: RAIL-HO-WP-ADHOC-2026-08-22-T02
|
|
status: done
|
|
priority: medium
|
|
```
|
|
|
|
Make status metadata honest, identify the canonical source for duplicated
|
|
ADRs, and add complete publication front matter to current decisions.
|
|
|
|
Result: `railiance-infra` is the canonical source for the shared ADR-003 and
|
|
ADR-004 because `railiance-hosts` declares itself superseded by this repo.
|
|
ADR-002 is explicitly superseded; ADR-003 through ADR-005 now have complete,
|
|
globally unique `RINFRA-ADR-*` publication metadata. Policy Nexus and the
|
|
historical repo were notified of the ruling.
|
|
|
|
## Triage the proposed confidential custody transfer
|
|
|
|
```task
|
|
id: RAIL-HO-WP-ADHOC-2026-08-22-T03
|
|
status: done
|
|
priority: high
|
|
```
|
|
|
|
Check the proposed destination and confidentiality policy, then accept or
|
|
return a value-safe change request without copying restricted material into an
|
|
inappropriate repository.
|
|
|
|
Result: changes requested. Forgejo reports this repository as public, while
|
|
the complete proposed tree is `client_confidential`. No engagement material
|
|
was copied; kaizen-agentic was asked to use restricted custody or propose a
|
|
separately reviewed, redacted public-safe subset.
|