Skip to content

docs: Protecting frontier agent workloads with OpenShell - #98

Merged
zredlined merged 5 commits into
mainfrom
codex/frontier-workloads-dev-note
Nov 9, 2026
Merged

zredlined merged 5 commits into
mainfrom
codex/frontier-workloads-dev-note

Conversation

@zredlined

Copy link
Copy Markdown
Collaborator

Adds “Protecting frontier agent workloads with OpenShell,” a Dev Note on the reference architecture for long-running frontier agents on live systems. Includes the approved hero, SVG figures with titles in Markdown, links to earlier adversarial testing and policy-prover research, and a short explanation of the example integrations added through OpenShell’s existing interfaces. Includes documentation and images only.

Validation: renderer tests (11 passed), clean documentation build including rendered Markdown/navigation/SEO checks, comparison against the source text with the approved edits, and browser review in Chromium and WebKit across light/dark themes and desktop/tablet/phone widths. The final article checks passed 16/20; the four failures reproduce the existing Chromium desktop reading-width assertion on the unchanged Policy Prover article. Index and thumbnail checks also passed.

@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Documentation preview

The preview has been removed.

@johnnygreco

Copy link
Copy Markdown
Collaborator

"Accesses" vs. "permissions": the note uses "accesses" in six places, but also uses "permissions" for the same idea (for example, "grow its permissions" on line 76). Most readers treat "access" as uncountable, so "accesses" reads a little unusual. Consider standardizing on "permissions":

  • Line 70: "abuses accesses that it was legitimately granted" → "abuses permissions that it was legitimately granted"
  • Line 70: "through accesses that had already been reviewed…" → "through permissions that had already been reviewed…"
  • Line 76: "the agent's accesses near zero" → "the agent's permissions near zero"
  • Line 100: "propose new accesses through the Policy Advisor" → "propose new permissions through the Policy Advisor"
  • Line 110: "start the agent at near zero with accesses" → "start the agent with near-zero permissions"
  • Line 104: "give powerful, possibly hostile processes accesses to things they can misuse" → here "access to things" reads better than "permissions to things"

Not blocking. Feel free to keep "accesses" if it's intentional.

@zredlined zredlined self-assigned this Nov 9, 2026
@zredlined zredlined added the documentation Improvements or additions to documentation label Nov 9, 2026
@zredlined
zredlined marked this pull request as ready for review November 9, 2026 15:51

@johnnygreco johnnygreco left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @zredlined!

@zredlined
zredlined merged commit 5def0d6 into main Nov 9, 2026
16 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants