Examples

Django with Synapsor

Keep Django ORM for the web app and use Synapsor for agent-safe reads, proposals, approvals, and replay.

Overview

Django models and migrations stay in place. Add Synapsor for agent-facing workflows where tenant scope, evidence, proposal review, and replay matter.

The Django view or service layer should set SESSION tenant/principal/object values before invoking a Synapsor capability.

Proposal writeback can run from a Django management command, Celery worker, or other trusted process after approval.

Developer notes

Use a read-only database URL for Synapsor, separate from Django's write database credentials.
Prefer Django-created safe views for sensitive models.
Run writeback from trusted server code after approval.
Keep model-provided fields out of HIDDEN bindings.

View shape

views.py

def answer_ticket(request, ticket_id):
    ticket = Ticket.objects.get(id=ticket_id, tenant_id=request.user.tenant_id)

    synapsor.set_session({
        "tenant_id": request.user.tenant_id,
        "principal": request.user.id,
        "current_ticket_id": ticket.id,
    })

    return synapsor.capabilities.invoke(
        "support.answer_ticket_question",
        {"question": request.POST["question"]},
        response_envelope=True,
    )

Examples

bash

synapsor sources create postgres --name django_postgres --url env:DJANGO_READONLY_DATABASE_URL --ssl require --mode live_read
synapsor sources inspect django_postgres --schema public
synapsor sources generate django_postgres --template support-ticket-agent --namespace support