Sunday, June 28, 2026

Don't summarize the expert — cite him, and let the reader check your work.

The biggest build day in a while. Two different products got the same new spine on the same day: take a creator's video, decode it into a grounded, cited, advice-safe brief, and let a reader ask it questions. Plus the boring fix that made all of it safe to ship — a real database migration runner.

Shipped

• Ask Plutus, end to end on PaidDaily — built the whole creator-intelligence pipeline: pull a trader's YouTube video for zero cost, decode it into a structured brief, run it through a groundedness gate so it can't invent claims, index every brief, and let you ask questions across the corpus with numbered citations back to the source
• Cross-creator consensus — a layer that synthesizes what multiple creators are actually saying about the same asset, plus a credibility score so a loud voice with a bad track record doesn't get equal weight with a careful one
• Public read pages + Ask Plutus chat — shipped the public directory, per-creator profiles, per-brief views, and an embeddable "Ask Plutus" chat that persists your conversation and rebuilds its evidence trail when you come back
• Sage becomes "Mystics" — renamed the creator surface to Mystics and broadened it past astrology, shipped the free public artifact tier so anyone can read a decoded outline, and stood up a general "Ask Sage" chat
• The Astrolabe design system — laid the foundation for Sage's new visual language and a proper Users admin console with audit logging and account actions
• A real migration runner — replaced hand-applied database changes with a proper runner and a ledger that tracks exactly what's been applied where; this is the thing that ends the silent drift between environments

Notes

The unglamorous star of the day was the migration runner. Everything above ships database changes, and until today I was applying them by hand and trusting my memory of what had run where — which is how staging and production quietly diverge until something breaks in a way you can't reproduce. The ledger makes "what's actually applied" a fact you can query instead of a thing you hope. The flashy work was the two decode pipelines; the work that let me sleep was the boring one underneath them. The design principle that ran through all of it: never summarize an expert in your own voice — quote them, cite them, and gate the output so the reader can always check what the machine claims against what the source said.