# Cloud SQL Studio parity gate

Captured UTC: `2026-07-10T06:57:22.085Z`

## Outcome

Cloud SQL Studio opened successfully for `teleo-pgvector-standby` under the authenticated `b***@livingip.xyz` Console session. The database login dialog did not provide an enabled existing IAM principal: IAM database authentication was disabled in the dialog, built-in authentication was selected, and that path required a password credential.

The lane stopped before authentication. No database session was established and no SQL ran.

- Required tier: `T3_live_readonly`
- Current database-parity tier: `T0_spec`
- Live gate evidence: `T3_live_readonly`
- Status: `blocked_with_artifact`

## Target verified from the live control-plane evidence

- Project: `teleo-501523`
- Instance: `teleo-pgvector-standby`
- Connection: `teleo-501523:europe-west6:teleo-pgvector-standby`
- Engine: PostgreSQL 16.14
- Endpoint: private-only `10.61.0.3:5432`
- Network: `teleo-staging-net`
- Instance flag: `cloudsql.iam_authentication=on`

## Exact gate

The Studio login surface exposed no enabled existing IAM database principal for this Console session. The selected built-in authentication route requires a raw database password. Using that password, creating a database user, changing IAM, or granting access is outside this lane's hard ceiling.

An operator can complete Studio login independently with an already-existing authorized principal, without sharing credentials with Codex, and then tell Codex the SQL editor is authenticated. Otherwise, IAM/user enablement must be handled by a separately authorized write lane.

## Not proven

No current database name, principal identity, transaction-read-only result, schema presence, table counts, proposal IDs/statuses, selected row identities, or GCP-versus-VPS comparison was read.

The planned `BEGIN TRANSACTION READ ONLY` query was not executed and therefore is not counted as evidence.

## Cleanup

- `Authenticate` was not clicked.
- No browser SSH was opened.
- Chrome was finalized and the agent-created Studio tab was closed.
- No database session or transaction remains open.
- No GCP, database, IAM, credential, key, service, deploy, or Telegram mutation occurred.

Machine-readable evidence: `gcp-cloudsql-studio-parity-gate-current.json`.
