Examples

Rails with Synapsor

Keep ActiveRecord for Rails and use Synapsor for reviewed agent capabilities, evidence, proposals, and replay.

Overview

Rails and ActiveRecord remain the normal app path. Synapsor is added at the agent boundary, where the model needs a reviewed tool rather than raw database access.

The controller or service object sets trusted SESSION values, then calls Synapsor through the Node/Python client, an HTTP client, or a small service wrapper.

Approved proposal writeback can be applied by a Rails job using ActiveRecord transactions and Synapsor idempotency keys.

Developer notes

Keep ActiveRecord as the normal write path.
Use Synapsor capabilities for model-facing agent tools.
Use a read-only database user or safe views for source access.
Run approved writeback from a trusted Rails job, not from model output.

Controller/service shape

ticket_agent.rb

ticket = Ticket.find_by!(id: params[:ticket_id], tenant_id: current_user.tenant_id)

synapsor.set_session(
  tenant_id: current_user.tenant_id,
  principal: current_user.id,
  current_ticket_id: ticket.id
)

result = synapsor.invoke_capability(
  "support.answer_ticket_question",
  question: params[:question],
  response_envelope: true
)

Examples

bash

synapsor sources create postgres --name rails_postgres --url env:RAILS_READONLY_DATABASE_URL --ssl require --mode live_read
synapsor sources import rails_postgres --schema public --tables tickets,customers,policy_chunks --tenant-column tenant_id
synapsor sources generate rails_postgres --template support-ticket-agent --namespace support