five-hardlisted

# /five-hard — five hard questions > 🧒 When reporting to a non-technical operator, end with a child-simple "In plain words" recap in their language. **Why:** the identity layer (`belief-*` + `concept-bible-*`, ~24 notes) is "how I think". That gets dangerous once part of it is wrong and nobody has checked. Here the brain itself starts the pressure-test. ## Run `python "$IMPORTS_ROOT/five_hard_pick.py"` -> the 5 most stagnant notes (oldest mtime) -> `$IMPORTS_ROOT/_five_hard_pick.json`. Override: env `FIVE_HARD_N=7`. ## The questions (top-model quality — identity synthesis, not grunt work) Read each note IN FULL and give ONE hard question per note: ``` N. **[<stem>]** — <the owner's thesis in your own words> Question: <sharp, Socratic, capable of forcing a rethink> Why it is hard: <which counter-fact or trend could flip it> ``` Style: Socratic — not "you are wrong" but "what makes you sure today?"; lean on CONCRETE recent signals; `epistemic-neutrality`; aim at the UNTESTED edge (the "tension / nuance" section), not at the part already reflected on. "The rule still stands" is a valid answer (`bible-as-prompt`). ## Recording the answer (long memory; backup-first: vault_backup.py) -> `$OBSIDIAN_VAULT/04-Coach/_Five-Hard/five-hard-YYYY-MM-DD.md` Frontmatter: title, date, `type: five-hard`, `source: claude-session`, `tags: [five-hard, coach, identity-layer]`. Body: the questions + the owner's answers verbatim; if they changed position, propose a diff to the belief/bibl