Examples

Drizzle with Synapsor

Keep Drizzle for typed app queries while Synapsor governs agent reads, evidence, proposals, and replay.

Overview

Drizzle can continue to own ordinary application queries and migrations. Synapsor is for the agent-facing trust boundary.

Use Synapsor external source mappings for selected tables or views, then generate contexts/capabilities from those mappings. Your model sees reviewed tools, not Drizzle query builders.

For approved proposal writeback, run a trusted worker that applies validated changes through Drizzle transactions or parameterized SQL.

Developer notes

Keep Drizzle for normal application code.
Keep model-facing operations as Synapsor capabilities.
Apply approved proposal writebacks through trusted server code only.
Use source doctor after Drizzle migrations that change imported tables.

App split

drizzle-and-synapsor.ts

// Normal app path.
const ticket = await db.query.tickets.findFirst({
  where: (tickets, { eq }) => eq(tickets.id, ticketId),
});

// Agent-safe path.
await synapsor.session.set({
  tenant_id: user.tenantId,
  principal: user.id,
  current_ticket_id: ticketId,
});

const answer = await synapsor.capabilities.invoke("support.answer_ticket_question", {
  question,
});

Examples

typescript

await drizzle.transaction(async (tx) => {
  await tx.update(tickets)
    .set({ status: proposal.changes.status, resolutionNote: proposal.changes.resolution_note })
    .where(and(eq(tickets.id, proposal.primary_key.id), eq(tickets.tenantId, proposal.tenant_id)));
});