04 / Commercial InterfacesChatGPT App
Use the ChatGPT App as a connected Bitcode interface
ChatGPT App docs explain conversational Bitcode operation: expressing Reads, attaching source, confirming writes, returning proof readback links, and preserving proof boundaries.
Use this page when the user experience is conversational but the outcome still has to be /packs-readable and Protocol-bound.
After reading
You can explain how a ChatGPT App can feel natural while still preserving Bitcode write admission and proof reread.
The ChatGPT App is a guided Bitcode interface, not a separate assistant
A ChatGPT App can help users express Reads, attach source, ask for proof explanations, draft Shippables, and operate through confirmation-gated writes.
Its answers should map back to /packs records and proof readback. The app may be conversational, but the proof and state contract remains Bitcode.
Why this matters
This keeps a familiar commercial interface aligned with Protocol-grade evidence instead of drifting into untracked chat output.
- Confirm writes before changing route-owned state.
- Attach source, output destinations, Read intent, and AssetPack references as structured context.
- Return /packs links or activity IDs for reread.
Chat results should teach where to verify
A good ChatGPT App response should say what it did, what is staged, what is blocked, and where the user can verify the result in /packs or the relevant route.
This is the same write/read discipline as the action guide, adapted for conversational operation.
Why this matters
Users should never have to trust a chat transcript when /packs and route readback can show the actual state.
Public docs expose guidance and proof posture, not protected source
Public Bitcode docs derive from the active Protocol, package-owned catalogs, route contracts, and source-safe generated artifacts. They can explain usage, measurements, event ids, proof roots, docs links, runbook links, redaction posture, testnet rollout readiness, fee boundaries, and settlement posture.
They must not reveal protected source payloads, raw protected prompts, secret values, provider tokens, wallet private material, or unpaid AssetPack source. Source-bearing AssetPack contents cross to the reader only after settlement and rights transfer.
Why this matters
This keeps the public product understandable while preserving the boundary that makes AssetPacks economically and operationally safe.
- Allowed: usage guidance, route links, state labels, source-safe measurements, proof roots, dashboard/runbook ids, redacted incident posture, testnet rollout readiness, LocalStagingTelemetryDocumentationRehearsal evidence, and fee/right boundaries.
- Interface docs may surface event ids, proof roots, docs links, runbook links, and redaction posture from TelemetryDocumentationInterfaceIntegration without revealing source-bearing payloads.
- Local and staging-testnet rehearsal docs may surface documentation discovery, telemetry event emission, dashboard/runbook lookup, docs QA, incident drill, source-safe proof-root review, and blocked value-bearing mainnet posture.
- Blocked: secrets, provider tokens, wallet private material, raw protected prompts, protected source payloads, and unpaid AssetPack source.
- Docs QA fails closed when public docs, internal docs, route docs, interface docs, generated artifacts, proof posture, or workflow checks drift.
- Compatibility boundaries stay explicit: /exchange redirects to /packs and does not create a parallel current product surface.