uncertain-onset docket · clerk's docket sheet

Keep Uncertain Onset Dates as Ranges Instead of Guessing an Order

A remembered onset “between Tuesday and Thursday” is a range, not a date to invent. Preserve that uncertainty and show which pairs cannot support a claimed order or minimum day gap.

1 · Event code | earliest date YYYY-MM-DD | latest date 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 uncertain-onset docket calculates in the tab from Event code | earliest date YYYY-MM-DD | latest date 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: uncertain notes were forced into an exact chronology. After: bounds preserve uncertainty and each unsupported pairwise gap is visible without an invented date.

2 · Read the uncertain-onset docket

Date-bound organization only: no diagnosis, causal inference, urgency assessment or treatment advice. Bring the original uncertain notes and any health concerns to a qualified clinician; do not delay care because this docket looks orderly.

Paid layer: uncertain-onset docket filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one full, unwatermarked uncertain-onset docket 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 uncertain-onset docket App calculations through a browser-local convenience signal
boundary-preserving print and row-and-summary CSV of this uncertain-onset docket; 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 uncertain-onset docket, 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 uncertain-onset docket

This docket preserves the precision you actually have. Use fictional event codes and civil dates for one coherent diary convention. Earliest and latest are inclusive bounds on an event date, not the duration of a symptom. An exact date is entered twice. Do not widen a range to cover a symptom’s whole course or choose a midpoint to make sorting easier. The supplied separation setting is an organizational question for this comparison, not a clinical threshold. A clinician may need the original narrative, exact times, medications and context; this bounded date map cannot infer causation, urgency or a treatment sequence.

Boundary and sources

Declared local method: If one latest bound is before the other earliest bound, that order is certain within the supplied dates. Their minimum separation is later earliest minus earlier latest. If ranges touch or overlap, no positive separation and no strict order is established. Mark pairs whose guaranteed gap is less than the setting. Each unordered pair contributes once to the headline but appears beside both events for inspection. This is interval logic, not a probability model of likely onset.
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 uncertain-onset docket 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 uncertain-onset docket. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Event code | earliest date YYYY-MM-DD | latest date YYYY-MM-DD; the setting is Required definite separation (whole 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.