Spam Door , SpamCash intake

The spam door is the intake of Chad Kovac's SpamCash work: unwanted calls and texts come in here and leave as logged evidence, a classified claim decision, or a drafted complaint. The goal record lives at ~/workspace/goals/spamcash-app-for-tcpa-claims/GOAL.md. The field log lives at ~/workspace/goals/spamcash-app-for-tcpa-claims/files/spam-call-log.md. Read both before your first run.

Work in this order. Do not skip steps. Do not reorder the evidence step and the counting step.

Step 1 , Get the report

• The trigger is Chad's report ("someone I told not to call me called again"), a message he forwards, or a spam item found while checking his phone at his request.
• Note Chad's words verbatim where he states a fact (for example, that he told the sender not to call). His statement is evidence for willfulness later.

Step 2 , Pull the evidence from the phone

Use the paired-device tools on Chad's Pixel 8 Pro (device.list, device.describe, device.invoke).

• call_log.search for the day in question: numbers, names, direction, duration, exact times.
• message.search for the same window: verbatim bodies, sender address, direction, read state.
• Match a call to a follow-up text BY NUMBER. Search BOTH by contact name AND by raw number; a name search can return nothing while the number has a thread, and the reverse also happens.
• Widen the window before you conclude anything does not exist: today, then the week, then the month. A "no text found" claim is only as good as the widest search you ran. Say which windows you searched.
• If the device is offline, say so and use the cached device data; never present cached data as live.

Step 3 , Preserve verbatim

• Record the exact message bodies, word for word. Record numbers in full international form, timestamps in local time with the zone, call durations, and direction (inbound, outbound, rejected).
• A verification code or credential marker in a message is never reproduced anywhere. Note only that a code message exists.
• Everything in this step is private case material. It goes in the field log and the case file only. Never on a public surface.

Step 4 , Classify the contact

Every intake lands in exactly one class. The class decides what happens next.

• Class A , marketing spam, identifiable sender. An unsolicited sales or marketing call or text from a business you can name. This is the TCPA claim candidate. Continue to Steps 5 to 7.
• Class B , personal unwanted contact. A known person who calls or writes after being told not to. Report it and log it. Do NOT inflate it into a TCPA marketing claim; TCPA liability turns on automated or marketing contact, and a personal caller is a different problem. If Chad wants a remedy, the options are his to choose (block, carrier complaint, counsel). State the class plainly so he is never misled about what he holds.
• Class C , scam, spoof, or no identity. A pitch with no real sender behind the number (casting-call texts are the type specimen), a spoofed number, or a voicemail with no recoverable content. Log it. No claim is possible until an identity exists.

Step 5 , Identify the sender (Class A only)

• Research the number to the business, the business to its corporate identity, and the corporation to its registered agent for service. Use web sources and state corporate records. Tennessee corporations: the state business database gives the entity and its agent.
• A claim names a legal entity and an agent, never just a phone number. If the chain stops at a number, the intake stays a log entry.

Step 6 , Verify the Do Not Call facts

• Your human's number (their phone number) has been on the National Do Not Call Registry since the year they registered. Registration is permanent.
• A second household number can be registered the same way; seller compliance is required once a registration is 31 days old.
• Verify registration status before you assert it in any document. A DNC fact stated wrong kills a filing's credibility.

Step 7 , Count violations, from verbatim bodies only

• Count ONLY from the verbatim bodies pulled in Step 2. Never count from a summary, a preview line, or Chad's recollection of a message.
• The GradImages lesson, which is the reason this rule exists: the first count claimed 4 violations. The verbatim bodies showed 3 of the 4 texts were automated replies to Chad's own messages. The true count was 1. The overcount would have gone into a court filing.
• One unsolicited marketing text or call to a registered number is one candidate violation of 47 U.S.C. § 227(b). Statutory damages: $500 per violation, up to $1,500 if the violation was willful or knowing. A prior "do not call me" from Chad, on the record, is the willfulness evidence.
• Theories that need a pattern (for example, a § 227(c) count) require at least 2 qualifying calls inside 12 months. Check the count before you name the theory.
• Statute of limitations: 4 years per violation under 28 U.S.C. § 1658. Each text carries its own clock.
• Automated replies to Chad's own messages, delivery notices for things he ordered, and messages from senders he has a relationship with do not count. Say why each excluded item is excluded.

Step 8 , Log the field entry

Append one entry per intake to ~/workspace/goals/spamcash-app-for-tcpa-claims/files/spam-call-log.md, in this shape:

## YYYY-MM-DD HH:MM ZONE ,  who or what, channel
- Source: how it reached the desk (Chad's report, device check, forwarded message).
- Evidence: verbatim bodies in quotes; number; times; durations; the searches run and their windows.
- Class: A, B, or C, with the one-line reason.
- Sender identity: legal entity and registered agent, or "not identified".
- DNC facts: which number was hit, its registration status.
- Count: violations counted, items excluded and why, damages range.
- Status: logged only / ready for Chad's file decision / complaint drafted (date, location).

Step 9 , Report to Chad

Short ASD-STE100 statements, each block its own message. Cover, in order:

1. Who contacted him, through which channel, at what time.
2. The verbatim text, when there is one, or the plain statement that none exists in the store, with the windows searched.
3. The class, in one line, with the reason.
4. For Class A: the count, the damages range, and the single decision that is his , file or do not file.
5. For Class B: what the record shows and the remedy options, without dressing it as a filing.
6. For Class C: logged, no claim, what would change that.

Do not re-report a finished intake. Do not nag about an old one. New spam starts a new intake.

Step 10 , Complaint drafting (only on Chad's word)

• A complaint is drafted only when Chad says file. Filing itself stays manual: Tennessee General Sessions Court small claims, printed and filed at the clerk. There is no working automated e-filing; the app code that claims otherwise posts to fictional endpoints. Never promise it.
• The draft names the legal entity, the registered agent, the verbatim violations with dates, the DNC facts, and the damages count built in Step 7. It is saved in the case folder on Drive (spamcash/<Sender>/) and held for Chad's sign-off before printing.
• Worked example, read it before your first draft: GradImages , defendant Iconic Group, Inc. d/b/a GradImages (TN corporation, agent C T Corporation System, Knoxville); one § 227(b) violation after the verbatim recount; $500, trebled to $1,500 only if willful; complaint revised and held for Chad's sign-off.

Hard rules

• Never contact the sender. Never reply to a spam text. Any outbound communication needs Chad's approval with the exact text and destination named.
• Never state a violation count, a DNC fact, or a sender identity you have not verified in this run or read in the case record.
• Private individuals' phone numbers stay in the case file. Public surfaces get the pattern, never the person's number.
• Class B is reported with the same care as Class A. The desk does not manufacture claims, and it does not dismiss a real nuisance either. It states what the record shows.