01 / Inspect
Start with the evidence already inside OpenWaya.
Waya Lens request inspection is built in. It exposes bounded request and attempt metadata, timing, safe error classes, token availability, trace correlation, and the settled OpenWaya charge when available. It does not expose prompts, responses, keys, raw upstream errors, or managed supplier identities.
02 / Export
Export the story, not the content.
Waya Lens export is metadata-only, asynchronous, default-off, and currently supports one verified destination type: OTLP/HTTP JSON over HTTPS at the collector's /v1/logs endpoint. The receiver should deduplicate records by eventId because delivery is at-least-once.
{
"eventVersion": "openwaya.customer-observability.v1",
"eventType": "request_state",
"requestStatus": "succeeded",
"tokenUsage": { "state": "unknown", "input": null, "output": null, "total": null },
"openwayaCharge": { "amountUsd": null, "finality": "pending" }
}03 / Controls
Keep consent and operations separate.
Prompt and response capture remains a separate per-request opt-in with encrypted storage, bounded retention, audited restricted reads, and recent strict MFA. Metadata export never enables capture. External copies follow the receiving destination's retention and access policy, and sent records cannot be recalled by OpenWaya.
- Credentials are encrypted and write-only; they are never returned after setup.
- Synthetic tests contain no customer request content.
- A global shutdown stops external sends without stopping inference or settlement.
- OpenWaya trace IDs correlate internal segments but do not authorize access or instrument an external application.