The honest ledger.

The Content pack now closes the loop from draft to traffic:

• Post bodies are claims, so version history is supersession: every revision is attributable and reversible.
• Publish flips editorial state through the same approval discipline as everything else, and a scheduled publisher automation handles timed releases.
• Public content API. Published posts serve over a cached, key-authenticated API, so your site renders straight from the substrate.
• Attribution. Because the site script and your content live in one graph, “which posts drive paying customers” is a pinned view, not a data project.

Also this month: the sustained-load gate passed on live infrastructure (1,000 events per second for a full minute, 100% accepted), and workspace timezones became changeable with every schedule re-armed correctly in the new zone.

The substrate grew the everyday verbs:

• Human writes. Inline fact editing, add-a-fact, and schema-driven New Record forms. Your edits travel the same claims path as everything else, so provenance says “you, today” instead of nothing.
• Boards that write back. Dragging a deal to a new stage proposes a stage claim, with the same receipt discipline as any other fact.
• Tasks and runs. A tasks surface with keyboard triage, and a runs ledger under every automation showing each execution and its cost.
• Sender identities and sequences. Verified sending addresses with reply routing; multi-step sequences that wait, re-check their guards on every resume, and stop the moment someone replies. A mid-sequence merge cannot cause a double-send.
• The composer. Answer a thread from the record page; the send waits as an approval with the real draft, threading headers intact.
• CSV import. The migration on-ramp: upload, map columns, and rows land as claims with the import as their source.

• Self-service. Sign up with email and password and provision a workspace yourself; no sales call, no waitlist. Multi-workspace users get a switcher in the masthead.
• The UX pass. All five surfaces rebuilt around a founder with five minutes: a command palette from anywhere (typing free text asks the graph), a live Inbox count in the chrome, receipts collapsed under every Ask answer, merge proposals with evidence chips and entity names, keyboard triage (j/k/a/r) in the Inbox, and citation hover that works from the keyboard too.
• Semantic search. “Who was unhappy about pricing?” resolves through the semantic index in both Ask and the MCP endpoint.

• Packs. The Agency GTM pack (companies, deals, pipeline board, follow-up automation) and the Content pack (posts, editorial board, scheduled publishing) install in one approval batch and compile into artifacts you own: forkable, diffable, reversible.
• Policies. Plain-language policy requests compile to a formal policy plus a golden decision corpus that gates the compile itself. Policy changes show a counterfactual replay (“yesterday under the current policy vs the candidate”) before approval.
• Tenant MCP. Every workspace now exposes a scoped MCP endpoint with OAuth 2.1. External agents get query, memory.read, draft.create, intent.propose, and task.create, within your policies, with every call logged and metered.

Describe recurring work (“every trial that goes quiet for 5 days, send a personal check-in unless they have an open ticket”) and the Compiler produces a workflow artifact.

Before it goes live, Wavetable replays it against your real history in shadow mode and shows the report: how many times it would have fired, with the actual drafts. Approve from the Inbox; it runs deterministically from then on.

Structural safety shipped with it: sends stay gated behind approvals, blast-radius limits block over-broad automations (an intent touching 500 entities is stopped pending approval, not politely warned), and every run is reproducible from its trace.

“Track deals with stages and amounts, deals belong to companies” now produces a migration diff you approve, a live projection, and a pipeline board view, all as versioned artifacts.

• Canvas: a workspace grid of pinned views, shared and explicitly versioned.
• Promote to pinned: a good Ask answer becomes shared infrastructure through the Compiler, with governance.
• Artifact browser: git-like history for your schema and views. Diff any two versions; rollback restores the prior state and leaves your claims untouched.

Connect Gmail and Stripe, paste the site script, and watch people, companies, revenue, and pageviews assemble into one graph.

• Identity resolution links the same person across email, payments, and site visits. Deterministic keys merge automatically; probabilistic matches only ever propose, because a wrong merge is the cardinal sin. Precision gate: 0.995 on our labeled truth set.
• Cited memory. Every record carries a written narrative where every sentence maps to the claims and events that support it. A sentence the generator cannot cite does not ship.
• Ask. The command bar answers questions like “which pages did my best customers visit before they first paid?” with a receipt: the exact read-only query, row count, and plan hash.

The foundation every other feature stands on. Every fact in Wavetable is now a claim with provenance: source events, asserter, confidence, status. Connectors propose; a serialized adjudication loop per workspace decides; projections are caches that can always be rebuilt from accepted claims.

Also in this release: per-workspace physical isolation (one database and one coordinating runtime object per tenant), crypto-shredding erasure primitives, and property-based tests that prove projection rebuild is idempotent under random histories.