Pluto / OpenAI reconciliation — 2026-11-12

Scope: public Pluto Dots and Codex practical guides and their linked architecture guidance, compared with current HTH Dots, Work/Codex, Enterprise and API Platform controls. No tenant changes or live validation. Public vendor Markdown bodies were fetched this session; automation capabilities are not inferred from third-party prose.

Sources and disposition

Source Recommendation groups HTH disposition
Dots practical guide Cloud/browser/password manager; local device controls; approval rules; memory; delegation; logging 3.1–3.4, 4.1–4.4, 5.2, 6.1, 7.1–7.2 already cover the baseline. Tightened browser-session cleanup, future app-action defaults and separate reviewer/telemetry boundaries. Added explicit delegation control 2.3 and local denied-read config pack at 3.4.
Personal-assistant architecture Runtime packages; desktop credential redirection; approval/artifact binding; persistent context; cross-channel delegation Explicit dispositions below. Historical research and proposed platform guarantees are not current exploitability evidence or available admin settings.
Codex practical guide Enforced requirements; sandbox/network; browser/desktop; cloud/GitHub/API identities; tool supply chain; audit/hooks; phased rollout Work/Codex 1.1–1.3, 2.1–2.7, 3.1–3.4, 4.1–4.4 and OpenAI API identity controls already cover these. Keep current HTH corrections rather than restoring May assumptions. No additional duplicate Codex pack warranted.

Dots detailed coverage

Personal-assistant architecture: full recommendation disposition

The article body was read through its conclusion, including its three execution zones and all five failure-path sections. The following closes the architecture-source mapping separately from the practical guide.

Recommendation or research boundary HTH treatment
Separate endpoint, orchestrator and hosted machine Dots overview, 2.3, 3.1–3.4, 4.2; no local policy treated as a universal cloud control
Review vendor package inventory, patch status and reachable vulnerable code Vendor-assurance follow-up, not a customer hardening API. 3.1–3.2 limit exposure; no present CVE totals/compromise assertion copied from the dated scan
Review extracted executable content, not merely archive listings 4.4 validation now checks reviewed artifacts/actual invocation. No archive-scanning pack represented as a complete defense
Restrict egress and minimize credential lifetime 2.1, 2.3, 3.2 and Work/Codex 1.2/3.1; source-service credentials remain independently scoped
Protect client launch configuration and use managed signed updates 3.4 now links Work/Codex 4.3. Endpoint-redirection research is version/test-specific; no invented production override-disabling key or claim of a fixed current build
Bind approvals to exact execution, including post-review mutations 4.4 adds operator validation. Immutable hash binding is a supplier architectural requirement, not an established Dots feature
Keep memory provenance, separation and selective deletion 5.2/7.2 constrain inputs and reset context. Per-entry deletion and perfect partitioning are not claimed; current supported admin lifecycle supersedes older no-reset assertions
Review unattended work and offboarding 7.1–7.2 and Activity View review; scheduled work and delegated work checked separately
Preserve originating requester and approval boundary on delegation 2.2–2.3 validation; low-trust channel input must not acquire environment credentials by implication
Minimize account-wide connectors; monitor organization evidence 2.1 and 6.1; task-scoped grants are not falsely represented as a native enforcement capability

Codex detailed coverage and rejected assumptions

Fetched primary references and automation census

Surface Evidence checked Disposition
Terraform Managed configuration and existing source ledger Public policy support is described, but no newly verified provider resource/schema obtained; no fabricated enforcement pack.
API Dots admin, Dots security, existing Compliance exporter Existing read-only exporter retained. Current environment/dots policy write schema remains unverified; console guidance only.
CLI docs/research/cli-inventory.md rows18/131; Agent Security Codex local controls are not dots workspace administration. No new dots admin CLI claimed.
SDK Current vendor administration/managed-configuration references No new dots/environment administration SDK contract verified; API Platform SDK not substituted.
Config Managed configuration Current available allowed_sandbox_modes and permissions.filesystem.deny_read produce reviewable native TOML; emitter is read-only, does not deploy. Existing runtime-specific packs retained.
SIEM Dots security, existing Compliance and OTel coverage Correlation and minimal content, not a new invented event schema.

Cloud environments and Apps and connectors were fetched for new delegation and future-tool guidance. Read/write boundaries remain explicit. The public OpenAI Trust Portal was reopened on 2026-11-12, with provenance from OpenAI’s security/privacy page. Its visible Documents list includes ISO SoA, Data Flow Diagram, System Cards, Pentest/Security Threat reports, Security Whitepaper, SOC3, VPAT, CSA STAR and FedRAMP20x. Public search for secure-configuration/deployment material did not reveal a new applicable customer Dots baseline. Restricted documents and the full authenticated catalog remain unreviewed; no completeness claim for gated contents or configuration inference from badges. Adjacent Gov/FedRAMP entries are not interchangeable with commercial Dots.

Verification

Offline tests parse emitted TOML and reject invalid profile levels. They do not prove tenant policy delivery, Windows shell denial, cloud-runtime applicability, or audit completeness. See consolidated Pluto validation report for run results.