Problem Mining Loop: five rules and a five-check script (free sample)
by PaperChaseWebb
From the Problem Mining Loop: five rules for a complaint log you can trust (one owner and one buyer type, a link and date on every complaint, quote never paraphrase, money shown not guessed, count people not posts), and a read-only script that checks one log for them.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
problem-mining-loop-five-rules-and-checks-free-sample.md · 8 KB · direct download, no signup
What you end up with
In a few minutes you can see which complaints in your log have no link, are paraphrased, or are counted twice.
What you get
- Five rules for a complaint log
- mine_mini.py: five read-only checks on one complaints-lite.json
- One prompt for all four harnesses
- Worked example: 5 findings, then 0
Who it is for
Anyone keeping a list of buyer pain points who wants to know which entries would hold up.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes to a first result
Sample prompts, free to use
For owners of [your buyer type], read public posts on [one forum or review site] from the last six months. Before reading, open its robots.txt and terms and tell me if they allow this; if not, stop. List complaints about their work in complaints-lite.json: the exact words, the link, the date posted, a made-up label per poster in place of their name, and a grade of gripe, pain, budget or buyer. Do not paraphrase, and do not post, reply or log in. Run mine_mini.py complaints-lite.json and show me the findings.
The rules and the script are in the file.
Free preview of the file
# Problem Mining Loop: five rules and a five-check script (free sample)
Version 1.0, 2026-10-29. By PaperChaseWebb. For founders, consultants and small agencies who want to know what one kind of buyer complains about, in the buyer's own words, before deciding what to build or offer. One Markdown file and one Python 3 script, standard library only. The script was tested on its worked example (5 findings, then 0) and on a missing file (exit 2). It was not run inside any agent harness or on research from a real community.
A list of pain points is easy to make and hard to trust. Some entries were written by a model and never said by anyone. Some were said by one person, several times. Some are paraphrases that drifted from what the poster meant. These five rules keep a small complaint log honest, and the script checks them in one file.
## Install in one line
Save this page as FREE-SAMPLE.md, then:
```
python3 -c "import re;t=open('FREE-SAMPLE.md').read();open('mine_mini.py','w').write(re.search(r'~~~python\n(.*?)~~~',t,re.S).group(1))"
python3 mine_mini.py complaints-lite.json
```
## Five rules
1. **One owner, one buyer type.** A person owns the log and decides what happens next. Each log is about one kind of buyer, so the counts mean something.
2. **Every complaint has a link and a date.** The link goes to the post itself, and the date is when the poster wrote it. No link, no row.
3. **Quote, never paraphrase.** The poster's exact words, 280 characters or fewer. If you caTest record
- Date
- Oct 29, 2026
- What was run
- mine_mini.py on the worked example, a fixed file and a missing file.
- Result
- 5 findings, then 0; exit 2 on a missing file.
- Not run
- The prompt inside a harness or on a real community.
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The sample checks one file against five rules. Source rules with robots.txt and terms, salted poster keys, solicited answers, the read-only fetcher, the report, owner approvals by hash and the fifteen checks are in the full pack.
- On 2026-10-29 mine_mini.py gave 5 findings on the worked example, then 0 on the fixed file, and exited 2 on a missing file. The prompt was not run inside a harness or on a real community.
Questions
Does it read any websites?
No. It reads one file and opens no network connection.
What is in the full pack?
The loop folder with templates, mine.py with salted poster keys, a read-only fetcher that obeys robots.txt, tally, a one-page report and the owner's yes tied to a hash with one use and expiry, fifteen read-only checks with a seeded test set, a skill file, AGENTS.md snippet and Grok Bot rules block, ten prompts and a failure table. $19.
Details
Version 1.0 · Updated Oct 29, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Problem Mining Loop: real complaints, graded and counted, before you build anything
Find out what one kind of buyer complains about, in their own words. Every complaint is a row with the link, the date posted, the exact quote and a salted key in place of the poster's handle, graded gripe, pain, budget or buyer. Clusters count independent posters, not posts, and leave out prompted answers and your own accounts. A cluster is proposed only when enough people at pain or higher, from more than one source, say so and one shows money. Public pages only, robots.txt and terms checked, GET only, and nobody in the community is ever contacted. Proposals wait for your yes at your own terminal; fifteen read-only checks run on the set.
Research Contract: five rules and a five-check script (free sample)
From Research Contract for Agents: five rules for agent research (every claim names its source, quotes word for word with a location, high confidence needs a primary source, two dates on every source, the owner's yes before anything goes out), and a read-only script that checks one research file for them.
Check the Claim: the six questions (free sample)
Six questions, an evidence level label, the add-the-parts check, one prompt and one card template that make any agent with web search check a claim before you use it. Updated to v1.1.
Agent Readiness Self-Check: score one workflow before you hand it to an AI agent
A free self-check for agencies and small businesses. Name the decision, then score one workflow across eight areas (workflow mapped, data access, approval gates, owner per agent, handoffs, cost tracking, security and vetting, measurement) with an evidence rule, three gate rules and a skeptical pass, and read your band and the next steps it allows. v1.1 starts with the decision the score will change, scores unknowns as unknown, adds rules for conflicting facts and lookalike public records, ties every band to the next steps it allows with the Production Readiness Audit before go-live, makes owner approval concrete (prepared and approved status, a one-reply approval line, decisions the agent must leave open, a done test), adds agent files for Grok Bot, Claude Code, Codex and Hermes, a second worked example (missed call to booked job), a readiness folder with a fifteen-check read-only checker, a front door test with four questions to ask anyone selling you an agent install, and a plain note on how it was tested. Still free.
Source Shelf: five rules and a five-check script (free sample)
From the Source Shelf: five rules for a small list of industry reports (one owner, link to the publisher not the post, dated and checked, three questions every time, every figure with its quote), and a read-only script that checks one small file for them.
Compounding Offer Audit: five rules and a five-check script (free sample)
From the Compounding Offer Audit: five rules for scoring an offer on six tests (one owner, six scores and no total, a fact for every score, no 3 on say-so, one change on the weakest test), and a read-only script that checks one small file for them.