📝 Record diagnostic gateway rollout and public verification

This commit is contained in:
Codex 2026-11-10 08:58:24 -08:00
parent a98127c42d
commit d393ba0d50
3 changed files with 7 additions and 7 deletions

View File

@ -1,6 +1,6 @@
# Diagnostic extension: production approval checklist
Local implementation only; no production grants, accounts, views, Secrets or deployment changed by this extension.
Executed 2026-11-10 after explicit combined approval: Mongo views/role/user/Secret, log Role/RoleBinding, and gateway rollout at a98127c4. BCM identity/Secret were NOT created; user agreed to defer unavailable cloud monitoring. Business records and business deployments unchanged. The table below records the approved scope; it is not an instruction to repeat creation.
| Change requiring approval | Exact bounded scope |
|---|---|

View File

@ -1,6 +1,6 @@
# Diagnostic data access: proposed production changes
Status: awaiting authorization. No database account, view, IAM principal or additional log permission has been created.
Status: Mongo and logs approved and deployed 2026-11-10; see production-approval-checklist.md and the external guide. IAM/BCM remain deferred by user agreement. The following documents scope and limitations, not a repeatable creation instruction.
## Mongo

View File

@ -58,15 +58,15 @@ The client honors normal HTTPS proxy environment settings. It never disables cer
Authenticated requests have a 60-per-minute per-key limit; the ingress also applies 2 requests/second per observed source IP with a burst of 10. A 429 requires waiting before retry. Load-balancer source NAT may make the ingress limit shared by clients. Do not run stress tests against production. The gateway logs a short key fingerprint, method and path, not key values. Public/private-CA certificate expires 90 days after issuance; the operator must renew it before expiration.
Share only ca.crt, the assigned key file, this guide and client.py with an approved external Agent. NEVER share ca.key or tls.key. The initial key is for this deployment's operator; provision separate keys before allowing independent external parties. Platform task/customer content and cloud monitoring remain unavailable in this initial release.
Share only ca.crt, the assigned key file, this guide and client.py with an approved external Agent. NEVER share ca.key or tls.key. The initial key is for this deployment's operator; provision separate keys before allowing independent external parties. Annotation/customer bodies remain excluded. Task metadata and structured logs are available in v2; cloud monitoring remains disconnected.
## Planned diagnostic extension — NOT available in the current deployment
## Deployment status — 2026-11-10
Business task diagnosis, bounded structured logs and EIP monitoring are being prepared. Their permission boundary and acceptance criteria are in deploy/diagnostic-gateway/readonly-data-plan.md. Dedicated Mongo view-only and BCM monitor-only identities do not yet exist. Continue using capabilities as the authority; do not call undocumented endpoints or infer that these data sources are already connected.
Version 2 is deployed at the existing HTTPS endpoint (source a98127c4). Task diagnostics and bounded API request logs passed public-interface checks. Cloud monitoring remains disconnected by user agreement because no usable dedicated monitoring identity is available. It returns 503 `bcm_not_configured`, not zero traffic. Resources, replica count and configured 50 Mbps are unchanged.
When historical records have been deleted or logs rotated, the correct result is insufficient evidence. A current successful task cannot explain a historical failure by itself. Synthetic replay must always be labeled synthetic.
A public-only check of the historical IMU incident returned validation failed/attempt 5/imu_invalid, cancelled item and empty assignee (74 ms, 1875 bytes). A request ID from a read-only API health request matched a structured trace (56 ms). These are single samples, not capacity guarantees or proof of the original source-file contents. Missing/deleted history still means insufficient evidence.
## Local v2 implementation (production enablement pending)
## Diagnostic commands
The client additionally supports: