OpenChainGraph Suite · ART-520 · Government & Public-Money Payment Evidence

Operator Exit & Data Portability

You declare your data categories, which components you or your supplier control, your dependencies, escrow arrangements, and your notice / transition terms — this tool checks whether that declared exit posture hangs together. It reports a stranded-category list (categories with no declared export path), an operator-control ratio as declared, single-supplier dependencies with no declared substitute, and whether a contractual-operator claim is supported by the declared component control. It does not audit your supplier, rate a vendor, or opine on contract enforceability — it evaluates the declarations you supply. Undeclared is always kept distinct from a declared failure: silence is never scored as "not portable". Emits a hash-anchored OpenChainGraph v0.4 artifact. Region-portable: the same fields serve DORA exit plans, EBA outsourcing guidelines, FFIEC third-party risk, or any comparable regime — every fact below is an input you declare, never a hardcoded country or scheme.

Stranded-category list, not a coverage ratio Unsupported-operator-claim check Undeclared kept distinct from failure

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

⚠ This tool evaluates your DECLARED exit posture only — it does not audit, verify, or characterise any supplier, and no output names one. It does not opine on contract enforceability. It computes once when you press the button, stores nothing, runs on no schedule, and retains nothing.

Declaration

The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own. Load the stranded-category demo to see the flags this tool exists to catch.

As-of (ISO yyyy-mm-dd, your input, never a clock read)

Are you (the buyer) the contractual operator? (true / false / leave blank if undeclared)

Data categories (JSON array: category, export_exists, format, format_open, export_cadence, last_successful_export — omit any key you have not declared) Declared components (JSON array: name, controlled_by — "operator" or "supplier", omit if undeclared) Dependencies (JSON array: name, single_supplier, substitutable — each true/false, omit if undeclared)

Escrow arrangement exists? (true / false / leave blank if undeclared)

Escrow description (optional)

Notice period (days, leave blank if undeclared)

Transition-assistance terms (as declared, leave blank if undeclared)

Data categories

Dependencies

Exit-readiness exceptions

Rejected inputs

Rationale

Execution Hash (SHA-256)

What this does not do

It does not audit a supplier, rate a vendor, or opine on whether an exit clause is enforceable — those require legal review and evidence this tool never collects. It does not verify that the figures you supply are complete or accurate, and a clean result is not a determination that the underlying contract has been tested. Where you have not declared a fact — escrow, format openness, component control — this tool reports it as undeclared, never as a silent pass or a silent failure.

No node in the catalogue evaluates a declared exit posture directly. Related but non-overlapping: 100 assesses a broader declared operational-resilience posture, not exit-specific; 413 scopes EU Data Act applicability, not portability posture. The subject generalizes past government procurement to DORA exit plans, EBA outsourcing guidelines, and FFIEC third-party risk — the same declared fields serve any of them. Part of the government-payment-lifecycle chain alongside the programme's other reconciliation and audit-evidence nodes as they ship.