Skip to main content
Governance4 min read

26/09 edition: switch AI supplier with an exit dossier

A demonstration of the new answer does not prove that data, tools and permissions can survive the switch. Each dependency needs separate decision evidence.

Updated
Recovered day
2026-09-26
Actual publication
2026-10-05
Author
Redação Velqory
Verification
05/10/2026 · Europe/Lisbon
Scope
Retrospective analysis published on 5 October; it does not represent original publication on the recovered date. Plans and scenarios are original, untested editorial proposals, not internal experience.
Review
Review before selecting a destination, changing tools or moving new data; confirm applicable conditions at decision time.
Person compares a storage device and adapters between two open equipment cases.
Person compares a storage device and adapters between two open equipment cases. Generated conceptual scene; not documentation of an actual event, product or test.AI-generated image under Velqory editorial direction.

In brief

A switching dossier proposal for a proposal assistant, focused on usable exports, tool authority and negotiated exit conditions.

  • Test reference reconstruction, not merely file downloads.
  • Compare tool authority separately from answers.
  • Document exit conditions without assuming entitlements.

The new answer is only one part of switching

An SME wants to change the supplier of an assistant that reads dossiers and prepares proposals. The new service produces a good demonstration answer. The team still needs to know whether it can move permitted material, reconstruct references and retain the same action boundaries.

Our proposed decision does not compare models through a general ranking. It asks whether this specific service can move without losing control of its dependencies. The dossier should let someone uninvolved in the sale understand what migrates, what remains behind and who owns each gap.

The basis is governance, not an assumed entitlement

NIST GOVERN 6.1 addresses third-party risks. OWASP LLM06 recommends downstream authorisation. The AI RMF is voluntary. Our dossier proposal does not turn these references into an export obligation, contractual portability or an exit entitlement for every service.

Data: exporting is not reconstructing

We propose inventorying source documents, passages, references, configuration and records needed for continuity. For each item, request a written answer about available format, use conditions, retention and deletion. Where third-party rights or contractual uncertainties arise, the competent owner should resolve them before transferring material.

Run a trial with synthetic or previously authorised documents. At the destination, reconstruct an answer whose reference an authorised person can open. An export containing files but losing the passage-to-document link fails our criterion. We do not assume vectors or configuration can be reused without adaptation.

Tools: carry the boundary, not the credential

Our plan records each permitted operation, identity, destination and approval decision. Real credentials do not belong in the demonstration package. The team should create test access at the destination and show that an out-of-scope operation is refused regardless of the generated answer.

Hypothetical scenario: the current assistant only prepares a draft, but the destination integration also permits sending it. Equivalent answers do not make the configurations equivalent. Testing must distinguish preparation, human confirmation and sending; expanded authority should be decided separately or removed from the design.

The dossier that decides the switch

The original matrix requires artefacts, not sales promises. An unowned gap keeps the affected scope on hold. Procurement documents conditions; engineering demonstrates reconstruction; the service owner accepts the workflow. These trials are not product benchmarks or supplier certifications.

Evidence before switching supplier

Original, untested Velqory operating proposal. Failing a criterion blocks progression within the stated scope.

Action / scopeOwnerEvidencePass / fail
Data and referencesData owner and engineeringPermitted export and reconstructed answerPass with usable reference; fail if linkage lost
Tool authorityIntegration ownerAllowed and refused destination operationsPass without implicit expansion; fail if draft becomes sending
Exit conditionsProcurement and service ownerWritten answers and continuity planPass with known conditions; fail if rights assumed

Exit and return need a concrete condition

Before switching, we propose stating how to suspend new tasks, recover the queue and reconcile work begun during transition. Define which evidence triggers return to the previous workflow and who decides. Keeping an old subscription is not proof that the return path remains functional.

For the Portuguese SME, the final dossier should include contractual answers approved by competent owners, an inventory with limits and the trial report. The conclusion may be to move only consultation while keeping tools on the existing path. This avoids calling a partial transfer a global success. We assert no legal obligations, internal experience or comparative advantages; this is an untested decision plan.

Consulted on the stated update date.

  1. 01AI RMF Playbook — GovernNIST AIRC · GL-NISTAI
  2. 02LLM06:2025 Excessive AgencyOWASP Gen AI Security Project · GL-OWASPGENAI
  3. 03AI Risk Management FrameworkNIST · GL-NISTAI