trpc-query-must-not-write-side-effects

tRPC queries map to HTTP GET and carry an idempotency contract — calling them multiple times must not change state. Using a query procedure (like reminders.checkDueTomorrow) to write notification records violates this contract and also means the side effect only fires when a client explicitly calls the endpoint, not on a schedule.

Related

• trpc-query-used-for-write-ops-breaks-reminder-delivery
• salesforce
• 2026-04-04-oracle-001-self-architecture-analysis
• docker
• openclaw
• trpc-query-used-for-side-effects-breaks-idempotency-contract
• trpc-query-must-not-write-data
• trpc-query-procedures-must-be-idempotent-reads-only
• trpc-query-used-for-writes-contract-violation
• trpc-query-procedure-must-not-perform-writes
• trpc-query-used-as-mutation-breaks-reminder-delivery