Telemetry

The Honesty Principle

The Honesty Principle is the product's differentiator: ArmorIQ Tools does not invent numbers. Usage is read from the assistant's own records, not estimated, and a protection claim appears only when there is real evidence behind it.

In practice:

• A session with no recorded tool traces shows "telemetry unavailable," not a reassuring empty dashboard.
• A failed data request shows "unavailable," not zero. The Home page does not turn an API error into "0 runs / $0."
• Analytics labels unknown evaluation evidence as "Unknown," not "no Armor evaluation."
• "Verified" connection proof requires the same user, product, device, and session, plus a real pre-tool evaluation.

How telemetry flows

Telemetry flows guardrail to SDK to backend observability store; the Console reads from that store. Because the Console is read-only over recorded evidence, an empty or degraded state is an honest signal about ingestion, not a UI bug to hide.