diff --git a/docs/superpowers/plans/2026-09-17-obot-research-note.md b/docs/superpowers/plans/2026-09-17-obot-research-note.md
new file mode 100644
index 0000000..52227a8
--- /dev/null
+++ b/docs/superpowers/plans/2026-09-17-obot-research-note.md
@@ -0,0 +1,46 @@
+# Obot Research Note Implementation Plan
+
+> **For agentic workers:** Execute this plan inline with validation checkpoints.
+
+**Goal:** Add and publish a sourced research note on Obot as a governed AI platform for gateways, registries, hosted agents, policy, and audit.
+
+**Architecture:** Describe Obot's platform as a set of cooperating planes: MCP/LLM gateways, hosted sandbox execution, identity and policy services, registries, and user-device controls. Map those planes to Cloud Foundry services and identify where Diego, CAPI, routing, isolation, and Loggregator would need extensions.
+
+**Tech Stack:** Markdown, YAML frontmatter, Devbox, Git, GitHub CLI.
+
+---
+
+### Task 1: Write the Obot research note
+
+**Files:**
+- Create: `research/obot.md`
+
+- [ ] Add frontmatter with title `Obot: Governed AI Gateways, Registries, and Hosted Agents`, author `Ruben Koster (@rkoster)`, date `2026-09-17`, tags `[governance, authorization, agent-runtime, ecosystem-survey]`, `cf_areas: [uaa, capi, diego, loggregator]`, `status: draft`, provisional ratings, and Obot repository/README sources.
+- [ ] Describe the MCP Gateway as a governed entry point with proxying, composite servers, per-identity access, OAuth/credentials, secret bindings, and request/response filters.
+- [ ] Describe the LLM Gateway as provider-compatible access with centrally managed credentials, scoped client keys, model access policies, token/cost recording, and request/response metadata.
+- [ ] Describe hosted MCP servers and agents, Docker/Kubernetes sandbox execution, domain egress policy, and the security trade-off of mounting a Docker socket for development.
+- [ ] Describe Obot Sentry, CLI, Git-backed MCP/Skills catalogs, registry APIs, identity providers, permissions, secrets, and correlated audit logs.
+- [ ] Assess CF relevance as a shared gateway/registry/policy service, with service bindings for credentials/endpoints, Diego or an external sandbox substrate for hosted workloads, CAPI lifecycle integration, and Loggregator-compatible audit correlation.
+- [ ] Add open questions about tenant isolation, platform versus application ownership, sandboxing, egress policy, credential rotation, catalog governance, and audit data boundaries.
+
+### Task 2: Validate and inspect
+
+**Files:**
+- Test: `.github/scripts/validate_notes.py`
+
+- [ ] Run `devbox run validate` and expect all research notes and ideas to be valid.
+- [ ] Run `devbox run test` and expect success.
+- [ ] Run `git diff --check` and inspect `git status --short`; leave unrelated environment artifacts unstaged.
+
+### Task 3: Commit and publish
+
+**Files:**
+- Include: `research/obot.md`
+- Include: `docs/superpowers/specs/2026-09-17-obot-research-note-design.md`
+- Include: `docs/superpowers/plans/2026-09-17-obot-research-note.md`
+
+- [ ] Stage only the three intended files, using `git add -f` for ignored planning artifacts.
+- [ ] Commit with `docs: add Obot research note`.
+- [ ] Push `research/obot` to origin.
+- [ ] Open a PR titled `docs: add Obot research note` targeting `main`, with the repository checklist completed.
+- [ ] Verify the PR URL, branch, state, and CI status with `gh pr view`.
diff --git a/docs/superpowers/specs/2026-09-17-obot-research-note-design.md b/docs/superpowers/specs/2026-09-17-obot-research-note-design.md
new file mode 100644
index 0000000..a982de8
--- /dev/null
+++ b/docs/superpowers/specs/2026-09-17-obot-research-note-design.md
@@ -0,0 +1,40 @@
+# Obot Research Note Design
+
+## Goal
+
+Add a sourced research note on Obot as a governed AI platform combining gateways, registries,
+hosted sandboxes, identity, policy, and audit.
+
+## Scope
+
+The note will describe Obot's MCP and LLM gateways, hosted MCP servers and agents, skills and
+MCP registries, identity and credential management, access policies, request filtering, and
+correlated audit logs. It will distinguish user-device components such as Sentry and the CLI
+from Obot Server capabilities.
+
+The Cloud Foundry analysis will map these capabilities to shared platform services, service
+bindings, Diego-hosted workloads, sandbox/isolation requirements, CAPI lifecycle management,
+and Loggregator-compatible auditing. It will not claim existing CF integration.
+
+## Structure
+
+Create `research/obot.md` using the repository template and required sections:
+
+1. Summary
+2. Key findings
+3. CF relevance
+4. Open questions
+
+Use provisional ratings and clearly label deployment and CF mapping conclusions as analysis.
+
+## Sources and evidence
+
+Use the Obot GitHub repository, README, architecture image/documentation, and deployment or
+feature documentation available from the project. Claims about Cloud Foundry will be analysis
+or open questions, not documented Obot integrations.
+
+## Validation
+
+Run the repository's configured Devbox validation and test scripts, inspect whitespace and the
+staged diff, then commit the note, plan, and design spec on `research/obot`. Push the branch and
+open a new PR targeting `main` without staging unrelated environment artifacts.
diff --git a/generated/research-map.html b/generated/research-map.html
index a2d1686..709aef2 100644
--- a/generated/research-map.html
+++ b/generated/research-map.html
@@ -23,9 +23,9 @@
Focus use cases
Attested Workload Authority and Mediated Tool AccessExchange platform-attested workload identity for scoped authority while credentials and outbound tool access remain mediated by the platform.Strategic decision: Decide whether CF should become the portable trust and policy layer between agent workloads and the tools they invoke.Gap, experiments, and evidence
Current CF gap
CF issues workload identity certificates but does not exchange them for scoped tool authority, keep third-party credentials out of workloads, mediate off-platform access, or record delegation-aware audit events.
Candidate POC
Exchange a Diego instance identity certificate for a short-lived scoped token, invoke one allowed tool through a credential proxy and egress mediator, deny another, and emit attributable audit events.
Candidate RFC scope
Define workload token exchange, authority and delegation claims, credential brokering, outbound mediation and policy enforcement, audit events, revocation, and integration boundaries for UAA, routing, and service brokers.
CF can stage apps and run ephemeral tasks but cannot cheaply compose a reusable environment with per-session workspace state, select stronger isolation, constrain session networking, or resume the session lifecycle.
Candidate POC
Start two isolated sessions from one content-addressed staged environment, attach separate mutable workspaces, apply per-session egress policy, stop one session, and resume it on fresh compute.
Candidate RFC scope
Define environment and workspace references, session identity and lifecycle, isolation classes, network policy, workspace persistence and cleanup, scheduling, quotas, and compatibility with existing CF staging and task APIs.
Familiar < Novelty > EmergingEmerging < Maturity > Established
Unplaced notes (0)
All notes are placed.
Maturity x Actionability
Exploratory < Actionability > Ready to actEmerging < Maturity > Established
Unplaced notes (0)
All notes are placed.
+Gap, experiments, and evidence
Current CF gap
CF can stage apps and run ephemeral tasks but cannot cheaply compose a reusable environment with per-session workspace state, select stronger isolation, constrain session networking, or resume the session lifecycle.
Candidate POC
Start two isolated sessions from one content-addressed staged environment, attach separate mutable workspaces, apply per-session egress policy, stop one session, and resume it on fresh compute.
Candidate RFC scope
Define environment and workspace references, session identity and lifecycle, isolation classes, network policy, workspace persistence and cleanup, scheduling, quotas, and compatibility with existing CF staging and task APIs.