← Go back

Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team

Break Reminders at Least Every 3 Hours: The Minor Cadence, Explained

The short answer

The California pack's minor sentence makes a measurable promise: break reminders at least every 3 hours for known minors. 'At least' makes 3 hours a floor — more frequent reminders are compliant, fewer are not. In CompanionGuard the free disclosure snippet delivers the reminder in minor mode; on Pro and Team, operator session and daily caps add enforcement behind the offer. This guide covers the cadence arithmetic, the copy, and the composition of offer and enforcement.

What is the 3-hour break reminder rule?

The 3-hour rule is the cadence in California's disclosure pack for known minors: the bot must offer break reminders at least every 3 hours of use. CompanionGuard's minor mode implements it in the free snippet, and the pack's banner sentence states it publicly: 'we will remind you every 3 hours, as California law requires for known minors.'

Create the free safety kit Next guide All guides

CompanionGuard is built by Ingenious AI. A compliance toolkit — not legal advice and not a clinical service. If you are in crisis right now: US — call or text 988; UK & Ireland — Samaritans 116 123.

Reading 'at least' correctly

Two words in the pack's duty list carry the rule: reminders 'at least every 3 hours'. The cadence is a maximum interval, not a schedule — a reminder at hour 3 satisfies it, a first reminder at hour 4 violates it, and reminders every hour exceed it honourably. Products whose natural session is shorter than 3 hours may rarely trigger the interval in-session, which is compliant by arithmetic and worth a second thought in spirit: the duty aims at long, immersive use, and a bot engineered into 2-hour-59-minute sessions to stay beneath the reminder is complying with the letter against the purpose. Reviewers notice such engineering; design for the purpose and let the arithmetic follow.

Cumulative or continuous? The pack does not specify session mathematics, so the defensible reading tracks elapsed engagement per minor user across a day, not per conveniently-bounded session — the same reason the runtime keeps both a session clock and a daily clock for caps. When in doubt, remind on the interpretation that interrupts more: the reminder is gentle, and its cost is a sentence.

The reminder as a piece of copy

A break reminder is a small UX text with an unusual job: interrupt immersion, kindly, without shaming the user for enjoying the product. The pack's framing — 'Please take regular breaks' — models the register: an invitation with a reason implied (care), not a warning with a threat. In-product, the reminder should be brief, warm, non-negotiable in its delivery but non-blocking in its effect (it is an offer — enforcement is the caps' separate job), and it should not be gamified away ('click to dismiss forever' converts the duty into a setting).

Frequency of wording matters less than reliability of arrival, but vary the surface lightly if your design allows — the same sentence at hour 3, 6 and 9 becomes wallpaper; the same fact in fresh sentences stays a reminder. What may never vary: that it fires, that it is for the user's good, and that continuing afterwards is allowed without penalty or guilt copy.

Composition with caps: the nudge and the wall

Minor mode's reminder and the runtime's caps are one system in two registers. The reminder (free, snippet) is the nudge: at least every 3 hours, an offer. The caps (Pro/Team, runtime) are the wall: at the operator's session or daily limits, enforce_break pauses the session. Composed well, caps sit inside the reminder story — a session cap of 90 minutes means many sessions end by enforcement before a 3-hour reminder would ever fire, and that is coherent: the operator chose a stricter rhythm than the floor, and the protocol page should say so plainly.

Composed badly: a session cap of 5 hours with reminders promised at 3 — the wall contradicts the nudge's world, and the evidence (enforce_break events at 5 hours, reminder claims at 3) documents the incoherence permanently. Choose the numbers as one design, describe them as one design. The caps guide and the minor-safety overview hold the other pieces.

Verifying the cadence without waiting 3 hours

You cannot launch-test a 3-hour interval in real time, so verify by construction and by staging: in staging, configure a compressed cadence if your integration allows test timings, or verify the timer logic against session elapsed values the runtime already tracks; in production, the evidence and reminder logs let you audit actual intervals after the fact — sample minor sessions weekly and confirm no inter-reminder gap exceeded the floor. The audit-after-the-fact is not a concession; it is how all cadence duties are honestly verified, and the counts-only design makes it a five-minute query rather than a surveillance project.

Also verify the negative configuration: adult sessions must not receive minor reminders (the cadence is a minor protection, and spraying it at adults teaches everyone to ignore it), and unflagged sessions follow your documented age-knowledge policy — the flag's integrity is the cadence's integrity. The configuration guide covers asserting it.

Five actions for a cadence that keeps its promise

  1. Read the duty as a floor: first reminder no later than 3 hours into a minor's engagement, subsequent gaps never longer — more frequent is compliant.
  2. Track the cadence against elapsed engagement per minor, not per conveniently-bounded session; choose the interpretation that interrupts more when in doubt.
  3. Compose reminder and caps as one design: caps inside the reminder's story, both described identically on the protocol page.
  4. Verify in staging with compressed timings, then audit real intervals weekly from the records — no inter-reminder gap may exceed the floor.
  5. Confirm adult and unflagged sessions do not receive minor reminders; the protection's precision is part of its credibility.

Worked example: a cadence audit finds the session loophole

A fictional companion, Tempo Jr., promises the California wording and delivers reminders faithfully — per session. Its first cadence audit, run over a week of minor usage, finds the loophole its users already knew: sessions auto-restarted on a common client event, resetting the reminder clock, so a minor in continuous use for 5 hours received one reminder at the first session's 3-hour mark and none after the restart at 3:10 — technically per-session compliant, substantively a 5-hour stretch with a single nudge.

The fix tracks the cadence on the daily engagement clock the runtime already keeps for caps: reminders now fire on cumulative minor engagement, restarts irrelevant. The next audit shows maximum inter-reminder gaps of 2:58 across the minor population. The story is invented; the pack wording, the floor and the two clocks are the product's own.

Frequently asked questions

How often must break reminders fire for known minors?

At least every 3 hours, per California's pack — a maximum interval (floor of frequency), so more frequent reminders comply and a first reminder later than 3 hours does not. Colorado's pack promises break check-ins during long sessions without a stated cadence.

Who delivers the reminder?

The free disclosure snippet, in minor mode. On Pro and Team the runtime adds operator-configured session and daily caps that enforce breaks (enforce_break) behind the reminder's offer.

Is the 3 hours per session or cumulative?

The pack does not specify session mathematics; the defensible reading is elapsed engagement per minor across the day (the runtime keeps session and daily clocks for caps). Choose the interpretation that interrupts more — a reminder costs a sentence.

May adults receive the reminders too?

They should not: the cadence is a minor protection, and spraying it at everyone teaches everyone to ignore it. Minor reminders are for known-minor sessions, asserted by the operator's flag.

How do I verify a 3-hour cadence in practice?

By construction in staging (compressed test timings, timer logic against elapsed values) and by audit in production: sample minor sessions weekly and confirm no inter-reminder gap exceeded the floor, using the counts-only records.

Keep going