Running an assurance suite
- A run failed to start. Usually credentials or
INFORMATION_SCHEMApermissions. The CLI reports the failing check by name — see CLI reference. - Everything came back
INDETERMINATE. Almost always a missing or unratified business definition. The Business Definition Owner has a contractual 48-hour window to resolve each one; unresolved items stay indeterminate in the bundle with the date they were raised. - Coverage is lower than expected. Excluded items count in the denominator. How exclusions are counted.
- I think a finding is wrong. That is the recall protocol — email with subject
[RUN]and it triggers an automated hold within four hours.
Bundles and verification
- Verifying a bundle — paste the hash into the verifier. “No record” means the hash is not one we issued; it does not mean the bundle is invalid.
- Exporting everything — case-level records in a documented non-proprietary schema. Export schema and exit guide.
- A bundle looks out of date — it is evidence about a frozen configuration on a date. Changing the prompt, semantic model, tool definitions or model version invalidates it. Why.
The qabit adapter
- Installing the widget — copy the snippet from the console’s install tab. One script tag, no build step.
- Nothing is arriving — check the hash key is active and the origin is allowed. Submissions from an unlisted origin are rejected by design.
- Slack or Asana not firing — both are configured per hash key, and Asana only creates a task for the bug-report form type.
Account and billing
Plan changes, invoices and tax documentation are handled in the console. For anything the console will not do, email with subject [BILLING] — response within two business days. target
Still stuck
There is no ticket queue to disappear into. Four routes, four owners, four stated response times. A live run gets four business hours; a security issue goes to [email protected] and is acknowledged within one business day.