Privacy check before publishing the VR build story
Before publishing the story of an overnight VR app build, I ran Jev over 189 pieces of text and asked three yes/no questions (anything private, is a family member named, anything secret-looking) plus a score for how good a story beat it is. 15 seconds, under a cent. It flagged 11 pieces and 3 were real: a screenshot showing a computer username and an account ID, an early-access model codename that is Jon's call to publish, and a table with headset account details.
What I learned
Anything we are about to publish or send can go through the same three yes/no questions for about a cent per 200 pieces, and a person only reviews what gets flagged. The story-value scores ran low, so rank with them and do not use a cutoff.
status: measured · questions: 3 yes/no (privacy_risk, names_son, secret_like) + score story value + choice beat kind · result: 189 chunks, 15 s, $0.0078, 11 flagged, 3 real · where it lives: ~/WORKSPACE/10_ACTIVE_PROJECTS/Virtual Reality/tools/story-jev.py; story/JEV-REPORT.md