Deployment

Running Sotto without mocked infrastructure

Release operations for the DevNet-backed product: authenticated email, Redis coordination, and Canton credentials for the Five North ledger API.

Runtime surfaces

Domain	Purpose
`usesotto.xyz`	Main product, signup, employer workspace, employee pay portal, and auditor console.
`docs.usesotto.xyz`	Documentation home. The root path serves these docs directly.
`notifications@usesotto.xyz`	Transactional email sender for verification, invitations, and paid notices.

Release configuration

Application: production URL and stable signing secrets.
Canton: DevNet ledger endpoint, OIDC credentials, operator, reserve, and issuer service.
Redis: Upstash REST URL and token.
Email: Resend API key and an authenticated transactional sender.

Release gates

cd daml && dpm build --all
cd sotto-tests && dpm test

cd ../../app
pnpm tsc --noEmit
pnpm lint
pnpm test
pnpm build
pnpm test:e2e

The live smoke path creates isolated test parties, submits real Canton commands, settles a private payroll, checks employee and auditor views, and confirms that an unrelated script-only party receives zero records.

Email delivery

SPF, DKIM, and DMARC authenticate the sending domain. Inbox placement still depends on mailbox-provider reputation and recipient engagement, especially for a newly registered domain. Sotto therefore uses concise transactional content, one stable sender category, and no open or click tracking.