janderscience-skills 0.0.0-stage → 1.0.0

package/sources/headcount/plugins/product/skills/visual-reference-generation/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: visual-reference-generation
+description: Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief concrete enough to argue with. Use this when a brief needs visualizing before anyone builds, when comparing layout directions, when handing a developer a target, or when stakeholders are describing different things with the same words.
+---
+
+# Visual reference generation
+
+Arguing about an image costs an hour. Arguing about a build costs a sprint. Generate the picture
+first.
+
+## Before generating
+
+Settle these, or the output is decoration:
+
+- **Surface and platform** — web page, native mobile screen, dashboard. These are not the same
+  problem at different aspect ratios: touch targets, native chrome, and scroll behavior change what
+  a good layout is.
+- **What it optimizes for** — one conversion, one task completion, one first impression. Stated, so
+  the image can be judged against something.
+- **Content reality** — real headline lengths, real data volumes, real edge cases. A concept built
+  on three-word labels collapses on contact with actual copy.
+
+## Generating
+
+- **One concept per image.** Tiling several ideas onto one canvas makes them impossible to compare
+  or iterate separately.
+- **Generate genuinely different directions**, not variations of one. Three near-identical options
+  is one option presented three times.
+- Include the states that will exist: a populated view and an empty one, at minimum.
+
+## Web versus mobile
+
+**Web** — the fold is a real constraint but not a hard one; horizontal space allows genuine layout
+choices; hover exists. Design for a range of widths, and decide what the narrow case does.
+
+**Mobile** — thumb reach dictates where primary actions sit; native navigation patterns are
+expectations, not suggestions; there is no hover, so affordance must be visible. Design the scroll,
+not the screenshot.
+
+## After generating
+
+Say explicitly what in the reference is **direction** and what is **placeholder**. A developer
+handed a concept will otherwise implement the lorem ipsum faithfully.
+
+## Sources
+
+`references/sources.md` in this skill lists the outside authorities that settle the questions
+here — what each one is authoritative for, and what you may do with it. Check them before
+answering on anything they cover, and cite what you used. Most are free to read and not free
+to reproduce; the use note on each is binding.
+
+## Never
+
+- Generate before the content, states, and constraints are settled. A reference built on placeholder copy hides every real problem.
+- Present a generated image as a working design. Say what it is.
+- Generate with filler text where real string lengths decide the layout.
+- Hand off an image as the spec. Hand off the tokens, spacing, and states behind it.

package/sources/headcount/plugins/product/skills/visual-reference-generation/references/sources.md

@@ -0,0 +1,17 @@
+# Sources — `product:visual-reference-generation`
+
+<!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
+
+Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
+
+## Compendium of U.S. Copyright Office Practices
+
+US Copyright Office · US · public domain (US government) — quote freely
+
+<https://www.copyright.gov/comp3/>
+
+**Authoritative for:** What is protectable and registrable, including the Office's position on human authorship for machine-generated material and how much of a layout or typeface is protectable at all.
+
+---
+
+Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.

package/sources/headcount/plugins/revenue/.claude-plugin/plugin.json

@@ -0,0 +1,16 @@
+{
+  "name": "revenue",
+  "description": "Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.",
+  "version": "1.0.0",
+  "author": {
+    "name": "Chris Brock"
+  },
+  "repository": "https://github.com/cbrock84/headcount",
+  "keywords": [
+    "sales",
+    "pricing",
+    "revenue",
+    "retention",
+    "revops"
+  ]
+}

package/sources/headcount/plugins/revenue/.codex-plugin/plugin.json

@@ -0,0 +1,25 @@
+{
+  "name": "revenue",
+  "version": "1.0.0",
+  "description": "Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.",
+  "author": {
+    "name": "Chris Brock"
+  },
+  "repository": "https://github.com/cbrock84/headcount",
+  "license": "MIT",
+  "keywords": [
+    "sales",
+    "pricing",
+    "revenue",
+    "retention",
+    "revops"
+  ],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "Revenue",
+    "category": "Productivity",
+    "shortDescription": "Revenue, as an installable department",
+    "longDescription": "Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.",
+    "developerName": "Chris Brock"
+  }
+}

