REG-1 - Synthetic scope sheet
Payment platform from Northstar ICT and a non-critical collaboration service from Cedar Tools are both present; function mappings are recorded.
VAREXIS-INDEX - Synthetic examples
We have a supplier list. Which register fields and service-chain entries still need evidence?
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.
Choose a question below; each full record supplies exact MCP arguments, source clauses and limitations. This example as JSON
Payment platform from Northstar ICT and a non-critical collaboration service from Cedar Tools are both present; function mappings are recorded.
Northstar is the direct provider. A storage subcontractor effectively underpins the critical service. An intra-group provider uses a first extra-group subcontractor for the non-critical service; that entry is missing.
Northstar is a Union legal person; active LEI recorded, EUID availability not assessed. Storage is foreseen temporarily in France and Germany, entered in one comma-separated country cell.
Criticality assessment for another function not performed; RTO is undefined and encoded 0. Alternatives assessment is not performed. No dated validation evidence is attached.
The outcome labels describe only this manual example. They are not engine results, regulatory findings or permissions.
The synthetic inventory includes both named ICT contracts, without dropping the non-critical service. This supports only that narrow completeness check for the two supplied entries.
Source records: DORA: The information register is broader than critical-function suppliers
Permitted reliance: Use the documented all-ICT register scope; do not infer full register compliance.
Direct providers and effectively underpinning critical-function subcontractors must be considered, plus the stated intra-group/first extra-group exception. Add the missing exception entry before relying on this chain extract. Rank describes position, not supplier risk.
Source records: DORA: Direct-provider and subcontractor register scopes differ; DORA: Register rank identifies contractual distance
Permitted reliance: Prepare a scoped correction list; no supplier rating or approval.
Confirm EUID availability and legal-person/establishment facts; both identifiers apply where available, while non-Union legal persons use LEI only. Apply conditional location fields and separate valid country values into rows.
Source records: DORA: Provider names do not replace the required legal identifiers; DORA: Distinguish storage and processing locations in the register; DORA: Multiple valid register values need additional rows
Permitted reliance: Request documentary corrections, not regulator acceptance or live residency assurance.
An unperformed assessment and reporting code 0 for undefined recovery objectives do not establish low risk, zero downtime, or an absence of alternatives.
Source records: DORA: Keep missing assessments distinct from recovery targets; DORA: Distinguish alternatives from an unperformed assessment
Permitted reliance: Report the gap and reporting convention; no performance or resilience conclusion.
The same worksheet cannot establish that an unrelated UK-only enterprise is subject to DORA or certify its compliance.
Source records: DORA: The information register is broader than critical-function suppliers
Permitted reliance: Explain the applicability boundary and refer the determination to the responsible reviewer.
The register owner should reconcile contracts, chain scope, identifier and location fields, then review corrections and assessment evidence. Do not submit a register or approve a supplier 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.
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.