[RobGrafrath]

What this changes and why

MOD-US-0003 supplies the United States federal values that the federal Compliance Pack, compliance.us, feeds into the contact window and contact frequency counter of HIVE-0010. HIVE-0010 builds the mechanisms and holds no values, so without this decision the federal pack had nothing to state. Rob Grafrath asked for it after #30.

The values were read from the text of Regulation F, 12 CFR part 1006, sections 1006.6 and 1006.14, and their official interpretation on the Consumer Financial Protection Bureau's site on 2026-10-11. Every statement of law is flagged as needing verification by someone with compliance standing, and the decision cites the section or comment behind each.

• The window runs from 8:00 a.m. through 9:00 p.m., local time at the consumer's location, on every day and for every channel, from section 1006.6(b)(1)(i).
• An electronic message is timed when the collector sends it, so the check runs at sending, from comment 6(b)(1)(i)-1.
• When the location information conflicts, contact must be convenient in all of the locations the consumer might be in, from comment 6(b)(1)(i)-2, so the pack requires the moment to fall inside the window in every candidate zone that the Locale Module returns.
• The consumer's prior consent given directly to the collector is the window's exception, from section 1006.6(b)(4)(i), and the check honors it only when it is on record.
• The call limits are no more than seven calls to a person about a debt within seven consecutive days, and no call within the seven days that begin on the date of a conversation with the person about the debt, from section 1006.14(b)(2).
• Calls placed with recent direct consent, calls that do not connect, calls to the persons listed in section 1006.6(d)(1)(ii) through (vi), and calls to a number that turns out not to be the person's do not count. A ringless voicemail and a call that reaches voicemail count, and a text or an email does not.
• A call about several debts counts toward each of them, a call that names no debt counts toward one debt the collector chooses, and student loans serviced under one account number count as one debt, from section 1006.14(b)(4) and its comments.

These are consumer debt rules. As Rob Grafrath pointed out, the Fair Debt Collection Practices Act and Regulation F govern consumer debts, so the pack applies the window and the call limits only to a debt whose debt type declares the consumer regulatory nature, the standardized property that HIVE-0009 already gives every debt type, and a debt declared commercial is outside them. MOD-US-0001's validation notice rules are scoped the same way. The rules for collecting commercial debt in the United States need separate research, recorded as a new open question, and will be stated in their own decisions.

Interacting decisions

• HIVE-0010, from Add HIVE-0010, contact windows and contact frequency #30: the decision configures its window and counter, and HIVE-0010 now points here for the United States federal values instead of to a future decision.
• MOD-US-0002, from Add MOD-US-0002, the United States country layer #29: the consumer's candidate zones come from the US Locale Module.
• MOD-US-0001, from Rename account to debt and add multi-level debt grouping #27: the same pattern, federal values as Compliance Pack content with their sources and flags.
• WAX-0008, from Draw clean lines between modules, locale packs, compliance packs, and boilerplate packs #28: each value records its source, legal force, effective date, and verification status.
• HIVE-0009: the debt type declares the regulatory nature, consumer or commercial, and Compliance Pack rules read it. MOD-UNSECURED-0001 already declares its debts consumer.
• HIVE-0010, from Add HIVE-0010, contact windows and contact frequency #30, now says that a rule names the debts it governs by these declared properties, so a rule written for consumer debt never reaches a debt declared commercial. MOD-US-0001, from Rename account to debt and add multi-level debt grouping #27, now states the same scoping outside its Decision section.
• WAX-0001: a call records the debts it concerns through the communication aggregate's covered debts, so the counts follow the rule for more than one debt.
• OPEN-QUESTIONS.md gains "Commercial collection rules in the United States" for the separate research on commercial debt.
• OPEN-QUESTIONS.md, from Add HIVE-0010, contact windows and contact frequency #30: times a consumer has said are inconvenient, and how the collector may respond when the consumer initiates contact at such a time, belong to the restriction mechanism recorded there.

If this touches decisions/wax/

It does not. No Wax decision changes.

Version bumps

MOD-US-0003 is new, Proposed, at 0.1. HIVE-0010 and MOD-US-0001 change only outside their Decision sections, HIVE-0010 to name MOD-US-0003 and to say that rules select debts by their declared properties and MOD-US-0001 to state its consumer scope, and as proposals at 0.1 they take no bump.

Choices this draft makes

1. HiveAR enforces the call limits as limits, although the rule states them as presumptions of compliance and of violation. An agency can set stricter values.
2. For a call that names no debt, the check permits the call when at least one of the person's debts has room under both limits, and it records the call against such a debt.
3. The seven consecutive days are counted as calendar days in the zone the window uses.
4. The window applies to every channel through which the agency communicates with a consumer, and letters are not singled out.
5. Federal law sets no count for email or text messages, so any limit on messages is the agency's own rule. Third-party location contacts under section 1006.10 and state limits are left to later decisions and to the state packs.
6. Consumer or commercial is read from the regulatory nature that the debt type declares, as Rob Grafrath set it, so a debt type that could be either would need to be split into two debt types or given a per-debt override.
7. Phasing puts the window, the limits, the quiet period, the exclusions, and counting by debt in v1, and the prior-consent exception, which needs consent recorded as evidence, in v2.

Stacked on #30

This pull request is based on #30, which sits on #29, #28, and #27, because it configures HIVE-0010 and refers to MOD-US-0002. Its base is the contact-timing branch, and when #30 merges, its base moves on.

Checklist

• I read the decisions neighboring this change, not just the file I edited.
• New or retitled decisions have a matching line in INDEX.md, and front matter follows CONTRIBUTING.md.
• python3 scripts/validate.py --base main passes locally, or I am relying on CI to tell me.
• No pricing, rates, market or customer allocation, consumer data, or client-confidential information.
• Claims about law or regulation are flagged for verification, not asserted.
• Commits are signed off (DCO). If I forgot, I will post the retroactive sign-off comment per CONTRIBUTING.md.
• I license this contribution under CC BY 4.0 (prose) and Apache 2.0 (embedded code samples).

🤖 Generated with Claude Code