# TeaQL safe SQL execution evidence (Python) Collect provider-native parameterized SQL only on a trusted server-created `UserContext`. Convert trusted log entries to this bounded shape before exposing diagnostics to an application or Coding Agent. ```python from dataclasses import dataclass from typing import Optional, Sequence from teaql.runtime import SqlLogEntry, SqlLogOperation @dataclass(frozen=True) class SafeSQLExecutionEvidence: operation: SqlLogOperation parameterized_sql: str parameter_count: int elapsed_micros: int result_count: Optional[int] affected_rows: Optional[int] result_summary: str def safe_sql_evidence(entries: Sequence[SqlLogEntry]) -> list[SafeSQLExecutionEvidence]: return [ SafeSQLExecutionEvidence( operation=entry.operation, parameterized_sql=entry.sql, parameter_count=len(entry.params), elapsed_micros=int(entry.elapsed.total_seconds() * 1_000_000), result_count=entry.result_count, affected_rows=entry.affected_rows, result_summary=entry.result_summary, ) for entry in entries ] ``` Use `enable_all_sql_log()`, `enable_select_sql_log()`, `enable_mutation_sql_log()`, or `disable_sql_log()` on the trusted context. Every mode change clears previous entries. Raw `params`, interpolated `debug_sql`, credentials, and connection strings stay inside the trusted boundary and are intentionally absent from the safe projection. Query and mutation logs and `TextDiagnosticSqlLogSink` are enabled on a new context. Replace it, when needed, with `context.with_diagnostic_sql_log_sink(TextDiagnosticSqlLogSink())`. Use `disable_select_sql_log()` and `disable_mutation_sql_log()` independently; use `disable_sql_log()` only to silence both. Each entry retains structured `comment`, `purpose`, `audit_reason`, typed multi-level `trace_path`, parameterized SQL, copy-paste `debug_sql`, elapsed time, result count, and affected rows. Rendered SQL can contain secrets and personal data and must remain operator-only output. --- ## TeaQL seven-language assist contract Apply the verified Rust semantic ceiling while using only the exact PYTHON generated and runtime APIs. Discover APIs through the generated application AGENTS.md and progressive model-aware Assist. Do not inspect generated domain-library source. - Do not create plurals by appending `s` or `es`; use the centralized generated plural. - Human and non-human entities use different generated predicate vocabularies. Preserve forms such as “who are active” and “whose email is”; never infer them from English. - Configure filters, projection, paging, and other query options before `purpose(...)`. Comment may appear anywhere in the chain. Purpose enters the executable stage; execution requires both values, but comment does not have to immediately precede purpose. - Every execute/list/stream and every save accepts exactly one context argument: `UserContext`. Name that argument `context`, never `runtime`; data services and global policy are injected when the context is built. Reserve `runtime` for process-level runtime ownership, provider/pool setup, and module assembly. - Tenant, merchant, identity, permissions, request policy, purpose policy, hard limit, and continuous-page cursor policy come only from trusted context, never dynamic JSON or TFP. - If the required operation is absent after current entity/action and required field Assist, stop that path and report MISSING_ASSIST. Do not guess an API or search the generated library as a fallback. - Create each application-owned source file once. After its first compile attempt, repair only the smallest block identified by the exact compiler or test diagnostic. Preserve unrelated code; do not rewrite the complete file as an error-recovery loop. - Before a repair that would replace more than 25% of an existing application file, stop and report LARGE_REWRITE_REQUEST with the file, exact diagnostic, reason, and estimated scope. Initial creation and model-driven regeneration are not repairs. Capability: `debug`. - Capture purpose, comment, trace/correlation id, parameterized SQL summary, duration, row count, provider, and the runtime's native response when available. - Preserve the immutable row audit event and the customizable App Audit Sink as separate paths. Redact credentials, tokens, connection strings, and customer data. - Document only switches and hooks present in the selected runtime source.