RUMBO IA CRM — ChatGPT app submission review checks

Date: 2026-09-11 UTC Candidate SHA: 9152f5a50de42be55508f0effed5ed09aee44c60 Budget invariant: MONEY_SPEND=0

Source review

  • Tool count: 4.
  • Every exposed tool declares all three required annotations explicitly: readOnlyHint=true, openWorldHint=false, destructiveHint=false.
  • Every exposed tool declares a non-null outputSchema; there are no missing-outputSchema warnings.
  • Tool names and descriptions match the implementation: readiness returns status only; note/stage/outreach tools prepare reviewable artifacts and do not apply/send them.
  • Custom UI: none. Widget CSP review: not applicable.

Sensitive-data review

The input schemas do not solicit credentials, MFA codes, payment-card data, health data, government IDs, biometrics, or other explicitly sensitive categories. However, free-text fields such as note, reason, and objective, and identifiers such as workspace_id, subject_id, and lead_id, can contain user-provided customer or business information. Review mitigation is explicit:

  • /privacy describes these inputs and their bounded processing.
  • /support instructs users not to send passwords, API keys, authentication tokens, or unnecessary customer data.
  • Public v1 exposes no customer-record search/retrieval tools.
  • Public v1 exposes no CRM mutation or autonomous message-send tools.
  • Proposal outputs remain REVIEW_REQUIRED with side_effect=false.

Submission import artifact

chatgpt-app-submission.json contains:

  • App info: RUMBO IA CRM, subtitle Prepare CRM proposals, category PRODUCTIVITY.
  • 4 tool annotation blocks with behavior-grounded justifications.
  • Exactly 5 positive test cases.
  • Exactly 3 negative test cases.

Remaining portal-controlled checks

  • Domain challenge token / verification not completed.
  • Apps Management write permission not proven.
  • Publisher/developer identity not proven.
  • OpenAI Platform project data residency is not proven GLOBAL; current MCP review requirements reject EU-residency projects and require a global-residency project.
  • Canonical logo is prepared and hash-verified, but portal upload is not executed.
  • Scan Tools is not executed.
  • Distribution scope is not selected.
  • Production MCP URL promotion/submission authority is not granted.

Invariant: TECHNICAL_PASS != PORTAL_PASS != SUBMISSION_AUTHORITY != PUBLICATION.