VAREXIS

VAREXIS-INDEX - Synthetic examples

Contractual audit, continuity and exit

We have a certificate and an exit clause. What supports audit rights, service continuity and a tested exit plan?

1. Establish the scope

The original /mcp find_evidence_questions searches the frozen 1,003-record population. DORA records are catalogue-only additions. Select a title/question here and retrieve its full free JSON or use get_publication_record on /mcp/catalogue with the returned record_id. No schema or search expansion.

2. Select and retrieve source evidence

Choose a question below; each full record supplies exact MCP arguments, source clauses and limitations. This example as JSON

3. Inspect the synthetic material

EXIT-1 - Synthetic contract package

A downloadable, versioned full contract includes its SLA and parties. A supplier certificate is attached, but the contract says all audit rights are replaced by the certificate.

EXIT-2 - Synthetic alternative assurance request

A separate fictional microenterprise asks whether agreed delegation to an independent third party appointed by the provider can apply. Information and assurance availability and the delegation agreement are not supplied.

EXIT-3 - Synthetic continuity/exit file

A draft exit plan describes migration and a 30-day transition. Continued service obligations and a complexity assessment are missing. There is no test result or periodic review record. Thirty days is a fictional proposal, not a DORA minimum.

EXIT-4 - Synthetic data-return clause

The contract provides accessible recovery/return for personal and non-personal data on insolvency, resolution, discontinuation and termination. No actual recovery or deletion evidence is provided.

4. Compare within the evidence boundary

The outcome labels describe only this manual example. They are not engine results, regulatory findings or permissions.

supported - EXIT-1

The fictional package includes a durable full contract and SLA with version and parties. This supports that documentary packaging observation only.

Source records: DORA: The full ICT contract must include the service levels

Missing evidence

  • Authenticate executed current documents and actual scope in a real review.

Permitted reliance: Identify complete contract evidence; no overall legal or supplier approval.

refused - EXIT-1

A supplier certificate does not automatically replace critical-function access, inspection and audit rights. Audit planning and auditor competence remain separate questions; high technical complexity triggers the stated competence assessment.

Source records: DORA: Critical-function audit rights have a specific microenterprise alternative; DORA: Predetermine risk-based audit scope and frequency; DORA: Technical complexity requires competent auditors

Missing evidence

  • Executed rights and applicable affected-client alternative
  • Risk-based audit programme
  • Complexity and auditor skills assessment

Permitted reliance: Identify clause gaps; do not claim audit rights were exercised or the service passed an audit.

conditional - EXIT-2

The express microenterprise alternative may apply with agreed independent delegation and information/assurance available at any time. Microenterprise status alone is not sufficient.

Source records: DORA: Critical-function audit rights have a specific microenterprise alternative

Missing evidence

  • Verified microenterprise/entity status
  • Agreed delegation and independence
  • Information and assurance availability

Permitted reliance: Request the conditions supporting the alternative, without asserting entitlement to private data.

unbound - EXIT-3

The draft demonstrates a proposed plan, not a sufficiently tested and periodically reviewed exit or an adequate continuity transition. Neither a universal transition length nor fixed testing interval follows from these records.

Source records: DORA: An exit document needs a tested and reviewed plan; DORA: Exit clauses need an adequate transition period; DORA: Contract for implemented and tested contingency plans

Missing evidence

  • Adequate continued-service transition clause
  • Complexity and migration/in-house assessment
  • Proportionate test scope/results and review record
  • Service-specific provider contingency evidence

Permitted reliance: Prepare an evidence request; no migration success, resilience or production readiness conclusion.

conditional - EXIT-4

The listed events and data types support a bounded clause comparison. Actual recoverability, applicable insolvency law and third-country enforcement need separate evidence; a return clause does not prove deletion.

Source records: DORA: Contract for protected data access, recovery and return; DORA: Consider insolvency, data recovery and foreign enforcement

Missing evidence

  • Formats, inventories and service scope
  • Applicable insolvency/urgent-recovery assessment
  • Third-country data-protection/enforcement analysis if applicable
  • Actual outcomes where claimed

Permitted reliance: State the documented clause and unresolved execution evidence; no verified return or deletion.

5. Hand over the gaps

The contract and continuity owners should resolve rights, qualified exceptions, transition adequacy and dated test evidence before any real reliance decision. Do not run a test, disclose supplier data or initiate exit through this example.

Review dates remain those of the reused records. Recheck current official texts, corrections, applicability and current service/contract evidence before actual reliance.

6. Keep free evidence separate from paid services

All DORA records, sources, hashes, navigation and these manual examples are free. Save the public JSON locally if useful.

Not established. These catalogue-only additions are outside original paid saved retrieval and Evidence Receipt. No DORA-specific product or executable profile exists.

Compare existing offers and their limits