Question-to-source lookup.

1. start_hereWhere should a reviewer start?Start at the route index, then use the digest for the shortest role-fit read. Navigation proof only; no interview invitation or hiring decision. Primary: route index Support: reviewer digest
2. technical_depthWhat is the strongest technical-depth evidence?Use the executable receipt system: validators, renderers, fixtures, unit tests, and public-pack verification. Cleanroom mechanics and test discipline; no production system access claim. Primary: deployment_receipt.py Support: deployment receipt tests
3. customer_adoption_gapHow do you handle the customer-adoption gap?State the gap directly, then show the 30-day field plan and acceptance scorecard as the adoption runway. No customer deployment exists in this fixture; readiness architecture is not adoption history. Primary: field-trial scorecard Support: 30-day plan
4. workshop_enablementCan this support workshops or enablement?Use the workshop kit and post-workshop handoff: session flow, friction deltas, safety gates, ownership, and follow-up. Enablement-system proof from a public-safe fixture; no external workshop delivery claim. Primary: workshop kit Support: post-workshop handoff
5. product_judgmentWhere is product-judgment evidence?Use the product-feedback export and sample run: buckets, severity, recommended action, and promotion rules. Simulated public-safe signals; no private customer telemetry or internal feedback. Primary: feedback export Support: filled sample run
6. safety_boundaryHow is legal and safety confusion avoided?Start with the nonconfusion policy and verifier gates: no copied brand surface, private data, customer claim, employment claim, or premature outreach. Engineering safety and public-claim boundary; not legal advice or trademark clearance. Primary: non-confusion policy Support: verifier
7. operational_readinessWhat proves operational readiness?Use the public proof ledger inspector and autonomy status surface: hash-chain, graph state, URL checks, scheduler health, guardrails, and next-work packet. Inspectable cadence and public verification; no legal incorporation or external account authority. Primary: proof ledger inspector Support: autonomy status
8. current_next_stepWhat is the current next step?Show the graph node and autonomy selector. The next branch is a cold-read simulation for reviewer traversal. No outreach, hiring claim, autonomous external action, or customer claim before the date gate or a fresh override. Primary: source-answer graph preset Support: autonomy status

• Public-safe dataEvery answer points to a public URL or repository artifact and excludes private evidence.
• No customer deploymentThe adoption answer names the no-customer boundary before describing the readiness path.
• No affiliation or employment claimThe claim boundary excludes affiliation, endorsement, employment, revenue, incorporation, and production-impact claims.
• No outreach before 2026-05-26The index improves reviewer navigation only; outbound remains date-gated.
• Reviewer lookup compressionEight common questions map to exact primary and supporting sources.

• python3 tools/deployment_receipt.py validate-source-index --input examples/source_to_answer_index.json
• python3 tools/deployment_receipt.py source-index --input examples/source_to_answer_index.json
• python3 scripts/verify_public_pack.py
• python3 -m unittest tests/test_deployment_receipt.py

This page does not claim OpenAI employment, affiliation, endorsement, customer deployment, revenue, incorporation, funding, trademark ownership, legal status, or production impact. It is a source-backed reviewer lookup for an independent cleanroom lab concept.