Pool Defined Technical Terms Across Chapters to Audit Glossary Coverage
Averaging chapter glossary percentages treats a twenty-term safety primer the same as an eighty-term chemistry module. Pool total defined terms over total introduced terms to calculate true course-wide glossary coverage.
1 · course module | technical terms introduced | terms defined in glossary
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Data note: Everything runs in this browser tab on the glossary coverage register: your course module | technical terms introduced | terms defined in glossary stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: A small 100-percent module hides a large 75-percent module unless denominators are pooled. After: the glossary coverage register shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the glossary coverage register
Pooled proportion arithmetic on term counts you enter. Not curriculum accreditation or exam-readiness certification; verify definitions against authoritative course textbooks.
Paid layer: glossary coverage register print and history
one-time step · the free reading above stays complete
Free tier
- one complete glossary coverage register run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the glossary coverage register with its row workings
- CSV of percent defined and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the glossary coverage register, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
Pooled proportion arithmetic on term counts you enter. Not curriculum accreditation or exam-readiness certification; verify definitions against authoritative course textbooks.
- Method: Enter the percentage of terms each module should define before exam revision begins (for example, 85 percent).
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this glossary coverage register, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a glossary coverage register. Return plain rows only: course module | technical terms introduced | terms defined in glossary. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: course module | technical terms introduced | terms defined in glossary. No AI response is executed as code.