fold-order packet · stapled evidence packet

Lay Out Explicit Front and Back Page Pairs for Folded Booklet Signatures

Knowing how many sheets a zine needs does not tell you which page goes opposite page one. Keep the logical front/back pairs and every padded blank visible before testing a printer's folding convention.

1 · Booklet code | content pages | first content page number

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 fold-order packet processes Booklet code | content pages | first content page number 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 sheet count left page placement to guesswork. After: every outer-to-inner sheet has explicit front/back content pairs and named blanks.

2 · Read the fold-order packet

Logical imposition map only, not a printer-ready file or production guarantee. Verify the declared convention with a four-page physical test and consult a print technician about duplex orientation, creep, trim and binding before a full run.

Paid layer: fold-order packet filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked fold-order packet 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 fold-order packet app calculations after a local convenience signal
print the fold-order packet with visible assumptions and its safety boundary
CSV of the displayed blank positions 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 fold-order packet, 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 fold-order packet

The model treats each signature as an independently folded stack containing a multiple of four logical page positions. It arranges outer-to-inner sheets, left-to-right logical pairs: front [last,first], back [second,second-last], then moves inward by two positions per side. The last signature is padded to the chosen signature size, not shrunk to a different size. Content page labels increase from the supplied positive first number. No creep, trim, bleed, paper thickness, binding allowance or printer rotation is modeled. One booklet may contain at most 512 content pages and the run at most 4,096 padded positions, keeping the complete free pair list bounded. A driver-specific print-ready file is not generated.

Boundary and sources

Method: For each signature, place its last logical position opposite its first on the front of the outer sheet, then its second opposite its second-last on the back. Move the boundaries inward by two positions and repeat. Resolve a position beyond the content count as blank. Keep every sheet's signature, front and back pairs in the free notes so the map can be checked independently.
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 fold-order packet 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 fold-order packet. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Booklet code | content pages | first content page number; the setting is Pages per independently folded signature. 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.