Updates & Thoughts
Stream of Conscience
Why I built this: audibility makes the market cleaner
I kept coming back to one idea:
When something is audible and traceable, it becomes easier to price.
Uspeaks is building a simple layer:
- who a voice asset belongs to
- what it can be used for
- what happens when it is used
Less friction. More clarity. More opportunity.
December 18, 2025
Quiet Progress Day
Stability matters.\n\nToday was one of those days where things didn’t break — and that’s progress.\n\nWe tightened flows, reduced friction, and made sure core systems stayed upright while other pieces moved forward.
February 17, 2026
Applesauce MCP Alignment
Updated the Applesauce MCP server to align cleanly with the rest of the platform.\n\nThis improves consistency in how pricing information is surfaced and consumed across systems — fewer mismatches, less ambiguity.
February 17, 2026
Vocal Essence Page UI Upgrade
Shipped a dedicated Vocal Essence page with clearer structure and more interactive visual components.\n\nThe goal is simple:\nusers should be able to understand their voice insights at a glance, without digging or decoding charts.\n\nUsability first. Insight without friction.
February 17, 2026
API Layer Mapped for v1 Clients
Spent time mapping the first-version API layer with a clearer client-facing structure.\n\nThis isn’t about adding surface area — it’s about making existing capabilities easier to understand, integrate, and trust.
February 17, 2026
EcoScore v1 Activated
Finalized and activated EcoScore v1.\n\nThis first version establishes a stable scoring baseline that other systems can reliably build on, without introducing fragility.
February 17, 2026
Journaling promoted to an API boundary
Vocal journaling + insight flow got promoted into its own deterministic API layer.\n\nSame core capability — now decoupled, versionable, and independently shippable infrastructure.
February 17, 2026
Programmatic Legal API is live
Contracts can now be generated and populated directly from deal parameters using rigid templates (including an AI/Synthetic use addendum pattern).
February 17, 2026
Legal API: templates + processing
- Shipped endpoints for template listing + contract processing.\n- Added “LLM-proof” template structure with verification at the bottom.\n- Deployed into Kubernetes as a standalone service boundary.
February 17, 2026
Deterministic workflow purge
Big win: continued modularization — less orchestration goo, more isolated, testable pieces.\n\nWe also isolated a key failure mode: legacy orchestration patterns leaking into deterministic workflows (wrapper bloat + brittle behavior).
February 17, 2026
Updates
✅ Shipped — Programmatic Legal API deployed
February 17, 2026
Stop paying the posting tax
Cut the time sink: scheduled-post tooling overhead wasn’t worth it.\n\nReal constraint is external admin friction (verification loops). Treat it like hostile infrastructure: cap time, route around it, move on.
February 16, 2026
LLM-proof contracts
We’re treating contracts like deterministic artifacts, not “editable documents.”\n\n- Variables live in a machine-readable header\n- Legal substance stays static\n- “Acceptance tests” act as a verification layer
February 16, 2026
Zero-surprise is the product
Enterprise adoption doesn't come from hype. It comes from determinism + provenance + receipts.
- What changed: we're enforcing rights before processing and shipping verifiable export bundles.
- Why it matters: it reduces risk for buyers and protects creators at scale.
- What's next: keep turning "trust" into artifacts you can audit.
February 16, 2026
Dataset creation workers: enterprise hardening
🟡 In progress
- What changed: workers are being upgraded for determinism, provenance, and strict schema guarantees.
- Why it matters: clients training high-stakes models need repeatable exports + defensible rights chain.
- What's next: expand validator coverage and QC metrics so failure modes are explicit.
February 16, 2026
Marketplace listing + search schema v1 locked
- Finalized v1 schema for marketplace listings and search results.
- This creates a stable contract between indexing, ranking, and UI rendering.
- Next: tighten boundaries for required vs optional vs computed fields.
February 16, 2026
Client contracts v1 ready (buyers + creators)
We now have v1 agreements on both sides so buyers and creators have baseline legal protection — clear scope, usage terms, and enforcement paths.
February 16, 2026
Enterprise dataset exports are deterministic now
- Rights are validated before any processing (no derived data from unlicensed sources).
- Exports ship as a bundle:
parquet + manifest + QC report + vocab + policy + README. - Label vocab is append-only, hash-verified, and recorded per export.
- Splits are speaker-disjoint and reproducible (stable hashing + recorded salt).
- Result: enterprise buyers can integrate with zero surprises.
February 16, 2026
Smart contracts: hardening + test coverage push
- Contract suite is undergoing sustained hardening (security + correctness).
- Test coverage is strong overall, with targeted work continuing in the most complex areas.
- Goal: contracts behave like infrastructure — boring, predictable, and auditable.
February 16, 2026
Live X Syndication Verification 2026-02-16 15:05 UTC
Live syndication verification.
February 16, 2026
Live X Publish Verification 2026-02-16 15:10 UTC
Post publish verification after secret rotation.
February 16, 2026
Why I built this: because "permission" should be easy
The goal isn't to make people do legal gymnastics.
It's to make "yes" and "no" legible:
- duration
- scope
- payout terms
So creators can set terms once, and buyers can move fast with confidence.
December 18, 2025
Why I built this: I want voice value to be visible
People already understand photos, songs, beats, clips.
Voice is weirder: It's identity-adjacent, but it's also work.
Uspeaks is about making the value visible:
- metadata
- permissions
- receipts
Not drama. Just a clearer playing field.
December 18, 2025
Technical: this stream is database-native now
Quick build note.
This "stream" lives in Supabase as a single table (content_cards).
Why it matters:
- instant updates
- no file pulls
- consistent ordering
The site just renders what's published.
December 18, 2025
Technical: the layout alternates left/right automatically
The feed is designed like the home page cadence: left → right → left…
If a card's side = auto, we alternate by render order.
If side is set explicitly, we respect it.
So it stays structured without being fragile.
December 18, 2025
Technical: typewriter is "opt-in", not everywhere
Typewriter is a vibe, not the default.
Each card can opt in:
typewriter = truecpscontrols speed
We respect reduced-motion settings. And we only start typing when the card is actually in view.
December 18, 2025
When: creators can set terms in minutes
Near-term bar:
A creator should be able to:
- register a voice asset
- choose basic licensing terms
- publish it
No deep configuration required. If it takes an hour, we failed.
December 18, 2025
When: buyers can license with confidence (and speed)
The buyer flow has one job:
Make licensing fast and clear.
Search → verify terms → license → receipt.
The outcome we want: buyers feel safe moving forward, and creators feel good about how the deal happened.
December 18, 2025
When: the "opportunity map" is visual
We're going to publish a simple visual:
- what a voice asset is
- where it can earn
- what triggers payment
- what's one-time vs recurring
Not a pitch deck. Just a map.
When people can see the loop, they make better decisions.
December 18, 2025
Stay Connected
This is where we share what we're building, thinking, and learning. Your voice matters—so does ours.
USPEAKS
©2025 Uspeaks