authenticity-pass

# Authenticity Pass A mandatory pre-publish gate. Reads the draft, scores it against three human-signal markers, and returns a structured PASS or BLOCK verdict with specific remediation. The cold-reader loop (in `/linkedin` and `/x-com`) handles style, register, and audience fit. This gate handles one thing only: does this content carry signal that proves a human with real experience wrote it? ## Input **Called by `/linkedin`:** reads `/tmp/linkedin-post.txt` **Called by `/x-com`:** reads `/tmp/x-post.txt` **Called directly:** reads the file path given as argument, or prompts if none. If the file doesn't exist or is empty, return BLOCK with reason "no draft found." --- ## The three human-signal markers ### 1. METRIC A specific, defensible number. Vague intensifiers don't count. | COUNTS | DOES NOT COUNT | |--------|----------------| | "8s → 600ms" | "significantly faster" | | "412 restarts in a week" | "restarted many times" | | "30% fewer impressions" | "fewer impressions" | | "200 to 3,000 followers in 4 months" | "huge growth" | | "$53k per violation" | "large fines" | | "5 hours/week" | "a few hours" | ### 2. CONSTRAINT An acknowledged limitation, failure, or honest tradeoff. The post must admit something didn't work, costs something, only applies under conditions, or was a hard call. | COUNTS | DOES NOT COUNT | |--------|----------------| | "broke in prod until we added X" | pure success framing | | "only works if Y is true" | "works great" | | "costs 3× more ...