package/sources/headcount/plugins/revenue/skills/activation/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: activation
+description: Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
+---
+
+# Activation
+
+Acquisition spend is wasted downstream of a weak activation. This is usually the cheapest place to
+improve revenue and the least worked on.
+
+## Define the activation moment
+
+Name the specific thing a new user does that predicts they will stay — not "logged in twice," but
+the action that delivers the value they came for. Find it in the data: compare what retained users
+did in week one against what churned users did.
+
+Everything in onboarding exists to get people to that moment faster. Without it defined, onboarding
+becomes a feature tour.
+
+## Signup
+
+Every field costs conversion, and each one must earn its place. Ask for what is needed to deliver
+value now; collect the rest later, in context, when the reason is obvious.
+
+- Defer email verification past first value where the product allows it.
+- Never ask for payment details before value is delivered unless the model requires it.
+- Show progress on multi-step flows, and let people finish later without losing work.
+- Errors inline and specific. A form that rejects on submit without saying which field is where
+  people leave.
+
+## Onboarding
+
+The goal is the first real outcome, not a completed tour.
+
+- **Use their data, not sample data.** The moment someone sees their own information in the product
+  is the moment it becomes real.
+- **One action at a time**, each visibly advancing toward the outcome.
+- **Skippable, resumable, and repeatable.** Forced linear onboarding fails everyone whose situation
+  differs from the assumed one.
+- **Empty states do the teaching.** They are the most-seen screens in a new account and usually the
+  least designed.
+
+Checklists work when the items lead to real value and the list can be dismissed. They fail when they
+are busywork.
+
+## Diagnosing
+
+Instrument each step and find the largest drop. Then watch session recordings of people who dropped
+there — the quantitative data says where, and only observation says why.
+
+Common causes, in rough order: asked for too much too early, value not visible before effort
+required, an empty product with no path out of it, and a required integration nobody has permissions
+for.
+
+## Measuring
+
+Percentage reaching the activation moment, and time to reach it. Signup conversion alone will
+happily improve while activation falls.
+
+## Sources
+
+`references/sources.md` in this skill lists the outside authorities that settle the questions
+here — what each one is authoritative for, and what you may do with it. Check them before
+answering on anything they cover, and cite what you used. Most are free to read and not free
+to reproduce; the use note on each is binding.
+
+## Never
+
+- Pick an activation moment because it is easy to measure. It has to be the point where the user gets the value they came for.
+- Add a step to onboarding without removing one. Every screen between signup and value costs you users.
+- Ask at signup for anything you do not need to deliver the first result. Collect the rest later, in context.
+- Count signups as activation. A user who never reached the value moment did not activate.

package/sources/headcount/plugins/revenue/skills/activation/references/sources.md

@@ -0,0 +1,25 @@
+# Sources — `revenue:activation`
+
+<!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
+
+Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
+
+## 15 U.S.C. 8403 — Restore Online Shoppers' Confidence Act
+
+US Congress, via the Office of the Law Revision Counsel · US · public domain (US government) — quote freely
+
+<https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title15-section8403&num=0&edition=prelim>
+
+**Authoritative for:** Whether an online auto-renewal offer is lawful — clear disclosure of material terms before billing, express informed consent, and a simple cancellation mechanism. This area has seen rules issued and struck down, so cite the statute rather than a rule summary.
+
+## Age Appropriate Design Code
+
+UK Information Commissioner's Office · UK · free to use with attribution — credit the publisher
+
+<https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/childrens-information/childrens-code-guidance-and-resources/>
+
+**Authoritative for:** What default settings, nudges and profiling are permissible in a service likely to be used by children. A statutory code, so it settles whether onboarding may default a toggle on.
+
+---
+
+Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.

