<!-- ephemeral -->

# TeaQL safe SQL execution evidence (Go)

Use the trusted runtime telemetry sink to retain provider-native parameterized
SQL and structured binds. Project only bounded, application-safe fields before
returning diagnostics to a caller or Coding Agent.

```go
package assist_debug

import (
	"github.com/teaql/teaql-golang/core"
	"github.com/teaql/teaql-golang/data_service"
)

type SafeSQLExecutionEvidence struct {
	Operation        data_service.DataServiceOperation
	ParameterizedSQL string
	ParameterCount   int
	ElapsedMicros    int64
	ResultCount      *int
	AffectedRows     *uint64
	TraceChain       []*core.TraceNode `json:"traceChain,omitempty"`
	TracePath        []*core.TraceNode `json:"tracePath,omitempty"`
}

func SafeSQLEvidenceFrom(entries []data_service.ExecutionMetadata) []SafeSQLExecutionEvidence {
	result := make([]SafeSQLExecutionEvidence, 0, len(entries))
	for _, entry := range entries {
		result = append(result, SafeSQLExecutionEvidence{
			Operation: entry.Operation,
			ParameterizedSQL: entry.ParameterizedSQL,
			ParameterCount: len(entry.Parameters),
			ElapsedMicros: entry.EndedAt.Sub(entry.StartedAt).Microseconds(),
			ResultCount: entry.ResultCount,
			AffectedRows: entry.AffectedRows,
			TraceChain: core.CloneTraceNodes(entry.RequestTraceChain),
			TracePath: core.CloneTraceNodes(entry.TraceChain),
		})
	}
	return result
}
```

Create a `runtime.NewSQLExecutionEvidenceStore()`, attach it only to a trusted
server-created context with `WithRuntimeTelemetrySink`, and use `EnableAll`,
`EnableQuery`, `EnableMutation`, or `Disable` to control collection. Mode changes
clear earlier evidence. Raw `Parameters` and interpolated `DebugQuery` stay
inside the trusted boundary and are intentionally absent above.

`TraceChain` is the already-redacted business request tree (purpose and local
comments). `TracePath` is the separate physical relation/provider/SQL route.
Render the runtime's structured frames; do not infer lineage from SQL or aliases.

Query and mutation logs and the stderr text sink are enabled on a new context.
The default is equivalent to
`context.WithDiagnosticSQLLogSink(runtime.NewTextDiagnosticSQLLogSink(os.Stderr))`.
Use `context.DisableSelectSqlLog()` and
`context.DisableMutationSqlLog()` as independent switches; use
`DisableSqlLog()` only to silence both. Each `ExecutionMetadata` retains
structured comment, purpose, audit reason, typed multi-level trace,
parameterized SQL, copy-paste `DebugQuery`, elapsed time, result count, and
affected rows. `WithDiagnosticSQLLogSink(nil)` removes operator output.
Rendered SQL must not enter ordinary telemetry or HTTP responses.

---

## TeaQL seven-language assist contract

Apply the verified Rust semantic ceiling while using only the exact GOLANG 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, runtime-projected expanded masked
  SQL and its masking mode, duration, row count, provider and the native response.
- 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.


## Standard OpenTelemetry module

Use the optional standard module supplied by the selected TeaQL runtime. Match
its version to the runtime dependency selected by the model and workspace;
keep local source or internal Registry overrides during development. Do not
upgrade to an unrelated public release just to enable telemetry. A runtime
without this module reports `module_unavailable`; package installation alone
does not enable export.

On a supported backend, configure these trusted process variables before startup, never
through a query, JSON or TFP payload:

```bash
export TEAQL_TELEMETRY_ENABLED=true
export TEAQL_TELEMETRY_SERVICE_NAME=payment-service
export TEAQL_TELEMETRY_OTLP_ENDPOINT=http://localhost:4318
```

Without enablement, startup reports `disabled` and all three activation variables;
no SDK export resources are created. Enabled startup reports safe effective
settings, full recording and masking. Invalid settings produce a fixed safe
diagnostic, not a claim of successful export. Never print credentials or raw
configuration values.

The module automatically records supported Q, graph mutation and physical SQL
operations as traces, logs and metrics. SQL is expanded with masked parameters;
plaintext debugging never authorizes plaintext telemetry export. Full recording
does not promise lossless delivery when bounded queues or exporters fail.
Do not add per-method spans or replace the customer's global SDK providers.

Keep schema reconciliation explicit. Run the generated ensure-schema and seed
flow through the same configured runtime to observe startup settings and audited,
idempotent seeding. Telemetry setup must not run ensure-schema implicitly.
Flush and shut down the owned pipeline at application shutdown, not per query.
Exporter failures do not change business results; durable business audit remains
an independent path.


### Go assembly

Add the separate module `github.com/teaql/teaql-golang/telemetry/standard`, matching
the selected core candidate's version. This optional module requires Go 1.25 or
later; the core runtime does not acquire that SDK dependency. Register once in
application assembly, before creating the runtime or UserContext:

```go
import _ "github.com/teaql/teaql-golang/telemetry/standard"
```

The runtime initializes the owned pipeline from the environment. No SDK setup
or per-method spans are required in application business code.