docs(hcg-runbook): refresh rollout runbook v0.1→v0.2 after Phase D close (standards#100)#207
Merged
Merged
Conversation
…ards#91 / #100) Refreshes docs/integration/hcg-tier2-rollout-runbook.md from v0.1 (draft, 2026-05-20, pre Phase-D) to v0.2 reflecting the current state of the single-lane channel rooted at standards#91: - §1.1 Phase D deliverables: tick D-1..D-3 + D-4 bootstrap with http-capability-gateway PR refs (#12 / #14 / #22 / #26 / #30) and the boj-server D-1 load-profile (#168) that joint-closed standards#99 on 2026-06-01. The one remaining open item is the owner-driven perf-rebaseline workflow dispatch + `_status: scaffold-placeholder -> active` flip; called out explicitly rather than left as a stale unchecked checkbox. - §1.4 BoJ-side prereqs: tick the three loopback-bind layers (#130 / #131 / #132), the Phase C TrustPolicy clause (#106), the NetworkPolicy (#173), and the SSE-route policy coverage (#165). The Trustfile `tier_2_gateway.status: PENDING` line stays intentionally unchecked - it's the §6.4 last-action target. - §1.5 Gateway-side prereqs: tick the new `container/gateway-deploy.k9.ncl` from http-capability-gateway#38 (2026-06-03), record what stays PLACEHOLDER until cerro-torre signing runs, and expand the smoke-test entry with the concrete allow/deny sequence boj-server#165 deferred. - Header banner: replace the stale "Phase D has merged the scaffold only" Phase-D-dependency note with a current-state summary, bump version 0.1 -> 0.2, date 2026-05-20 -> 2026-06-08. - CHANGELOG.md: Documentation entry under [Unreleased] summarising the refresh. No code, infrastructure, or runtime behaviour changes. The runbook is the operator-facing source of truth for what's gating the next Phase E owner action; the drift it had was making "what's still open" harder to read at a glance. Refs hyperpolymath/standards#91 Refs hyperpolymath/standards#100 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
🔍 Hypatia Security ScanFindings: 272 issues detected
View findings[
{
"reason": "Stale AI session file -- delete",
"type": "stale",
"file": "GEMINI.md",
"action": "delete",
"rule_module": "root_hygiene",
"severity": "medium"
},
{
"reason": "Action if: always()\n uses: actions/upload-artifact@ea165f8 needs attention",
"type": "unpinned_action",
"file": "e2e.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Action perpolymath/standards/.github/workflows/governance-reusable.yml@main\n needs attention",
"type": "unpinned_action",
"file": "governance.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in abi-drift.yml",
"type": "missing_timeout_minutes",
"file": "abi-drift.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in container-publish.yml",
"type": "missing_timeout_minutes",
"file": "container-publish.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes
docs/integration/hcg-tier2-rollout-runbook.mdfrom v0.1 (draft, 2026-05-20, pre Phase-D) to v0.2 reflecting the current state of the single-lane HCG tier-2 channel rooted atstandards#91. Documentation-only PR — no code, no infrastructure, no behaviour change. The runbook had visible drift across three sub-sections of §1 (Prerequisites) since Phase D (standards#99) closed on 2026-06-01 and gateway E1 (deploy spec) landed on 2026-06-03; this PR ticks the boxes that have evidence and calls out exactly what's still open.Refs hyperpolymath/standards#91Refs hyperpolymath/standards#100Channel position
What changed
docs/integration/hcg-tier2-rollout-runbook.mdHeader banner.
0.1 (draft, Phase E first cut)→0.2 (post Phase-D close, Phase E in-progress).2026-05-20→2026-06-08 (rev. from 2026-05-20)._statusflip). The old admonition still claimed "Phase D has merged the scaffold only" — six weeks stale.§1.1 Phase D deliverables landed.
[ ]D-2,[ ]D-3,[ ]D-4 →[x]lines per phase with PR refs and dates:workflow_dispatchrebaseline onubuntu-latest) — http-capability-gateway#26 (2026-05-30).standards#99.[ ]line for the remaining open item only: owner-driven dispatch ofPerf Rebaseline+ maintainer-merge of the generatedperf: rebaseline (standards#99)PR +_status: scaffold-placeholder → activeflip. Until this lands the gate runs in non-blocking scaffold mode.§1.4 BoJ-side prerequisites.
[ ]Loopback bind →[x]enumerating the three layers that landed: Elixir Cowboy bind tightening (boj-server#130), k8s Service ClusterIP (boj-server#131), Zig-adapterAPP_HOST=127.0.0.1acrossstapeln.toml,entrypoint.sh,compose.prod.yaml(boj-server#132). Deployment-time confirmation that the staging port really is closed at the network layer stays an operator pre-check before §2.1.[ ]TrustPolicy clause →[x]with the verified line reference (elixir/lib/boj_rest/trust_policy.ex:73) and PR (boj-server#106).[x]entries for the two additional Phase-E-supporting BoJ-side landings flagged in gateway#38's channel position:Trustfile.a2ml tier_2_gateway.status: PENDINGline stays intentionally unchecked — it's the §6.4 last-action target.§1.5 Gateway-side prerequisites.
[ ]container/gateway-deploy.k9.nclexists →[x]with PR ref (http-capability-gateway#38, 2026-06-03), naming the five-level k9-svc pedigree (Snout / Scent / Leash / Gut / Muscle), per-environmentBACKEND_URL, trust-source flip pattern ("header"staging →"mtls"production after §2.4 rehearsal),max_unavailable = 0, andfailure_mode = "fail-closed"matching the[SEAMS] gateway-boj-gnosisdeclaration.[ ]Containerfile +.ctpsigning entry extended with a note thatpedigree.security.signature+pedigree.validation.checksumstayPLACEHOLDERin the k9.ncl until cerro-torre signing runs (separate operator action, key-handling discipline).cartridge-sse-postrule.POST /cartridge/:name/sseX-Trust-Level cases).CHANGELOG.mdNew
### Documentationentry under[Unreleased]summarising the refresh and pointing at the PR refs. Sits with the existing Phase E### Addedentry for the NetworkPolicy (#173) and the prior loopback-bind entries.What this PR deliberately does NOT do
Trustfile.a2ml tier_2_gateway.status. That's the §6.4 last action; flipping it before the soak windows are complete would mis-represent the deployment state.standards#100. Same channel discipline as PR chore(deps): bump nixpkgs from01fbdeeto6368eda#38 / docs(hcg-load-profile): Phase D D1 — load profile declaration (standards#99) #168 — single-lane joint-close, owner-only.gh pr viewon a merged-and-confirmed PR (verified via the GitHub MCP at preparation time).Test plan
Governance/Secret Scanner/Dogfood Gate/LSP/DAP/BSP CI/Hypatia Security Scan/CodeQL Security Analysisall pass — they're green onorigin/mainand this is a docs-only diff that touches no workflow input.OpenSSF Scorecard Enforcer,Scorecards supply-chain security,Instant Sync) — known failures onorigin/mainunrelated to this PR. Same status before and after.01fbdeeto6368eda#38, confirm each is the cited PR.grep -n 'tier_2_gateway:' .machine_readable/contractiles/trust/Trustfile.a2ml→897: tier_2_gateway:so thestatus:field is line 900). Confirmed at PR-creation time.🤖 Generated with Claude Code
Generated by Claude Code