Guide

Follow-up workflow verification

Review the disposable workflow results, test screenshots, and provider acceptance status.

Demo baseline · November 13, 2026

These checks used the platform image for Cloud Run revision qintorava-cloud-00781-pez with disposable PostgreSQL databases. The browser scenarios exercised actual Qintorava screens and checked the saved states. The provider tests used controlled responses and signed synthetic callbacks.

Platform source 01e411fddde62e47724862964902b82e9ad47421. Cloud Build 47ff4c2d-80fa-4ccc-9a76-47f8e4be53bd. Receipt recorded at 2026-11-14T02:35:03.951Z (UTC).

Browser workflow results

8 of 8 browser scenarios passed.

Scenario	Result and verified behavior
Cloud plan automation requires independent approval of the current validation evidence	Passed. An independent reviewer approved the current validation. The earlier package was stale. The approved plan did not grant execution.
contract automation requires an independent contract manager and current supplier risk	Passed. The administrative role alone was denied. A contract manager approved after the supplier risk assessment was current.
FinOps budget automation requires independent approval of the exact budget version	Passed. The budget owner could not self-approve. The reviewer got a conflict on the old version and approved the revised amount.
CMDB assurance workflow records field decisions and remediates a failed certification	Passed. The assigned reviewer recorded a failed field, remediated it, and certified the corrected record. An unassigned reviewer was denied.
CMDB normalization automation honors reviewer assignment and rejects a stale CI snapshot	Passed. The assigned reviewer used the current CI. A run against an older CI snapshot failed.
event workflow protects firing alerts and audits independent recovery closure	Passed. The firing alert could not close. The cleared alert required an independent reviewer and recorded an audit entry.
playbooks and major cases execute within the shared desktop and mobile CSM workspace	Passed. The desktop run exercised case playbooks and the major-case lifecycle in the shared CSM workspace.
closed-case low score becomes a governed recovery with reviewed closure and preserved portal feedback	Passed. The browser passed through claim, start, review, return, resubmission and approval. The original satisfaction score remained intact.

CMDB field decision selector for the synthetic manufacturer field. — Configuration Studio showed field-level review. The test verified that the assigned reviewer could reject the original value, complete remediation and certify the corrected value.

Event alert review panel with state and recovery evidence. — The firing alert could not close. After recovery, the independent reviewer closed the alert and the saved audit recorded the reviewer.

Customer satisfaction recovery dialog showing the completed and approved decision. — The recorded recovery outcome left the original score of one out of five intact. The test verified the closed case and the recorded return for more work.

Disposable database and connector tests

97 test cases passed across the suites below. The test runner counts nested cases and their parent suites.

Suite	Run outcome
Customer service playbooks and major cases	18 passed, 0 failed, 0 skipped. Runner exit 0.
Customer recovery and reviewer access	15 passed, 0 failed, 0 skipped. Runner exit 0.
Datacenter capacity and reservations	8 passed, 0 failed, 0 skipped. Runner exit 0.
Datacenter work orders and role scope	21 passed, 0 failed, 0 skipped. Runner exit 0.
Field-service worker authorization	1 passed, 0 failed, 0 skipped. Runner exit 0.
Major incident Twilio callbacks	4 passed, 0 failed, 0 skipped. Runner exit 0.
Major incident Twilio request construction	4 passed, 0 failed, 0 skipped. Runner exit 0.
Federation token, assignment and session policy	18 passed, 0 failed, 0 skipped. Runner exit 0.
Supplier lifecycle and simulated ERP reconciliation	8 passed, 0 failed, 0 skipped. Runner exit 0.

Ticket WhatsApp round trip with a simulated provider

Cloud Build b20f3902-6075-4495-9f1d-03d61bae1a4b. The runner recorded 5 of 5 cases passed.

The test rejected a forged signature, attached one inbound comment after a duplicate webhook, dispatched one outbound request after a duplicate queue operation, kept the delivered state after a stale callback, and blocked a new message after receiving STOP.

External sandbox acceptance

The demo switched to revision qintorava-cloud-00783-riw during the audit. The release comparison found identical ERP connector, ticket WhatsApp transport, callback, migration and gateway contract files. The live ERP reconciliation endpoint returned HTTP 401 for an anonymous request after the switch.

Integration	Status	Evidence still required
ERP	Pending approved sandbox	The signed-in demo listed zero ERP integrations. An approved connector and synthetic purchase order are needed to record the provider order count, read-only lookup result, and reconciled Qintorava state.
Twilio / WhatsApp	Pending approved sandbox	An approved sandbox with a joined test recipient. Capture Qintorava delivery state, the Twilio message receipt, and the matching WhatsApp conversation and reply.

See the ERP reconciliation runbook and the WhatsApp delivery runbook for how to run and record the provider checks.