adapter return bridge
return generated text through supplied-text intake
Returned generated text is supplied text. Use the main intake to paste the original question and generated text, show reading structure, then export receipt or capsule from that reading result.
This bridge does not create a separate adapter intake, source packet, receipt, capsule, proof path, source attestation, platform attestation, or output provenance.
canonical intake
The public supplied-text intake is /. That is where reading structure, receipt export, and capsule export happen.
returned text lane
Returned generated text enters as pasted_answer: user_supplied / null / pasted / not_model_attested.
no output provenance
Copy hash, platform name, instruction slot, or adapter-used wording does not attest which app produced the text or whether the instruction was used.
bridge boundary
return_page_is_intake_engine: false
return_page_posts_to_mode_api: false
return_page_exports_receipt: false
return_page_exports_capsule: false
query_prefill_allowed: false
url_full_text_transfer_allowed: false
copy_payload_hash_is_output_provenance: false
Returned generated text remains supplied text until it is pasted into the canonical intake.
Open supplied-text intake
Paste the question and returned generated text on the main page, then show reading structure and export receipt or capsule from the result.
Copy instruction
SHA-256 verifies instruction bytes before copying. It does not attest any generated text returned from another app.
Instruction slots
A slot may hold instruction text. It does not establish that later generated text used it.
Paste targets
Platform recipe headings are paste targets, not integrations, provenance, source attestation, or proof authority.