Security, multi-tenancy & honest compliance boundaries
Supply-chain contracts contain pricing schedules, SLA penalties, and customs records that cannot leak across tenants or unvetted tools. Here is exactly how SCA enforces boundaries—and where managed cloud inference carries important residency nuance.
Architectural safeguards shipped in @sca/web
Tenant Data Partitioning
Strict company_id foreign keys across specialists, revisions, KBs, chunks, conversations, messages, and run_events verified server-side on every request.
Tested across isolated tenants (NorthStar Logistics, Balkan Freight, Alecs CORP).
Knowledge Access Split
Separate retrieval_use (ground answers safely) from view_content (open source chunk text or raw PDF passages) by user or department team.
Configured per Knowledge Collection and Department Group.
Write Connector Guardrails
State-changing tools declare require_approval, display exact JSON parameters inline, hash payloads with SHA-256 idempotency keys, and expire after 2 hours.
Live inside Direct Threads & Tools Catalog governance screens.
Prompt-Injection Isolation
SearXNG external web results remain delimited tool observation blocks—never merged into system instructions or bypassing approval gates.
Enforced in group and specialist orchestrator pipelines.
Revision Rollback & Secrets
Specialist edits append immutable specialist_revisions rows for instant comparison/restore; API keys stay encrypted server-side only.
Never exposed to browser bundles or client localStorage.

ADR-005 Transparency: Inference Processing & EU Data Residency
Your PostgreSQL application records, uploaded customer SOPs, vector chunks, and company settings stay partitioned inside your tenant deployment. However, under ADR-005, requests dispatched to default DigitalOcean Serverless Inference endpoints do not carry strict EU-only physical execution guarantees on prompt payloads.
For enterprises requiring contractual EU-only model hosting, SCA’s provider adapter contract allows connecting dedicated EU VPC or self-hosted endpoints without changing any workspace UX or specialist workflows.
Read model routing & ADR-005 docs