yycore.ai

Public Poe utility · v0.0.1

Leave the chat with a receipt.

YY Chat Receipt

Bring one no-model-call utility into a Poe thread. It turns the ordered conversation visible to the bot into a deterministic ZIP you can read, hash, and verify on your own machine.

  • Visible chat
  • Canonical records
  • Portable verifier
Open YY Chat Receipt on PoeInspect the packet

YY adds no creator charge in this release. A Poe account and Poe platform limits or points may still apply.

One narrow job

Capture the thread Poe actually handed to the bot

Poe primes a Script Bot with the chat UI at invocation. YY Chat Receipt records that bounded input without calling another model, making an external request, or writing persistent bot state.

  1. Bring it into the thread

    In a Poe conversation, mention @YYChatReceipt. Poe supports bringing another bot into an existing multi-bot thread with its prior context.

  2. Request the export

    Ask it to export the conversation. The triggering user message is included exactly once, then the ZIP is attached to the bot response.

  3. Verify away from Poe

    Extract the ZIP and run python verify.py .. The verifier needs Python 3.11 or newer and no third-party package.

The packet

Five files, one closed verification contract

The archive is stored with fixed file order and metadata. Each payload can be inspected independently; the bundled verifier then checks whether the pieces still agree.

  • transcript.md

    Readable message text with redacted user identity and explicit attachment-content exclusions.

  • receipt.json

    Canonical message records, per-message SHA-256 digests, a chained digest, and sender/model inventory.

  • manifest.sha256

    Byte-level digests for every payload file in the packet.

  • verify.py

    A dependency-free Python verifier for the manifest, records, chain, transcript, counts, and inventory.

  • VERIFY.md

    The exact local command plus the evidence boundary a passing result does not cross.

Host boundary

The chat stays inside Poe and the downloaded ZIP

The bot runs in Poe's default full-shield environment. Its code makes no model call and no direct network request. YY operates no receiving endpoint, so conversation content is not sent to YY by this tool.

The conversation already exists on Poe, and Poe's own platform terms still apply. Full shield is a host boundary, not a general privacy or security certification.

Read Poe's full-shield documentation ↗

Evidence boundary

What the receipt records—and what it cannot prove

  • The receipt contains only the ordered history Poe presents to the bot when it runs.
  • Message text is included. Attachment names and media types are included; attachment URLs and contents are not.
  • Human display names and identifiers are redacted to the user role. Bot display names remain as sender inventory.
  • The packet is unsigned and does not authenticate YY, Poe, a person, a bot, or an attachment.
  • A passing verification does not prove truth, origin, completeness, chronology, or that Poe exposed the entire human-visible history.
  • There is no timestamp. The same ordered message records produce the same ZIP bytes.

Release evidence

Tested against the real Poe runtime

Twenty local tests cover deterministic output, canonical message digests, chained hashing, identity redaction, attachment metadata, input limits, tamper refusal, and Poe history handling.

A live three-message Poe export built from synthetic prompts verified successfully and rebuilt byte-for-byte with the same local core. The source is not publicly licensed; the dependency-free verifier travels inside every receipt so the packet contract remains inspectable.

Tests
20 passing
Model calls
0
Direct network requests
0
Persistent bot state
0

Two different receipts

Need usage evidence without conversation content?

YY Chat Receipt deliberately includes the message text Poe exposes to it. YY Workload Receipt is the separate local tool for content-free usage metadata, tool counts, retries, approvals, and explicit evidence gaps.

Compare Workload ReceiptAll YY projects

Related YY tools

Need a packaged local check?

These paid, one-time releases address narrower operational checks. Review their public evidence and scope before deciding whether either fits your workflow.

  • YY Dataset Preflight

    For teams that need a local, inspectable dataset inventory before training or upload.

    $39 one-time

    Review the product

  • AgentSafe

    For OpenAI Agents SDK teams checking whether approval preceded FunctionTool execution.

    $49 one-time

    Review the product