LensReading which lens this session carries.

Portability and exit

What leaves with you, in what format, and how long it takes

14 asset classes covering roughly 41,876,166 records, and a 10-step exit path across 7 phases that runs 144 days end to end.

14 of 14 open format

Health

Format, automation, proof, elapsed time

An export that only exists as an intention scores nothing here, however well documented it is.

How it runs

Everything the platform holds

Grouped by data class.

Operating model

3 assets · 1,855 records · 0 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Agent registernever restored

One row per agent with its function, sub-function, autonomy level, confidence, trust score and the authority it holds.

Produced by hand from a database query. There is no button.

CSV · JSON1,361by handOn requestHead of Agent Platform38 days ago
Workflow definitionsnever restored

Stages, stations, routing rules and the human checkpoints on each of the 475 workflows, as a nested document per workflow.

The export describes the workflow.

JSON475by handOn requestHead of Agent Platform38 days ago
Model and vendor registrynever restored

The registry exactly as it appears on this site, including deprecation dates and substitution notes.

JSON · CSV19by handOn requestHead of Agent Platformtoday

Transaction record

1 asset · 41,600,000 records · 0 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Work unit historynever restored

Every work unit that has passed through a station, with its timestamps, its outcome and the agent or person who handled it.

Roughly 41.6 million rows. The nightly extract runs and is monitored

Parquet · CSV41,600,000by handNightly to our own object storageHead of Data and Analytics1 day ago

Audit record

2 assets · 272,080 records · 1 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Evidence recordsrestore proven

The evidence pack route is live and produces a self-contained JSON document plus a rendered PDF for any referenced decision.

Per reference, not in bulk. There is no route that returns all 8,080.

JSON · PDF8,080/api/evidence/pack/[ref]On demand, per packHead of Internal Audit2 days ago
Decision ledgernever restored

Append-only. Every decision, its inputs, the authority under which it was taken, the approver and the outcome. One JSON object per line. Like the work unit history, the row count is a modeled estate figure for a rolling year rather than a live table count.

Retention is set to seven years in the product.

JSONL264,000by handNightly to our own object storageHead of Internal Audit1 day ago

Governance

3 assets · 983 records · 0 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Policy corpusnever restored

All 465 policy items with their text, owner, effective date, review cycle and the workflows they bind.

The bindings between a policy and a workflow are the valuable part and they are expressed as our own identifiers.

Markdown · JSON465by handOn requestChief Compliance Officer2 months ago
Strategy positionsnever restored

The 209 ratified positions with their sponsor, the policy they generated and the date they were ratified.

Same identifier problem as the policy corpus.

JSON · CSV209by handOn requestChief Strategy Officer2 months ago
Authority grantsnever restored

Who — person or agent — may decide what, to what value, with which second signature.

None on the data.

JSON309by handOn requestChief Compliance Officer38 days ago

Commercial

3 assets · 1,048 records · 0 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Service levels and breachesnever restored

28 service levels and the 29 breaches recorded against them, with credits owed and paid.

Only four towers have signed service levels, so this export describes a third of the estate.

CSV57by handOn requestHead of Global Business Services18 days ago
Benefit ledger and baselinenever restored

The frozen baseline, every claimed benefit against it, and the finance sign-off state of each claim.

The baseline is a modeled reconstruction, which is stated on the ledger page and travels with the export.

CSV · JSON655by handMonthlyGroup Financial Controller14 days ago
Scorecardsnever restored

Function and tower scorecards by period

CSV336by handMonthlyHead of Global Business Services14 days ago

Workforce

1 asset · 154 records · 0 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Role transition ledgernever restored

The 154 role transitions with released, redeployed and unplaced headcount, consultation state and training hours.

Contains workforce data subject to local consultation rules.

CSV154by handOn request, restrictedChief Human Resources Officer9 days ago

Assurance

1 asset · 46 records · 1 with a route

AssetFormatsRecordsRouteCadenceOwnerLast verified
Trust attestations and questionnairerestore proven

The attestation register and the completed vendor questionnaire, rendered through the brief route that already serves the rest of the site.

The underlying certificates and test reports are held by the issuers and are released under non-disclosure.

JSON · PDF46/api/briefOn demandChief Information Security Officertoday

What to pick up

What stands between this and a clean exit

A buyer's counsel will read this list before they read anything else on the page.

Assets with no export route at all

12

Agent register · Workflow definitions · Work unit history · Policy corpus · Strategy positions · Authority grants · Decision ledger · Service levels and breaches · Benefit ledger and baseline · Scorecards · Role transition ledger · Model and vendor registry

Exports never restored into anything

12

Only Evidence records and Trust attestations and questionnaire have been read back after export.

Exit steps that have never been executed

4

Freeze · Freeze the operating model · Extract · Reconcile the extract against the live estate · Cutover · Parallel run · Verify · Restore verification

Assets carrying a stated gap

12

