# Teleo Cloud SQL T3 live-readonly inventory

Captured: `2026-07-10T06:52:27Z`

## Outcome

The authenticated `authuser=5` Cloud Console session proves that project `teleo-501523` currently has exactly one Cloud SQL instance.

- Required tier: `T3_live_readonly`
- Current tier: `T3_live_readonly`
- Status: `done_verified`
- Account: `b***@livingip.xyz`
- Project: `Teleo` / `teleo-501523`

## Current inventory

| Instance | Status | Engine | Region / zone | Availability | Connectivity |
|---|---|---|---|---|---|
| `teleo-pgvector-standby` | Available / runnable | PostgreSQL `16.14`, Enterprise | `europe-west6` / `europe-west6-c` | Single-zone; not highly available | Private IP and PSA enabled; public IP disabled |

Instance count: `1`.

## DB parity routing metadata

- Cloud SQL connection name: `teleo-501523:europe-west6:teleo-pgvector-standby`
- VPC: `projects/teleo-501523/global/networks/teleo-staging-net`
- Private endpoint: `10.61.0.3:5432`
- Private Service Access: enabled
- Public IP connectivity: disabled
- Cloud SQL IAM database authentication: enabled
- Write endpoint: none shown

The DB parity worker must run from a host or connector with private reachability to `teleo-staging-net`, authenticate with an authorized database principal, and issue read-only schema/count queries. A public-IP route is unavailable.

## Other current facts

- Machine: `1 vCPU`, `628.74 MB`
- Storage: `10 GB` SSD, `2 GB` shown used; automatic storage increase enabled
- Automated backups and point-in-time recovery: enabled
- Deletion prevention: enabled
- Latest visible backup: finished on `2026-07-10`
- Two sanitized import operations are shown as successful on `2026-07-08`
- Maintenance: Sunday `06:00-07:00 CEST`; no maintenance currently scheduled
- Observed health issues: auditing not enabled, no password policy, no user password policy

## Claim ceiling

This proves the current Cloud SQL control-plane inventory and private routing surface. It does not prove database names, contents, row counts, schema parity, an application connection from `teleo-prod-1`, production traffic cutover, or failover capability.

## Actions and mutation boundary

The exact live list and instance Overview URLs were read through Chrome. No Edit, Connect, Restart, Stop, Import, Export, Migrate, Clone, Delete, or failover control was activated. GCP writes, DB writes, IAM changes, key creation, service restarts, deploys, and Telegram sends were all zero.

Cleanup readback: the agent-created Cloud SQL evidence tab was closed and no browser handoff tab was retained.

Machine-readable evidence: `gcp-cloud-sql-t3-live-readonly-current.json`.