paycycle calendar folio · stapled evidence packet

Count Anchored Paydays by Complete Calendar Month, Not by Four-Week Guess

A fourteen-day cycle does not reset at the first of each month. Enumerate it from a known anchor, keep partial months separate, and verify every modeled deposit date against the employer’s calendar.

1 · Plan code | anchor payday YYYY-MM-DD | window start YYYY-MM-DD | window end YYYY-MM-DD

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: This paycycle calendar folio calculates in the tab from Plan code | anchor payday YYYY-MM-DD | window start YYYY-MM-DD | window end YYYY-MM-DD. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.

Perspective: Before: a pay cycle was approximated as four-week months. After: anchored dates show actual calendar-month grouping and make truncated windows explicit.

2 · Read the paycycle calendar folio

Calendar illustration only, not employment, tax or financial advice and not a promised deposit schedule. Confirm actual pay dates, holiday shifts and pay-period conventions with the employer’s payroll team before scheduling payments.

Paid layer: paycycle calendar folio filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one full, unwatermarked paycycle calendar folio App execution
three invented readings and unlimited calculations in the paired article demo
copy the complete working and boundary; voluntarily share non-sensitive input state

What $4 one-time adds

subsequent paycycle calendar folio App calculations through a browser-local convenience signal
boundary-preserving print and row-and-summary CSV of this paycycle calendar folio; conditional retyping budget uses only your entered minutes
five local headline/count/time summaries, separately deletable; full-input draft is separate and not a backup

HYPOTHESIS / PROTOTYPE: the proposed $4 one-time price concerns filing this paycycle calendar folio, not obtaining its answer. No checkout is available. An optional manual-retyping baseline computes a conditional one-export retyping budget; preparation, review, measured savings and buyer demand are not implied.

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 paycycle calendar folio

This folio models a fixed number of civil days between paydays. It does not model twice-monthly dates, working-day shifts, arrears, earned pay, tax withholding or public holidays. An anchor is one date known to lie on the cycle; dates may be generated before or after it using whole cycle multiples. Choose a window no longer than 1,096 inclusive days, within years 1900–2100. The three-or-more-month headline is suitable for a biweekly illustration, but other cycle lengths may naturally create more dates. Multiple rows are separate payroll scenarios, not additive income streams or a guarantee of deposit availability.

Boundary and sources

Declared local method: Find the first anchor-plus-cycle-multiple date at or after the start, then advance by the entered whole-day cycle until the end is exceeded. Include exact endpoints. Group dates by calendar month. A month is complete only when its first and last days both lie in the window; count complete months with at least three dates. Do not multiply a weekly average by four and call that a calendar-month answer: actual months and weekday alignments differ.
Every sample code, measurement, date, price, fingerprint and scenario is invented. Artifact checks do not verify reader data, policies, actual files, tickets, votes or health/accessibility outcomes.
Google’s official Gemini pricing page, fetched 2026-10-01, lists AI Studio access in its Free section, limited model access and free input/output tokens. Free-tier content may be used to improve products. Optional external formatting may require an account; limits/access can change. Manual local entry needs none. Do not send sensitive records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this paycycle calendar folio 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 paycycle calendar folio. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Plan code | anchor payday YYYY-MM-DD | window start YYYY-MM-DD | window end YYYY-MM-DD; the setting is Fixed pay cycle length (days). 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.