tracking: prepare for OpenAI Apps SDK submission (in-product Codex marketplace listing)

[Harihara04sudhan]

Type: info / coordination — outreach + distribution work

Goal

Get ArmorCodex listed in the in-product Codex plugins marketplace ("Make Codex work your way" surface inside Codex / ChatGPT). Full prerequisites + gap analysis written up at `APPS_SDK_PREREQUISITES.md` in this repo.

Key finding

Today there are 3 paths and only one is live:

• ChatGPT App via Apps SDK (LIVE): requires remote HTTPS MCP server. Our MCP is local stdio. Architectural mismatch.
• Direct Codex plugin self-serve ("coming soon" per OpenAI docs, no ETA): would fit our current architecture.
• OpenAI partnerships sponsorship: how Figma/Slack/Linear/Vercel got listed.

Recommendation: pursue the partnerships outreach path + finish all the submission-ready prep work, so we're ready the moment self-serve opens (or a partnerships sponsor unblocks us).

Tier 1 blockers (must fix before any submission)

• Add MCP tool annotations (`readOnlyHint`, `destructiveHint`, `openWorldHint`) to all 3 tools (`register_intent_plan`, `policy_update`, `policy_read`) in `plugins/armorcodex/scripts/policy-mcp.mjs`. Without these, submission auto-rejects.
• Bump `plugin.json` version 0.2.0 → 0.3.0 + git tag v0.3.0
• Verify `armoriq.ai/privacy` covers all OpenAI-required clauses (data categories, purposes, recipients, retention, user controls)
• Verify `armoriq.ai/terms` content is current
• Publish a `DATA_RETENTION.md` (linked from privacy policy)
• Code audit: confirm audit pipeline never captures credentials, PII secrets, or restricted data types (PCI/PHI/government IDs/auth secrets)

Tier 2 submission materials

• Create `support@armoriq.ai` mailbox + monitoring
• Create reviewer test account at `platform.armoriq.ai` with sample data
• Capture 3–5 screenshots at OpenAI's required dimensions
• Write `CHANGELOG.md` + release notes for v0.3.0
• Add `SECURITY.md` to repo
• Apply for developer verification at `platform.openai.com`

Tier 3 nice-to-have

• Audit tool descriptions for accuracy + non-promotional language
• Audit `defaultPrompt` for "manipulating model selection" red flags
• Consider OAuth 2.1 implementation in backend (if cloud-MCP path opens)

Outreach (parallel)

• Draft OpenAI partnerships email — angle: ArmorClaude marketplace listing + ArmorCodex traction (PR #140 community list + ArmorCopilot in pipeline)
• Identify warm intro at OpenAI if possible

Source docs (verified 2026-05-21)

• https://developers.openai.com/apps-sdk
• https://developers.openai.com/apps-sdk/app-submission-guidelines
• https://developers.openai.com/apps-sdk/deploy/submission
• https://developers.openai.com/codex/plugins/build
• https://developers.openai.com/apps-sdk/build/mcp-server
• https://developers.openai.com/apps-sdk/guides/security-privacy

See `APPS_SDK_PREREQUISITES.md` in this repo for the full breakdown.

[armoriq0]

@Harihara04sudhan where are we on this?

[Harihara04sudhan]

@armoriq0

Re-research today found one material change since May 21. Apps SDK submission portal is now LIVE at platform.openai.com/apps-manage, and an approved ChatGPT App auto-creates a Codex plugin listing. But there's a catch. Apps SDK is MCP-tools-only, no hooks. That means via this path we can only ship the policy CRUD surface (register_intent_plan / policy_read / policy_update inside ChatGPT). Not the runtime preToolUse enforcement that's actually our product. The local plugin stays the real enforcement plane.

Phase 1 (deterministic prep, needed regardless of path) is up as #32. MCP tool annotations, version bump to 0.3.0, DATA_RETENTION.md, CHANGELOG.md, SECURITY.md and LICENSE at repo root.

Phase 2 needs a product decision before code. Do we want a control-plane variant inside ChatGPT (Apps SDK route, hosted HTTPS MCP + OAuth + KYB) as a brand and listing wedge, even though it doesn't enforce? Or skip Apps SDK and ride partnerships outreach plus wait for direct Codex self-serve?

Local plugin distribution side: our submission to hashgraph-online/awesome-codex-plugins (hashgraph-online/awesome-codex-plugins#189) is approved by the maintainer with all CI checks green. Just waiting on final merge.

[Harihara04sudhan]

Submitted ArmorCodex hosted MCP to the largest MCP registry: punkpeye/awesome-mcp-servers (89K stars).

PR: punkpeye/awesome-mcp-servers#8732

Slot: Security category, inserted alphabetically after arian-gogani/nobulex. Direct peers in the same category: aegis (policy-based governance), agentward (permission control plane), nobulex (proof-of-behavior enforcement), mcp-guardian (security and governance proxy), asqav-mcp (AI agent governance). Same lineage as us.

This is independent of the OpenAI Apps SDK submission. Even if OpenAI takes weeks to review, the awesome-mcp-servers listing gives organic discovery from anyone browsing for governance/policy MCP servers.

Tracking:

• ✅ hashgraph-online/awesome-codex-plugins - landed yesterday (commit 2a75a908)
• ✅ OpenAI Apps SDK - in review queue
• ✅ punkpeye/awesome-mcp-servers (89K) - PR #8732 open
• Next candidates: appcypher/awesome-mcp-servers (5.6K), wong2/awesome-mcp-servers (4.2K), mcpso/chatmcp (2K)