follow sh.E across every channel you use

Pick channels × kinds. Every send is D-KaP-sealed and carries a one-click unsubscribe. Email is fingerprinted (sha256 + RAS + φ) before any seal — your raw address never touches the chain.

channels (pick at least one)

Postmark/Mailgun, sealed unsubscribe link in every send

Slack

paste your incoming-webhook URL below (per-channel, no OAuth)

Personalized RSS

we mint /follow/{token}/atom.xml only carrying your kinds

SMS staged

AgentTelephonyDO bridge — staged for v38.5

Web Push staged

Service Worker + VAPID — staged for v38.5

kinds (pick at least one)

Briefs

executive briefs sealed via D-KaP

Decks

v27 deck bundles (slides + speaker notes)

Directives

/ceo/directive issuances + seals

Sandbox briefs

watermarked /try outputs

On-chain anchors

Base L2 tx confirmations

Pulse

founder feedback log + heartbeat

Leverage tier-ups

v36 leverage gauge crosses a threshold

Weekly review

v34 keep-rate digest, Mondays

slack incoming-webhook URL (only when 'slack' chosen) sms phone (E.164) (staged · v38.5)

privacy posture

· raw email is encrypted-at-rest (AES-GCM, PBKDF2 100k rounds, RAS+φ salt)

· public seals only carry sha256(email|RAS|φ) — never the address

· retention envelope: SEC-17a-4 6-year floor

· one-click unsubscribe in every send + persistent personalized URL

Founder gate (v31 Cloudflare Access bypass): If /follow returns the Access login wall, the founder needs to add it to the bypass list (alongside the existing /, /verify*, /feed.xml, /og/*, /masterclass). Same gate covers /api/follow/*, /follow/{token}/atom.xml. WAF allow-list addition for the epochcore-backtest User-Agent (carry-over from v37) closes the synthetic-monitor path.

v24 apex efe714062b0a271e…

Agent #84 · cascade 7777.77 Hz · φ 1.618033988749895