Skip to content

docs(runtime): specialize isolation plan for OCI #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pigbibi merged 1 commit into from
Aug 23, 2026
Merged

docs(runtime): specialize isolation plan for OCI #164

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/operator_runbook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,14 @@ and rollback fence are documented in
informational until a separately reviewed live cutover is approved; the current
runtime remains authoritative.

The current host is operator-attested as a user-owned Oracle Cloud Compute
instance. The preferred future boundary is a separate on-demand OCI instance
launched from a pinned custom image, registered as a one-job JIT runner, routed
from a private subnet through an OCI NAT gateway with a reserved public IP, and
terminated with its boot volume after durable evidence. This is a migration
decision only: no OCI resource, Vault secret, allowlist entry, or live route has
been created or changed.

Before selecting a replacement host, manually run `Runtime Isolation Host
Profile`. It has repository read permission only, receives no GitHub environment,
OIDC token, or secret, and writes a redacted artifact. Provider or network fields
Expand Down
Loading