Agent register · Workflow definitions · Work unit history · Evidence records · Policy corpus · Strategy positions · Authority grants · Decision ledger · Service levels and breaches · Benefit ledger and baseline · Role transition ledger · Trust attestations and questionnaire

Detail on the record

The exit path, phase by phase

144 days from notice to termination if every step runs to its written duration.

Run-book

10 steps · 4 documented · 2 partly rehearsed · 4 untested

01Notice
Written notice and exit triggerDocumented0 days

Either party gives written notice.

Owner Chief Procurement Officer · can start on day one

Contractual. Ninety days on the master agreement.

02Notice
Name the receiving destinationDocumented10 days

The exiting party states where the work goes — a successor platform, a return to the prior systems, or a hold state where the workflows keep running under human execution.

Owner Chief Operating Officer · follows EXT-01

This is the step most exit plans skip and the one that decides how much of the rest is possible.

03Freeze
Freeze the operating modelUntested3 days

No new agents promoted, no new workflows published, no authority changes.

Owner Head of Agent Platform · follows EXT-02

The freeze is a configuration state that exists in the product. It has never been exercised across the whole estate.

04Extract
Produce the full data extractPartly proven14 days

All fourteen asset classes on this page, in the open formats listed, written to storage the exiting party controls.

Owner Head of Data and Analytics · follows EXT-03

Two assets have an export route. The other twelve are produced by hand. The fourteen-day figure assumes the hand-produced ones go right first time.

05Extract
Reconcile the extract against the live estateUntested7 days

Row counts, control totals and a sampled record-level comparison, signed by finance for the commercial assets and by audit for the evidence and decision records.

Owner Group Financial Controller · follows EXT-04

No reconciliation procedure has been written. This step is a placeholder with an owner, which is more than most exit plans have and less than a buyer should accept.

06Handover
Run-book handoverPartly proven21 days

The operating run-book: what each of the 475 workflows does, which stations require a person, the escalation ceilings, the kill switches and what each one stops …

Owner Head of Global Business Services · follows EXT-03

The run-book is generated from the same tables the product reads, so it cannot go stale. It has never been handed to anyone outside the team that wrote it.

07Handover
Model and vendor position transferDocumented14 days

Which model each workflow calls, the contractual position with each provider, and whether the receiving party can inherit the agreements or must contract fresh.

Owner Chief Procurement Officer · follows EXT-02

Only the Helix weights move cleanly. Abraxas and Corvid agreements are non-assignable and the receiving party contracts from zero.

08Cutover
Parallel runUntested30 days

The receiving destination processes the same inbound work alongside the estate for a defined period, with outcomes compared station by station before anything is switched off.

Owner Chief Operating Officer · follows EXT-06

Thirty days is an assumption, not a measurement. No parallel run has ever been performed.

09Verify
Restore verificationUntested10 days

The receiving party loads the extract and demonstrates that the operating model, the authority grants and the evidence trail are all readable and complete in the destination.

Owner Head of Internal Audit · follows EXT-08

Two of fourteen assets have ever been read back outside the product. This is the weakest link in the whole plan and it is the one the plan depends on.

10Terminate
Deletion and certificateDocumented35 days

Production data deleted, backups aged out on their existing cycle rather than deleted early, sub-processor instructions issued, and a signed deletion certificate produced listing every store and its completion date.

Owner Chief Information Security Officer · follows EXT-09

Backups age out over 35 days. Deletion is not instant and the certificate says so rather than pretending otherwise.

Against the written intent

Does the no-lock-in position survive contact with the record

Three commitments a buyer will hold the organization to, each answered from the table above rather than from intent.

Commitment

Everything the platform holds can be exported in a format that does not need this product to read it.

Holding — all 14 asset classes are in open formats.

Commitment

Export runs without asking the vendor to do anything.

Not holding — 14% of asset classes have a route. The rest need somebody inside the platform team to produce them.

Commitment

The exit path has been rehearsed, not just written.

Not holding — no step has been executed end to end. 2 of 10 have had part of them rehearsed, 4 are written in full but never run, and 4 have never been rehearsed at all.

What this page is, and what it is not

A security certification and a penetration test are organizational attestations.

A portability claim has the same shape. The formats, the routes and the durations below are real properties of the product; the exit run-book is not. It has been written by the team that built the platform and no step in it has ever been executed end to end against a live tenant, so the 144 days figure is a plan, not a measured elapsed time.

Actions

What is waiting on a person

Leaving is a capability, not a clause.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

14 portable assets covering roughly 41,876,166 rows across 7 data classes, and a 10 step exit runbook grouped into 7 phases with a stated total of 144 days. 14 assets come out in an open format and 2 have a working export route.

Live observability

What the record shows right now

How far each exit step has actually been taken.

Current distribution

10 steps

Documented440%
Partial220%
Untested440%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Not holding. The runbook is complete on paper and unrehearsed in practice.

Not holding on the record

The intent is that the platform can be left without a rescue project.