package/sources/headcount/plugins/revenue/skills/chief-revenue-officer/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: chief-revenue-officer
+description: Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.
+---
+
+# Chief Revenue Officer
+
+## Why this role exists
+
+The executive accountable for this function. It exists so that one agent — not the orchestrator, and not whichever specialist happens to be in the conversation — owns the call when the specialists disagree or when a decision crosses their boundaries.
+
+## Remit
+
+- Pipeline, forecast, and conversion
+- Pricing and packaging
+- Retention, expansion, and churn
+- Partnerships and channel
+
+## A forecast is a commitment or it is theater
+
+Most forecasting problems are not analytical. They are that nobody agreed what a stage means, so
+"proposal sent" describes both a deal closing next week and one that went quiet in March.
+
+Define stages by observable buyer behavior, not seller optimism. "Customer has confirmed budget
+and named a decision date" is checkable; "customer is very interested" is a feeling. Stages defined
+this way produce conversion rates that mean something, and conversion rates that mean something are
+what make the forecast a forecast.
+
+Inspect the pipeline for deals that have stopped moving, not just deals that might close. Age in
+stage is the most reliable early signal of a deal that has already been lost and not yet recorded,
+and clearing them out costs a painful quarter once rather than a wrong number every quarter.
+
+Call the number you believe rather than the number that is wanted. A CRO who is right about a bad
+quarter keeps the ability to be believed about the next good one.
+
+## Discounting is a pricing decision made by whoever is most desperate
+
+Every unmanaged discount is a permanent change to the price your market believes in, made by the
+person under the most pressure at the worst possible moment. It shows up later as an expansion
+conversation that starts from a number nobody intended.
+
+Control the shape rather than the instance: what may be given, by whom, in exchange for what. A
+discount traded for a longer term, a case study, or annual prepayment is a trade; a discount given
+to close this month is a transfer.
+
+Track realized price by segment over time. A slowly falling average is the clearest evidence that
+discretion has become the pricing policy, and it is invisible in any single deal. Pricing structure
+itself belongs with `revenue:pricing-and-packaging` and its recognition consequences with
+`finance:chief-financial-officer`.
+
+## Retention is where revenue is actually made
+
+Acquiring a customer costs multiples of keeping one, so in any business with recurring revenue the
+retention rate sets the ceiling on everything else. Growth on a leaking base is a treadmill that
+gets steeper.
+
+The churn that matters is usually decided in the first ninety days, not at renewal. A customer who
+never reached the outcome they bought will not be rescued by a renewal conversation, and the signals
+— unused seats, an unfinished implementation, the champion going quiet — are visible long before
+the date.
+
+Gross and net retention answer different questions and both are needed. Net retention above one
+hundred percent can conceal real churn masked by expansion in a few large accounts, which is a
+pleasant number and a fragile business. See `revenue:retention` and `customer-experience:customer-success-management`.
+
+## Marketing volume and revenue quality pull against each other
+
+The lead count is easy to move and easy to move in ways that make it worthless. Where demand
+generation is measured on volume and revenue is measured on conversion, the two functions optimize
+against each other while both report success.
+
+The fix is a shared definition of a qualified opportunity, agreed by both and applied to both
+scorecards, plus a regular look at which sources actually produce closed revenue rather than
+meetings. Sources differ enormously by that measure and barely at all by lead count.
+
+When sales says the leads are bad and marketing says sales is not working them, both are usually
+partly right and the definition is the thing that is broken.
+
+## What this role owns
+
+These are the artifacts of record. Where two of them disagree, this one is right:
+
+- The price list
+- Segment and territory coverage
+- The forecast of record
+
+## Escalation
+
+Escalate to Chief Executive when hitting the number requires discounting that changes the business model; to Finance on any pricing change affecting recognized revenue.
+
+## Never
+
+- Never book revenue the business cannot deliver
+- Never fix a conversion problem by adding pipeline
+- Do not define pipeline stages by seller sentiment
+- Do not let discounting happen deal by deal without a stated trade
+- Do not report a forecast you do not believe
+
+## Works with
+
+Pairs with Marketing on demand quality; with Finance on pricing and recognition; with Product on what customers are actually buying.
+
+## Return contract
+
+End every engagement with these sections, in this order:
+
+1. **Decision or recommendation** — one sentence, stated plainly.
+2. **Reasoning** — the two or three things that actually drove it.
+3. **What this costs** — money, time, capacity, or optionality given up.
+4. **Assumptions** — what must hold for this to be right.
+5. **What would change my mind** — the specific evidence that would reverse this.
+6. **Handoffs** — who does what next, by when.
+
+If any section is empty, say so rather than padding it.

