OpenAI publishes developer docs, examples, community routes, Cookbook links, and builder programs such as Codex Ambassadors, Codex for Students, Codex for Open Source, meetups, and hackathon support.
sourceVerified interest becomes a scoped session, not a vague partnership claim.
Prepare a collaboration-grade first working session for the independent proof lab without sending outreach, claiming affiliation, or treating public developer surfaces as permission. This packet answers: if a verified OpenAI-owned or human-owned signal asks to test working together, what exact safe session can run first?
Trigger
Use this only after verified collaboration interest, a verified human-owned reply, or a fresh same-thread override from Nic. Until then it is a local preparation artifact and public proof of collaboration readiness, not an invitation, pitch, post, or outbound message.
Allowed surfaces
OpenAI documents prompts as durable project assets that can be saved, versioned, shared, templated, tested, and evaluated.
sourceOpenAI exposes focused API examples and separates OpenAI-source examples from community examples.
sourceThe Cookbook contains open-source examples and guides for building with the OpenAI API, usually with an account and API key.
sourceThe public OpenAI Cookbook repository carries examples, guides, issues, pull requests, and an open-source license.
sourceThe developer forum is for technical discussion about OpenAI APIs and developer tooling, including Codex-related developer topics.
sourceOpenAI asked for feedback on documentation structure, use cases, tutorials, code samples, and videos in a public developer-community thread.
sourceThe live careers board exposes current OpenAI roles and changes frequently, including Codex-related and Technical Success openings when listed.
sourceContract
Input
- One bounded repo, docs, example, or adoption-workflow slice that can be discussed publicly or sanitized before publication.
- Acceptance criteria written before the run: expected behavior, required files, forbidden actions, and the closest verifier.
- A data boundary that names secrets, customer material, private account state, private source code, and unsupported tools as out of scope.
- A rollback or containment owner for any change that touches a repo, docs draft, public page, or workflow artifact.
Output
- Scope card that records the task, source basis, claim boundary, and allowed actions.
- Live run receipt with commands, changed files, verifier output, and blocked steps.
- Failure map that separates source uncertainty, tool failure, implementation failure, and claim-safety refusal.
- Ready/repair/reject decision with a handoff note and one product-signal note.
Success
- The verifier passes or the repair/reject path names the exact failing gate.
- The public-safe receipt contains no private IDs, emails, local paths, credentials, or customer material.
- The output states no affiliation, no customer deployment, no employment, no endorsement, and no outbound authorization.
- The work produces a reusable artifact: fixture, example, docs feedback, adoption receipt, or reviewer-safe implementation note.
Refusal
- Secrets, private customer data, protected UI trade dress, or private OpenAI material stop the session.
- Employment, affiliation, customer status, funding, incorporation, endorsement, or OpenAI review implications force a refusal.
- Legal, payment, banking, tax, hiring, fundraising, contract, or trademark action is outside this packet.
- Downgrade to review-only if there is no bounded verifier or no public-safe way to record the run.
Candidate collaboration shapes
Docs Feedback Packet
Turn a CIW proof-lab run into a structured docs-feedback artifact: source gap, example gap, proposed wording, test fixture, and public-safe receipt.
- Input
- A documentation area, confusion point, or example request that can be discussed publicly.
- Output
- A feedback packet with before/after notes, runnable fixture, claim boundary, and no-post/no-send status unless later authorized.
- Verifier
python3 tools/openai_collaboration_path.py validate --input ops/openai_collaboration_path.json- Refusal
- Block feedback that would expose private account details, unreleased product behavior, or unsupported claims about OpenAI review.
API Example Adaptation
Translate an OpenAI public example pattern into a CIW-style receipt-bearing example with prompt/version/eval notes, without copying brand identity or claiming endorsement.
- Input
- One public API example or Cookbook concept plus a target adoption scenario.
- Output
- A small public-safe example packet with problem, minimal input, steps, verifier, expected output, failure taxonomy, and extension gates.
- Verifier
python3 scripts/verify_pack.py- Refusal
- Reject examples that depend on private model behavior, protected UI copying, credentials, or a product name that could confuse source ownership.
Codex Adoption Instrumentation
Run a 60-90 minute adoption-workflow instrumentation session: scope card, live run, verifier, handoff receipt, and product-signal note for a Codex-like rollout.
- Input
- A sanitized adoption workflow, success metric, allowed repo slice, and disallowed data/actions.
- Output
- A ready/repair/reject receipt plus failure map, acceptance criteria delta, and operational-readiness note.
- Verifier
python3 -m unittest tests/test_openai_signal_router.py tests/test_company_system_map.py- Refusal
- Downgrade adoption work that asks for real customer data, private account access, unsupported deployment claims, or post-sales promises.
Public Repo Maintenance Sprint
Prepare a clean first-maintenance session around a public issue or docs/example fixture: reproduce, patch, test, record, and hold without submitting before authorization.
- Input
- One public issue, failing example, outdated docs path, or accepted maintenance target with contribution rules.
- Output
- A local patch packet, reproduction log, tests, non-confusion note, and send/hold/refuse decision.
- Verifier
python3 tools/openai_collaboration_path.py render --input ops/openai_collaboration_path.json --output applications/openai/OPENAI_COLLABORATION_PATH_PACKET.md --html demo/collaboration-path/index.html- Refusal
- Hold maintenance work when contribution rules are unclear, tests cannot run, or the route would imply contributor status before a merged public contribution exists.
Hard gates
- No outbound before 2026-05-26 unless verified human-owned interest appears or Nic gives a fresh same-thread override.
- No legal, tax, banking, payment, contract, hiring, fundraising, trademark, compensation, customer, or production-deployment action.
- No OpenAI affiliation, partnership, endorsement, employment, customer, funding, official status, contributor status, or accepted-feedback claim.
- No private inbox IDs, email addresses, local paths, credentials, account data, customer material, or private source material in public artifacts.
- No use of OpenAI logos, UI trade dress, protected product names as project identity, screenshots as branding, or copied proprietary examples.