QuotaWake Journal
A quieter way to begin an AI coding session.
Practical, source-backed notes for people who want to understand local-first session readiness: what it is, how it decides, and where its boundaries belong.
Foundations · 6 min read
Session readiness is about choosing when a legitimate local CLI check happens—not changing the limits of a plan. Here is the vocabulary, the workflow, and the line QuotaWake will not cross.
Read the guide →
Mechanism · 7 min read
Signals are imperfect. This is why confidence order, activity gating, cooldowns, idempotency, and an honest unknown state are all part of one decision.
See the decision model →
Trust · 6 min read
Installed CLIs, bounded processes, local logs, and no provider tokens: a clear explanation of what stays on your machine and why that boundary matters.
Read the privacy note →
Operations · 5 min read
Check local readiness state and logs first, pause automatic sends when needed, then stop or uninstall the per-user service with a clear record of what each action changes.
Read the operations guide →
Editorial standard
A claim should come with its boundaries.
These notes are written from the project’s implementation and documentation. When behavior depends on a provider, platform, or release, we link to the primary source, name uncertainty, and update the piece when the underlying fact changes.