TESSERA AI — SYNTHETIC DEMO DATATry with your data →

MONDAY MORNING Tessera AI · 6 drafts awaiting founder approval Drafted overnight · snapshot May 26, 2026

Solenoid drafted six things overnight.

Against the Notion-connector drift from the demand map, every artifact below was drafted by a Solenoid lane and is awaiting your approval. Solenoid drafts; you decide what ships. The gate is the human.

Yesterday's drift snapshot — top finding: Notion connector

Analyst

## Top finding — 2026-05-25 drift snapshot **Add Notion as a first-party connector** is the highest-drift demand item this snapshot: revenue weight 0.16 (top-5), 4 customer asks, **0 builds in flight**. [Observation]4 distinct asks reference this theme across Slack, a sales call, Linear, and a support ticket — 3 of the 4 name Notion explicitly. [Assumption]Mapping the asks to the accounts that raised them puts ~$214k ARR behind the theme; the sales-call account alone gated annual renewal on it. [Hypothesis]With zero builds against a top-5, revenue-weighted theme, this is a true alignment gap rather than work that is simply tracked elsewhere — the contrast the /demo/ceo drill-down surfaces. Recommend promoting to an ADR draft for a connector decision before the theme ages further.

slack://tessera-ai/C0PRODUCT/p1747245300Half our product specs live in Notion. We keep pasting links by hand — a first-party Notion connector would close the loop.
gong://tessera-ai/calls/expansion-q2-cedarbridgeThe prospect runs their whole roadmap in Notion; native Notion ingestion was their #1 must-have before they'd commit to annual.
linear://tessera-ai/TES-402Customer-requested: pull Notion docs into the knowledge base so summaries reference the source page, not a stale copy.

ADR draft — Add Notion as a first-party connector

# ADR (draft): Add Notion as a first-party connector - Status: Proposed — awaiting founder review - Date: 2026-05-26 - Lane: pm (drafted overnight in response to the 2026-05-25 drift snapshot) ## Context [Verified] Four distinct customer asks this snapshot request native Notion ingestion: a product Slack thread, an expansion sales call, a Linear request, and a support ticket. Three name Notion explicitly. [Assumption]The accounts behind these asks represent roughly $214k of ARR, and at least one gated its annual renewal on the capability. [Hypothesis]Tessera-AI customers keep their canonical product specs and roadmaps in Notion, so manual link-pasting is the dominant workaround today and a first-party connector would remove a recurring weekly chore. [Assumption]No existing build addresses this theme — it is a genuine gap, not work tracked under another item. ## Decision Ship a first-party Notion connector in three stages, behind a flag, BYOK-first: 1. A standalone `@solenoid/connector-notion` package (schema + types, no auth) so the surface is reviewable before any credential handling lands. 2. A Notion OAuth flow whose token is stored via the existing BYOK key vault — never logged, never rendered. 3. An ingestion pipe from Notion documents into `@solenoid/knowledge`, idempotent per document revision. [Hypothesis]Staging the work this way keeps each PR ≤500 LOC and lets the OAuth/credential surface be reviewed in isolation from ingestion logic. ## Consequences [Verified] The connector reuses the established BYOK token-storage pattern, so no new secret-at-rest surface is introduced. [Assumption]Ingestion volume for early adopters stays within the current pgmq throughput envelope; if not, we add a per-workspace rate limit before GA. [Hypothesis]Closing this gap converts the at-risk expansion account and removes the most-cited manual workaround, improving the alignment-drift score on the next snapshot. [Assumption]Notion API rate limits require incremental sync with a cursor rather than full re-crawls; the ingestion ticket accounts for this. ## Alternatives considered - Generic webhook ingestion (rejected: pushes mapping work onto the customer; the asks want first-party). - A read-only paste-a-link enrichment (rejected: does not solve the recurring sync chore the asks describe).

slack://tessera-ai/C0PRODUCT/p1747245300Half our product specs live in Notion. We keep pasting links by hand — a first-party Notion connector would close the loop.
gong://tessera-ai/calls/expansion-q2-cedarbridgeThe prospect runs their whole roadmap in Notion; native Notion ingestion was their #1 must-have before they'd commit to annual.
linear://tessera-ai/TES-402Customer-requested: pull Notion docs into the knowledge base so summaries reference the source page, not a stale copy.
zendesk://tessera-ai/tickets/8810Ticket #8810: 'Is there any way to sync our team docs in automatically? Re-uploading every week doesn't scale.'

Notion-link experience — 1-screen mockup

Designer

## Notion connector — 1-screen flow A single connect screen: the user pastes a Notion page URL into the connector card, the card transitions from a dashed empty state to a lit 'connected' state, and an inline preview renders the first ingested page's title + an excerpt. [Hypothesis]Pasting a URL is a lower-friction entry point than an OAuth-first flow, so the mockup leads with paste-then-authorize rather than authorize-then-browse. [Assumption]The preview reassures the user that the right workspace was connected before any bulk sync runs. Themed with the Tessera-AI synthetic palette so it reads as their product, not ours.

slack://tessera-ai/C0PRODUCT/p1747245300Half our product specs live in Notion. We keep pasting links by hand — a first-party Notion connector would close the loop.
linear://tessera-ai/TES-402Customer-requested: pull Notion docs into the knowledge base so summaries reference the source page, not a stale copy.

Bootstrap @solenoid/connector-notion package

Lead-eng

## Intent Scaffold a standalone `@solenoid/connector-notion` package — Zod schemas + types for Notion pages/blocks, no auth, no network. Reviewable surface before any credential handling lands. [Assumption]The package mirrors the existing connector package layout, so this is mostly scaffold + schema. ## Verify `pnpm install --frozen-lockfile && pnpm lint:privacy && pnpm --filter @solenoid/connector-notion build`

linear://tessera-ai/TES-402Customer-requested: pull Notion docs into the knowledge base so summaries reference the source page, not a stale copy.

~300 LOC

Notion OAuth flow + BYOK-stored token

Lead-eng

## Intent Add the Notion OAuth flow; store the resulting token via the existing BYOK key vault. [Observation]Reuses the `@solenoid/byok` storage pattern — no new secret-at-rest surface. [Assumption]The token is never logged and never rendered to the UI; only a connection status is surfaced. ## Verify `pnpm install --frozen-lockfile && pnpm lint:privacy && pnpm --filter @solenoid/connector-notion test`

gong://tessera-ai/calls/expansion-q2-cedarbridgeThe prospect runs their whole roadmap in Notion; native Notion ingestion was their #1 must-have before they'd commit to annual.

~400 LOC

Notion document → @solenoid/knowledge ingestion pipe

Lead-eng

## Intent Pipe Notion documents into `@solenoid/knowledge` over a pgmq topic, idempotent per document revision (ADR 0031 idempotency key). [Hypothesis]Incremental cursor-based sync stays within Notion API rate limits; full re-crawls would not. [Assumption]Ingestion volume for early adopters fits the current pgmq throughput envelope. ## Verify `pnpm install --frozen-lockfile && pnpm lint:privacy && pnpm --filter @solenoid/connector-notion test`

linear://tessera-ai/TES-402Customer-requested: pull Notion docs into the knowledge base so summaries reference the source page, not a stale copy.
zendesk://tessera-ai/tickets/8810Ticket #8810: 'Is there any way to sync our team docs in automatically? Re-uploading every week doesn't scale.'

~500 LOC

This is the Tessera-AI inbox.

Here's mine →