What Survives a Knowledge-Base Export? An 80-Record Round Trip

Direct answer

The executed transformation found that JSON preserved every frozen record exactly, flat CSV discarded list and nested provenance types, and Markdown kept visible values while losing machine-readable type information. Test the return journey, not the export button: compare values, types, provenance, identifiers, and Unicode after re-import. The conclusion belongs to one independent note record; visible readability alone cannot establish structural or intellectual fidelity.

A file can open after its knowledge has vanished

A JSON, flat CSV, and Markdown exports representation can look intact while its consequential relations have already vanished. The predetermined research question is: Which scalar, list, nested provenance, type, and Unicode fields survive JSON, flat CSV, and Markdown export transformations? The object under examination is one independent note record, not the quality of a person's thinking or the performance of an institution.

A file that opens successfully can still lose nested provenance, list structure, or data types during export. In this comparison, knowledge portability treats visible preservation and structural preservation as different achievements. A JSON, flat CSV, and Markdown exports file, map, or graph may remain readable while the relations needed for reuse are no longer recoverable.

Frozen knowledge portability material comprises notes: 80; formats: reported in the raw record. These JSON, flat CSV, and Markdown exports records are small enough to inspect but varied enough to reveal losses that a successful opening or clean diagram would conceal.

Recover the relations beneath the knowledge portability aggregate

The complete sanitized raw data is the canonical record for this run. These first twenty-eight knowledge portability rows expose the relations behind the aggregate. The complete JSON, flat CSV, and Markdown exports download retains the rest, including records that survive without incident.

• Row 1 — note Id: N01; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 2 — note Id: N02; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 3 — note Id: N03; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 4 — note Id: N04; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 5 — note Id: N05; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 6 — note Id: N06; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 7 — note Id: N07; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 8 — note Id: N08; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 9 — note Id: N09; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 10 — note Id: N10; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 11 — note Id: N11; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 12 — note Id: N12; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 13 — note Id: N13; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 14 — note Id: N14; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 15 — note Id: N15; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 16 — note Id: N16; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 17 — note Id: N17; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 18 — note Id: N18; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 19 — note Id: N19; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 20 — note Id: N20; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 21 — note Id: N21; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 22 — note Id: N22; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 23 — note Id: N23; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 24 — note Id: N24; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 25 — note Id: N25; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 26 — note Id: N26; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 27 — note Id: N27; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.
• Row 28 — note Id: N28; json Exact: true; csv Scalar Fields Retained: 5; csv List Type Retained: false; csv Nested Provenance Retained: false; markdown Visible Values Retained: true; markdown Type Information Retained: false.

Evidence snapshotHigh confidence

The executed knowledge portability record shows that JSON preserved every frozen record exactly, flat CSV discarded list and nested provenance types, and Markdown kept visible values while losing machine-readable type information. Row-level JSON, flat CSV, and Markdown exports fields support that bounded finding, while no field represents human learning, reader comprehension, or real-world deployment.

^lab-record

Claim sources: ^lab-record

Evidence snapshotModerate confidence

The reviewed method source supplies a relevant standard for context, traceability, or explicit evaluation of JSON, flat CSV, and Markdown exports. It disciplines interpretation of JSON, flat CSV, and Markdown exports; it does not generate or independently confirm this local aggregate.

^{method-source}

Claim sources: ^{method-source}

Eighty notes make portability measurable

To distinguish visible survival from relational survival, the run follows 3 fixed steps:

1. Freeze eighty independent notes containing scalar, list, nested, date, confidence, and Unicode fields.
2. Round-trip the records through JSON, a deliberately flat CSV mapping, and human-readable Markdown.
3. Compare field values and types against the immutable input rather than checking file existence.

Across the knowledge portability diagram and JSON, the same unit, sample, and result fields remain visible. If those JSON, flat CSV, and Markdown exports representations disagree, the visual is wrong; visual polish cannot override the canonical executed record.

Results: what survived the knowledge portability transformation

| Recorded result | Value | |---|---| | json Exact Records | 80 | | csv Records Retaining Nested Provenance | 0 | | markdown Records Retaining Types | 0 | | unicode Failures | 0 |

After transformation, knowledge portability produced a visible pattern: JSON preserved every frozen record exactly, flat CSV discarded list and nested provenance types, and Markdown kept visible values while losing machine-readable type information. This establishes what happened to one independent note record under the implemented JSON, flat CSV, and Markdown exports mapping, while leaving intellectual quality undecided.

The prespecified negative finding for knowledge portability is equally important: Readable Markdown retained visible values but did not preserve machine-readable list, date, or nested-object types. It marks the point at which this JSON, flat CSV, and Markdown exports method becomes silent, a condition a reader needs before deciding whether to use the rule.

Readable is not the same as recoverable

This is not evidence that CSV or Markdown are poor formats. The losses came from declared naive mappings; a richer schema, front matter, sidecar files, or normalized relational tables could preserve the missing structure.

This knowledge portability challenge shifts attention from format loyalty to recoverability. A simpler JSON, flat CSV, and Markdown exports representation is sufficient when the lost relation can be reconstructed reliably; otherwise, readability is a poor substitute for fidelity.

That reversal condition keeps knowledge portability from becoming either technological maximalism or ritual caution. The JSON, flat CSV, and Markdown exports procedure earns its place only when it makes a consequential uncertainty, tradeoff, or failure more visible.

Design the return journey before migration

Test the return journey, not the export button: compare values, types, provenance, identifiers, and Unicode after re-import. Reproduce knowledge portability through export and return, or through claim and relation reconstruction. When JSON, flat CSV, and Markdown exports identifiers, types, or edges change, report the loss instead of silently repairing it.

The working sequence for knowledge portability is specific to this study: lock the question and baseline, freeze the unit, execute the declared transformation, retain negative findings, and separate the local result from any transfer claim.

Human readability and machine fidelity diverge

A successful knowledge portability export, map, or graph can still be intellectually unfaithful. This JSON, flat CSV, and Markdown exports test fails when visible neatness overwrites lost types, contested relations, or judgments about necessity.

Reproducibility in JSON, flat CSV, and Markdown exports also fails when a download cannot regenerate the claim in the prose. This knowledge portability record keeps protocol, sample, aggregates, limitations, negative findings, and row-level output in one parseable object so that disagreement can reach the actual computation.

Where this knowledge portability result stops

Limits and counterevidence

The result applies to the declared transformations; richer CSV schemas or Markdown front matter could preserve more structure. The designed knowledge portability records reveal declared losses, not the quality of a person's knowledge or an institution's practice. A different JSON, flat CSV, and Markdown exports schema could preserve more, but it would constitute another transformation.

This knowledge portability limit specifies the next experiment. Transfer of this JSON, flat CSV, and Markdown exports result requires records from the target context, the same visible denominator, and a fresh execution—not stronger adjectives attached to the present run.

Related reading:

• Continue with the prerequisite analysis of knowledge portability.
• Continue with a comparison that tests a neighboring boundary.
• Continue with the next practical application.

The knowledge portability experiment leaves one durable test: can the consequential relation be reconstructed after the format changes?

Named sources

Evidence and further reading

1. What Survives a Knowledge-Base Export? An 80-Record Round Trip — Sanitized Raw Recordpractitioner · accessed 2026-07-28
2. Framework for Information Literacy for Higher Educationofficial · accessed 2026-07-28

Publication record

Published July 29, 2026. No substantive revision has been recorded. Evidence last verified July 28, 2026.