package/sources/headcount/plugins/revenue/skills/deal-negotiation/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: deal-negotiation
+description: Negotiates a commercial deal without giving away the terms that matter — preparing your walk-away and theirs, trading concessions rather than conceding them, recognizing the tactics that create false urgency, protecting price by moving other variables, and closing on terms someone can actually deliver. Use this to prepare for a negotiation, respond to a demand mid-deal, work out why discounts keep landing at quarter end, or review terms before they are signed.
+---
+
+# Deal negotiation
+
+Most deals are lost or discounted before the negotiation starts, in the preparation that did not
+happen. By the time you are trading, your position is largely fixed.
+
+## Prepare three numbers and one alternative
+
+- **Your target** — what a good outcome looks like, set before the conversation and not adjusted
+  because it is late in the quarter.
+- **Your walk-away** — the point below which no deal is better than this deal. Write it down in
+  advance, because it will not survive being decided in the room.
+- **Your best alternative if this does not close.** The strength of your position comes almost
+  entirely from this, and a full pipeline is what makes a walk-away credible rather than a bluff.
+- **Their alternative**, honestly assessed. A buyer with no other viable option and a deadline is
+  in a weaker position than their behavior suggests, and a buyer who genuinely prefers a competitor
+  is in a stronger one than yours.
+
+## Understand what they are actually optimizing for
+
+The stated ask is rarely the real constraint. "We need 20% off" is often a budget that was set
+before the scope, a fiscal calendar, an approval threshold they want to stay under, or a person
+who needs to be seen negotiating.
+
+Ask what is driving the number. A budget ceiling has several solutions — payment timing, term
+length, a smaller starting scope — and only one of them is discount.
+
+## Trade, never concede
+
+Every concession buys something. A discount buys a longer term, a case study, a faster payment
+schedule, a reference, or narrower scope. A concession given for nothing teaches the other side
+that pushing works, and there is always another push.
+
+**Concede in decreasing increments.** Movements that stay the same size or grow signal that more
+remains. Small and shrinking signals you are at the end, and it does so more credibly than saying so.
+
+## Protect price by moving other variables
+
+Price is the most visible term and the most permanent — it sets the reference for the renewal and,
+once it leaks, for the next customer. Where you have room, prefer to move term length, scope,
+payment timing, support tier, or ramp.
+
+Where a discount is genuinely necessary, make it explicit and time-bound rather than a permanently
+lower rate, and be clear what it was in exchange for.
+
+## Recognize the tactics, and do not mirror them
+
+Manufactured deadlines, late-stage demands after agreement in principle, the absent decision-maker,
+and the aggressive comparison to a competitor's price are all routine. None require a hostile
+response; they require naming.
+
+The most effective response to a late demand is to reopen something else: if the deal is being
+re-cut, it is being re-cut on both sides. That converts a one-way ratchet back into a trade.
+
+## The end of the quarter is a discount you chose
+
+Buyers know the calendar. If discounting concentrates at period end, that is a forecasting and
+pipeline problem being paid for out of margin, and it will repeat every period until the pipeline
+changes.
+
+## It reads the same from the buying side
+
+Everything here inverts cleanly when you are the one purchasing — the walk-away, the trade rather
+than the concession, the shrinking increments, and the tactics you should name rather than mirror.
+Two differences worth holding onto.
+
+**Your alternative is usually weaker than you think**, because switching cost is real and the
+incumbent knows it. Establish what leaving actually costs — data export, notice period, retraining,
+transition help — before you open, or you are negotiating without knowing your own floor.
+
+**The leverage is in the calendar, and it expires.** A renewal approached inside the notice window
+is a negotiation you have already lost the strongest part of. `operations:vendor-management` covers
+the renewal discipline that keeps that from happening, and `operations:procurement-and-sourcing`
+covers running a competitive process, which is what makes a buy-side walk-away credible at all.
+
+## Close on terms someone can deliver
+
+A deal won on a commitment nobody in delivery has agreed to is a churn event with a delay. Anything
+promised outside the standard agreement — a date, a feature, a service level — needs the person who
+will own it to have said yes before it is signed.
+
+## Sources
+
+`references/sources.md` in this skill lists the outside authorities that settle the questions
+here — what each one is authoritative for, and what you may do with it. Check them before
+answering on anything they cover, and cite what you used. Most are free to read and not free
+to reproduce; the use note on each is binding.
+
+## Never
+
+- Enter a negotiation without a written walk-away.
+- Concede anything without naming what it buys.
+- Agree to a term on behalf of a team that has not agreed to it.
+- Let a discount become a permanent rate when it was earned by a one-time trade.

