Skip to main content
WHAT IT IS

The working A prototype: use its controls to test the build question.

WHY IT MATTERS

Test whether exported data is complete, readable, reusable and actually movable elsewhere.

RN'S ROLE

RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.

BOUNDARY

This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.

HOW TO USE THIS PAGE

Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.

WHERE TO GO NEXT

The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.

BUILD 035-A

Data Exit & Portability Test

Test whether exported data is complete, readable, reusable and actually movable elsewhere.

JSON MODELED EXIT / portable-record-1 → target-record-2

STRUCTURAL LOSS

60% required/use-case presence · 11 findings

Parseable is not reusable, and this browser fixture moves no data. It does not verify a vendor import, attachment bytes, rights, source deletion, or real migration.

Source schema and package

Target mapping

recordId → external_idstring → string · null kept · order kept · reference kept · round trip verified
createdAt → created_atdatetime → string · null kept · order kept · reference kept · round trip missing
title → namestring → string · null lost · order kept · reference kept · round trip missing
tags → tags_importedstring-array → string-array · null kept · order lost · reference kept · round trip missing
attachment → filesattachment → attachment · null kept · order kept · reference kept · round trip missing

Findings

  • createdAt: type changes from datetime to string.
  • createdAt: lossy conversion declared — timezone/type semantics change.
  • createdAt: deterministic round-trip verification missing.
  • title: null semantics are not preserved.
  • title: deterministic round-trip verification missing.
  • status: use-case field missing.
  • tags: order is not preserved.
  • tags: deterministic round-trip verification missing.
  • decisionTrace: use-case field missing.
  • attachment: transfer rights are unknown.
  • attachment: deterministic round-trip verification missing.

Non-claims

  • Machine-readable means parseable, not understandable, reusable, compatible, semantically equivalent, or legally portable.
  • This fixture models a package; it does not move data, call a target system, verify attachments, delete source data, or prove a real migration.
  • A passing round trip covers only declared synthetic values and versions; production scale, vendor behavior, rights, and future versions remain external.