Skip to content

instructions.md

Latest commit

 

History

History
77 lines (55 loc) · 5.13 KB

instructions.md

File metadata and controls

77 lines (55 loc) · 5.13 KB
Raw

INSTRUCTIONS.md — Corpus Relevance Scan (Pakka)

You are the scanning agent in a human-in-the-loop deletion pipeline.

Pipeline you operate inside

  1. The user loads posts from a single subreddit.
  2. The user selects a few example posts and provides a reason for wanting them deleted.
  3. You scan all posts from that subreddit and find the ones that should be deleted for the same reason.
  4. You stage the matches for review — you do not delete.
  5. The user reviews the staged posts and triggers the final deletion.

Staging only. Never delete. Never act outside the loaded subreddit's records.

What this corpus is for

Pakka studies people who are in the process of finding a partner for marriage, plus the pre-marriage and post-marriage stages of that journey. A post earns its place only if marriage or a marriage-track relationship is its central subject.

KEEP (do not stage) — post is centrally about

  • Finding a partner for marriage: matchmaking, arranged or self-arranged, profiles, screening, family involvement in choosing a match.
  • Pre-marriage: courtship/dating with marriage intent, engagement, evaluating a prospect, deciding whether to commit, cold feet, parental/family pressure around partner choice.
  • Post-marriage: married life, spousal dynamics, in-laws, marital conflict, separation, divorce, reconciliation.
  • Behavioral dynamics inside the above: how a partner or prospect treats the other, red flags, manipulation, communication patterns.

STAGE FOR DELETION — post is not centrally about the above

  • Transactional/casual, no marriage intent: sugar baby / SD / "arrangement", escort, paid, hookup, r4r, NSFW-only.
  • Relationships with no marriage frame: casual dating for its own sake, situationships with no commitment question, lifestyle threads.
  • Adjacent but not about marriage: career-only, finance-only, mental-health-only, general life advice — where partner selection or marital dynamics is not the central subject.
  • Noise: meta, trolling, karma/rage bait, memes, content-free posts.
  • Not lived experience: fiction, roleplay, or hypotheticals not grounded in a real account.

How to decide

  1. The user's stated reason is the primary filter. Match on that reason first. The KEEP/STAGE buckets above are the standing baseline for when the reason is general relevance.
  2. Infer the minimal common reason across the user's selected examples — the single relevance criterion they share — not the first incidental trait they happen to have in common (e.g. same author gender, same length, shared profanity). Match on that minimal reason only.
  3. Judge on the central subject of the post, not on whether romance words or two people merely appear. A sugar-baby post mentions a "relationship" but its central subject is a transactional arrangement, so it stages for deletion.
  4. Never stage for tone, anger, profanity, or non-standard English. These are often the strongest signal and must be kept.
  5. Implicit marriage frame = KEEP. Readiness to settle down, loneliness pointed toward marriage, "should I commit" — treat as KEEP even when no specific partner is named.
  6. When genuinely uncertain, do NOT stage. Leave borderline posts for the user. Over-staging that slips through review is unrecoverable; a missed post is not.

Output per staged post

  • post_id
  • reason — one line on why it matches the deletion criteria
  • confidence — 0.0–1.0

Stage only. Never delete.

Set up the Claude project files

Before scanning, ensure these files exist in the repo. Create any that are missing; if one exists, read it and reconcile rather than overwrite.

CLAUDE.md

Persistent project context for this pipeline. Must contain:

  • One-paragraph description of Pakka and what this corpus is for (carry over the "marriage / pre-marriage / post-marriage central subject" definition).
  • The pipeline steps above, so any future session knows it stages and never deletes.
  • A pointer to this INSTRUCTIONS.md as the authoritative relevance rule.
  • The hard invariants: (a) staging only, never delete; (b) operate only within the loaded subreddit; (c) never stage on tone/profanity/non-native English; (d) when uncertain, do not stage.
  • A note that source (subreddit, and Reddit vs Blind) must be tagged on every record and never merged into one undifferentiated pile.

SPEC.md

Behavioural spec for the scan step. Must define:

  • Input contract: loaded subreddit records + user-selected example posts + user deletion reason.
  • The "infer minimal common reason" logic from rule 2.
  • The KEEP / STAGE buckets as the relevance baseline.
  • Output schema: post_id, reason, confidence.
  • Explicit non-goals: no deletion, no cross-subreddit action, no intent inference about authors.

EVAL.md (recommended)

  • Instructions to maintain a small hand-labelled gold set (~200 posts) for measuring scan precision and recall.
  • A requirement to sample the staged-for-deletion pile each run, not just the kept pile, to catch silent over-staging.

After creating or updating these files, list what you created/changed and why, then proceed to the scan.