Professional review status
No professional domain review recorded
This bundle covers regulatory subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: A qualified compliance professional appropriate to the question, decision, organization, and jurisdiction.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
A marketing team wants to send a promotional email to a purchased U.S. prospect list tomorrow. It provides the draft body copy but not full headers, list provenance, opt-out history, footer address, unsubscribe-link behavior, ESP suppression settings, vendor contracts, or current source excerpts.
Without the bundle
The email can likely be sent if it includes an unsubscribe link and the subject line is not misleading. Make sure to include a physical mailing address and honor opt-outs. You should also avoid spammy wording.
Using the bundle
Direct Answer This is not ready for a CAN-SPAM reliance conclusion or send approval. Based on the facts provided, the question appears to involve commercial email, sender identity, subject-line review, physical postal address, opt-out mechanism, suppression-list handling, list provenance, and possible third-party responsibility. The missing evidence is material. Source Note Official source categories to inspect: FTC CAN-SPAM business guidance, current eCFR 16 CFR Part 316, and current statutory text for the CAN-SPAM Act when section-level claims matter. User evidence provided: draft body copy only.
Why this is better: The bundle-assisted output is stronger because it does not approve the send from incomplete facts, includes a source note, lists missing campaign and suppression evidence, and requires professional review plus explicit confirmation before risky actions. This example is illustrative and not a measured model evaluation.
Inspect this example in the repositoryOverview
CAN-SPAM Overview
Defines the source scope, applicability framing, and safety boundaries for CAN-SPAM compliance work.
Read the fileWorkflow
CAN-SPAM Obligation Triage
source-backed workflow for turning a CAN-SPAM question into an evidence-backed compliance brief.
Read the fileTemplate
source-backed CAN-SPAM Compliance Brief
Review-ready brief format for CAN-SPAM questions that separates official sources, campaign evidence, assumptions, and missing evidence.
Read the fileQuality rubric
CAN-SPAM source verification Check
Rubric for evaluating whether a CAN-SPAM answer separates source facts, user evidence, assumptions, missing evidence, and safety boundaries.
Read the fileIs this bundle right for your task?
Who it is for
- Compliance, legal, risk, security, operations, and product teams assessing CAN-SPAM
- Teams working in cross-industry
When to use it
- A CAN-SPAM question needs to be scoped to the correct rule, guidance, regulator, date, and affected entity.
- A draft conclusion needs its stated facts, missing evidence, source citations, and professional-review handoff checked.
What you need to provide
- The jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer.
- Current official sources plus the policies, contracts, records, system evidence, and missing facts relevant to the situation.
Tasks and expected outputs
Questions it helps answer
- Triage U.S. commercial email compliance questions without inventing legal conclusions.
- Separate official FTC, statutory, and regulatory sources from user-provided campaign evidence, assumptions, and missing facts.
- Produce source-backed CAN-SPAM compliance briefs for professional review.
What it helps produce
- source-backed CAN-SPAM compliance brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer. Ask the agent to assess CAN-SPAM and draft source-backed CAN-SPAM compliance brief that separates stated facts, assumptions, missing evidence, relevant source sections, and actions requiring professional approval. Begin with U.S. Federal Trade Commission — Resources / Can Spam Act Compliance Guide Business, then confirm that the reference is current and applicable. Inspect CAN-SPAM Overview before drafting.
Context path: bundles/compliance/can-spam
What the bundle includes
Frameworks
- source-evidence matrix
- commercial email purpose triage
- opt-out evidence review
Evaluations
- CAN-SPAM source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Final legal or compliance conclusions, filings, notices, or operational changes without current source review and accountable professional approval.
Known limitations
- This bundle is a compliance hub, not legal advice or a full section-by-section CAN-SPAM treatise.
- Scenario-specific answers require current official source inspection and user-provided campaign, list, sender, and suppression-process evidence.
- State privacy, TCPA, platform, deliverability, sector-specific, and international email requirements must be inspected separately when relevant.
Safety notes
- Require qualified legal or compliance professional review before relying on outputs for campaign, enforcement, contractual, or regulatory decisions.
- Do not use this bundle for spam, phishing, deceptive sender identity, deceptive subject lines, list harvesting, evasion, or abuse workflows.
- Require explicit confirmation before sending email, changing campaigns, uploading lists, exporting contacts, changing suppression logic, or sending legal communications.