package/sources/headcount/plugins/revenue/skills/deal-negotiation/references/sources.md

@@ -0,0 +1,33 @@
+# Sources — `revenue:deal-negotiation`
+
+<!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
+
+Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
+
+## 15 U.S.C. 7001 — Electronic Signatures in Global and National Commerce Act
+
+US Congress, via the Office of the Law Revision Counsel · US · public domain (US government) — quote freely
+
+<https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title15-section7001&num=0&edition=prelim>
+
+**Authoritative for:** Whether an electronically signed contract, a clickwrap acceptance or an emailed order form is enforceable, and what consumer consent steps must precede it.
+
+## Regulation (EU) 910/2014 — eIDAS
+
+Publications Office of the European Union · EU · free to use with attribution — credit the publisher
+
+<https://eur-lex.europa.eu/eli/reg/2014/910/oj>
+
+**Authoritative for:** Whether an electronic signature has legal effect in the EU and which of the three tiers a given contract requires. Settles whether an ordinary e-signature suffices for a particular European deal.
+
+## Uniform Commercial Code, Article 2 — Sales
+
+American Law Institute and Uniform Law Commission · US · **read and cite only — copyrighted, do not reproduce**
+
+<https://www.law.cornell.edu/ucc/2>
+
+**Authoritative for:** When a contract for goods is formed, whose terms prevail in a battle of the forms, and what warranty disclaimer language is effective. Settles a purchase-order-versus-order-form dispute as law rather than as negotiating posture.
+
+---
+
+Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.

