puzzle-edge stub · punched ticket stubs

Cross-Check a Rectangular Jigsaw's Sorted Border Pieces

Before searching the floor for a lost corner, check whether the sorted edge pile matches the actual piece grid. Keep an excess count distinct from a short count, and handle narrow puzzles without double-counting corners.

1 · Puzzle code | columns of pieces | rows of pieces | sorted border count

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The puzzle-edge stub processes Puzzle code | columns of pieces | rows of pieces | sorted border count locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: a thin edge pile immediately meant a missing piece. After: grid dimensions, expected border and signed sorting discrepancy are separate observations.

2 · Read the puzzle-edge stub

Rectangular-grid inventory arithmetic only. This does not detect lost pieces or certify a puzzle's completeness; confirm the actual cut layout and check sorting before contacting the maker about a replacement.

Paid layer: puzzle-edge stub filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked puzzle-edge stub run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent puzzle-edge stub app calculations after a local convenience signal
print the puzzle-edge stub with visible assumptions and its safety boundary
CSV of the displayed pieces absolute discrepancy and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the puzzle-edge stub, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the puzzle-edge stub

Count actual columns and rows from a confirmed layout, not from dividing an approximate box total. The model assumes a complete rectangular grid with one piece at each position and recognizable border pieces. Irregular novelty cuts, shaped puzzles, missing grid positions and pieces that span several nominal positions do not fit it. The observed border count may be mistaken even when total pieces match the box. A positive signed difference means fewer pieces in the border pile than modeled border positions; a negative difference means an excess in that pile. The review mark is a personal sorting threshold. It is not a manufacturer defect criterion, and no family member is blamed by an arithmetic mismatch.

Boundary and sources

Method: Total positions are columns times rows. Interior positions are max(columns-2,0) times max(rows-2,0). Their difference is the modeled border. Subtract the observed edge-pile count for a signed discrepancy and use its absolute value for review. The summary adds those absolute values; a surplus and a shortage cannot cancel each other.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this puzzle-edge stub for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a puzzle-edge stub. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Puzzle code | columns of pieces | rows of pieces | sorted border count; the setting is Reader-selected border discrepancy review mark (pieces). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.