Compare evidence, not feature adjectives

Vendor capabilities change by plan, provider, and contract. This checklist avoids unsupported scorecards and tells you what proof to request from Liulum or any alternative.

Area	Question to ask	Liulum answer	Evidence to request
Business path	Can the product connect the customer action to the downstream business outcome?	Yes, when the required journey, event, and outcome sources are configured and tested.	Ask to see the connection test and outcome-reconciliation record.
Failure evidence	Does an alert retain the exact source, time, correlation key, and affected step?	Liulum incidents are ledger-backed; missing inputs remain unavailable.	Inspect an incident record from your Guided Proof, not a fictional sample.
Recovery boundary	Which exact provider actions can run, under which policy, and who verifies the result?	Only eligible, pre-approved, bounded playbooks on connected customer-owned infrastructure.	Review the capability matrix, project policy, and independent verification receipt.
Tenant security	Can one customer or staff role read another customer's data or use a privileged runtime database role?	Customer routes are CLIENT-only; continuity tables are tenant-scoped; production requires a restricted runtime role.	Request RLS, role, and authenticated cross-tenant probe evidence.
Commercial truth	Are prices, limits, trials, provider usage, and approval boundaries explicit before payment?	The public ladder and Guided Proof limits come from one executable plan registry.	Compare the public pricing page, checkout terms, and entitlement response.
Exit and deletion	What can be exported or deleted, what must be retained, and how is deletion verified?	Deletion is tenant-scoped and fail-closed when an unknown reference table appears; statutory billing records may be retained.	Review the DPA, privacy policy, and a staging residual-count drill.

Make Liulum prove the answers.

Use one real path, then compare the evidence with your alternatives.

Request Guided Proof

Area

Question to ask

Liulum answer

Evidence to request

Business path

Can the product connect the customer action to the downstream business outcome?

Yes, when the required journey, event, and outcome sources are configured and tested.

Ask to see the connection test and outcome-reconciliation record.

Failure evidence

Does an alert retain the exact source, time, correlation key, and affected step?

Liulum incidents are ledger-backed; missing inputs remain unavailable.

Inspect an incident record from your Guided Proof, not a fictional sample.

Recovery boundary

Which exact provider actions can run, under which policy, and who verifies the result?

Only eligible, pre-approved, bounded playbooks on connected customer-owned infrastructure.

Review the capability matrix, project policy, and independent verification receipt.

Tenant security

Can one customer or staff role read another customer's data or use a privileged runtime database role?

Customer routes are CLIENT-only; continuity tables are tenant-scoped; production requires a restricted runtime role.

Request RLS, role, and authenticated cross-tenant probe evidence.

Commercial truth

Are prices, limits, trials, provider usage, and approval boundaries explicit before payment?

The public ladder and Guided Proof limits come from one executable plan registry.

Compare the public pricing page, checkout terms, and entitlement response.

Exit and deletion

What can be exported or deleted, what must be retained, and how is deletion verified?

Deletion is tenant-scoped and fail-closed when an unknown reference table appears; statutory billing records may be retained.

Review the DPA, privacy policy, and a staging residual-count drill.