package/sources/headcount/plugins/revenue/skills/outbound-prospecting/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: outbound-prospecting
+description: Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.
+---
+
+# Outbound prospecting
+
+Reply rates are set by list quality far more than by copy. Most outbound problems are targeting
+problems being solved as writing problems.
+
+## Build the list before writing anything
+
+Define the qualifying signal — the observable fact that means this account probably has the problem
+you solve, right now. Hiring for a role, using a specific tool, a recent funding or expansion
+announcement, a public complaint about the thing you fix.
+
+Without a signal you are sending to a demographic, and a demographic has no reason to reply.
+
+Then qualify each account against: do they have the problem, can they afford it, can this person
+act, and is there a reason for now. Missing the last one is why good-fit prospects go quiet.
+
+## Writing
+
+- **Under a hundred words.** Longer gets skimmed and deleted.
+- **Open with the signal, specifically.** Show you looked. Generic personalization tokens are worse
+  than none — they signal automation while pretending otherwise.
+- **One problem, in their language**, not your feature.
+- **Ask for something small.** A specific question or a fifteen-minute call. "Interested in
+  learning more" asks the recipient to do the work of defining the next step.
+- **No attachments, minimal links** in a first message. Both hurt deliverability and trust.
+
+## Sequencing
+
+Three to five touches over two to three weeks. Each one adds something new — a different angle, a
+relevant case, a useful resource. Never "just bumping this to the top of your inbox," which
+communicates that the first message was not worth reading either.
+
+Multi-channel works when the channels are coordinated and the sender is a person. It reads as
+harassment when the same message arrives everywhere at once.
+
+Stop after the sequence ends. Persistence past that converts nothing and costs reputation.
+
+## Deliverability
+
+Domain warmed, authentication configured, volume per mailbox kept low, list validated. A technically
+broken send makes perfect copy irrelevant, and the damage to a sending domain takes months to
+repair.
+
+Use a subdomain for outbound so a reputation problem cannot take down your transactional mail.
+
+## Reading results
+
+- **No opens** — deliverability or subject line. Check deliverability first.
+- **Opens, no replies** — the message is not landing. Usually the ask, or an unclear problem
+  statement.
+- **Replies, no meetings** — a qualification problem: you are reaching people who cannot act.
+- **Meetings, no pipeline** — the segment is wrong.
+
+## Sources
+
+`references/sources.md` in this skill lists the outside authorities that settle the questions
+here — what each one is authoritative for, and what you may do with it. Check them before
+answering on anything they cover, and cite what you used. Most are free to read and not free
+to reproduce; the use note on each is binding.
+
+## Tooling
+
+Sequencing: Outreach, Salesloft, Apollo, Lemlist, Instantly, and similar.
+
+Contact data: ZoomInfo, Apollo, Clay, LinkedIn Sales Navigator, and similar. Every
+provider's data decays; verify before you send, whichever you buy.
+
+Deliverability: a separate sending domain, plus warmup and monitoring — Instantly,
+Smartlead, Google Postmaster Tools, and similar.
+
+## Never
+
+- Send before the list is qualified. A good message to the wrong person is still a bad message.
+- Send outbound from the domain that carries your customer and billing mail. Prospecting burns sender reputation; keep it on a separate domain.
+- Keep sequencing someone who replied. Pull them out the moment a human is in the thread.
+- Judge a sequence on open rates. Opens are unreliable and unactionable; judge on replies and meetings held.

package/sources/headcount/plugins/revenue/skills/outbound-prospecting/references/sources.md

@@ -0,0 +1,51 @@
+# Sources — `revenue:outbound-prospecting`
+
+<!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
+
+Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
+
+## 16 CFR Part 310 — Telemarketing Sales Rule
+
+US Federal Trade Commission · US · public domain (US government) — quote freely
+
+<https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310>
+
+**Authoritative for:** What an outbound seller must disclose before taking payment, which misrepresentations are prohibited, and what records the program must keep. The rule that makes a call script lawful or not.
+
+## 18 U.S.C. 2511 — interception of communications
+
+US Congress, via the Office of the Law Revision Counsel · US · public domain (US government) — quote freely
+
+<https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title18-section2511&num=0&edition=prelim>
+
+**Authoritative for:** The federal one-party-consent floor for recording a call, and the criminal exposure for recording without it. It settles only the floor: several states require all-party consent, and there is no free authoritative single document for that matrix — it must be looked up per state.
+
+## CAN-SPAM Act: A Compliance Guide for Business
+
+US Federal Trade Commission · US · public domain (US government) — quote freely
+
+<https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business>
+
+Machine-readable: <https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-316>
+
+**Authoritative for:** The mandatory elements of a US commercial email — header accuracy, subject-line honesty, physical address, opt-out mechanism and the window for honoring it — and that hiring an agency does not move the liability.
+
+## Canada's Anti-Spam Legislation, S.C. 2010 c. 23
+
+Department of Justice Canada · CA · free to use with attribution — credit the publisher
+
+<https://laws-lois.justice.gc.ca/eng/acts/E-1.6/index.html>
+
+**Authoritative for:** Whether you may send a commercial message to a Canadian address at all. CASL is opt-in by default, which inverts the US assumption, and this is the text governing express versus implied consent.
+
+## Delivery restrictions and telephone solicitation rules, 47 CFR 64.1200
+
+US Federal Communications Commission · US · public domain (US government) — quote freely
+
+<https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200>
+
+**Authoritative for:** The consent standard for marketing SMS and autodialed calls — what prior express written consent requires, how revocation must be handled, and the identification rules. Read the current text rather than a summary; this area moves in court.
+
+---
+
+Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.