yycore.ai
Menu

Public Poe utility · v0.0.1

Put the spec on the record.

YY Spec Court

Paste one bounded software or product specification. After a digest-bound confirmation, two named models review different lenses in parallel. You get their independent findings in a ZIP you can inspect and verify on your own machine.

  • Paste
  • Confirm digest
  • Two reviews
  • Verify
Open YY Spec Court on PoeInspect the packet

YY adds no creator charge in this release. A Poe account, model permission prompt, platform limits, and model point costs may still apply.

One bounded workflow

The handoff is named before either reviewer sees the text

The first turn performs no model call. It normalizes the pasted text, displays its SHA-256 digest, names both provider-managed reviewers, and waits for one exact confirmation.

  1. Paste one specification

    V0 accepts text only, up to 32 KiB. Repositories, archives, attachments, credentials, and executables are rejected.

  2. Inspect the disclosure

    Poe shows the normalized subject digest and the exact named handoff to GPT-5.4-Mini andClaude-Haiku-4.5 before any review begins.

  3. Confirm the same subject

    Reply with CONFIRM REVIEW. The script binds that confirmation to the preceding disclosure and refuses stale, changed, or attachment-bearing input.

  4. Download the evidence packet

    Both reviewers run independently. Deterministic Python validates and normalizes what they returned, preserves disagreement, and attaches one four-file ZIP.

The packet

Four files, with the source responses still visible

Normalization makes the evidence easier to compare without replacing the underlying reviewer text. The receipt records malformed and unavailable states instead of papering them over.

  • review.md

    A readable rendering of both named reviews, their verdicts, normalized findings, open questions, and structural lens comparison.

  • review-receipt.json

    Canonical reviewer records, exact source responses, stable finding IDs, the subject digest, request state, and explicit non-claims.

  • verify.py

    A dependency-free Python verifier for the manifest, receipt shape, reviewer order, finding IDs, status logic, and recorded response hashes.

  • manifest.sha256

    Byte-level SHA-256 digests for the Markdown review, JSON receipt, and verifier included in the packet.

Provider boundary

Full-shield script, disclosed provider-managed reviewers

YY's Python runs in Poe's default full-shield Script Bot environment. It makes no direct external request, writes no persistent script state, and operates no YY receiving endpoint.

The selected OpenAI- and Anthropic-managed Poe bots do receive the specification through Poe. YY does not represent those reviewers as full shield, and Poe may require its own provider permission prompt before the calls run.

Read Poe's Script Bot boundary ↗
PASTED SPECSHA-256 + CONFIRM
OPENAI REVIEWANTHROPIC REVIEW
RECEIPT ZIP

Evidence boundary

Two reviews are more evidence, not a certificate

  • The packet is unsigned and does not authenticate YY, Poe, either model provider, the author, or the submitted specification.
  • A passing verifier proves internal consistency only. It does not prove truth, correctness, completeness, implementability, security, or compliance.
  • The ZIP is deterministic for the captured responses. A new model run can produce different words, findings, verdicts, and bytes.
  • Reviewer output is preserved and may repeat some or all of the submitted specification; there is no separate raw-specification file.
  • If one reviewer fails, the packet says partial and preserves the valid review. No substitute model is inserted silently.
  • The structural comparison groups observable fields. It is not semantic consensus and does not decide which reviewer is right.

Release evidence

Tested locally, then exercised through the real Poe runtime

Twenty local tests include a deterministic matrix of 20 synthetic specification classes, plus strict schemas, stable IDs, deterministic packaging, hostile Markdown, stale consent, partial and total failure, tamper refusal, and the Poe adapter.

The public release source passed independent Claude Opus and GLM-5.2 reviews. Its live synthetic packet completed both named providers, matched Poe's displayed hash, and passed the dependency-free verifier after download.

Deployed source SHA-256:41f00b30e983a96d91c7c41843df61e5731c6571b7abe0c9ee7bf2c166f1117a

Tests
20 PASSING
Named reviewers
2 COMPLETE
Normalized findings
44 LIVE
YY receiving endpoints
0

Two different Poe receipts

Need a record of the conversation instead?

YY Spec Court sends one confirmed specification to two reviewer models. YY Chat Receipt is the separate no-model-call utility for exporting the ordered conversation Poe exposes to a bot.

Compare Chat 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