Free tool · works now

Offline note portability checklist

Audit software dependence, proprietary syntax, and air-gapped filesystem durability across note vaults.

Note Portability & Independence Audit

Evaluate physical filesystem custody, link format portability, media asset storage, and offline durability.

Zero Cloud TelemetrySelf-Reported EvidenceCommonMark & GFM Aligned
Transparent Audit Notice: Findings are self-reported observational diagnostics based on your architecture selections and local pattern checks. This tool does not issue a certified compliance score. True data durability requires verifying raw files directly on your local drive.
Which software currently holds custody of your primary notes?
Name of your notebook, folder, or personal knowledge base.

Portability Dimensions Assessment

Where do your note source files physically live on your computer disk?

What file format is used when inspecting a note with a plain text editor like TextEdit or nano?

How are internal links between related notes formatted in the text?

Where are inserted images, audio recordings, and PDF documents stored?

Does your workflow depend on proprietary block schemas, dynamic query engines, or custom plugins?

If your computer is in Airplane Mode for 30 consecutive days, can you open, edit, search, and export all notes?

Paste a representative markdown note to automatically check for dataview scripts, block IDs, cloud URLs, or proprietary protocols.
Independent (Open)4
Manageable Coupling2
Severe Lock-In0
Unverified Aspects0
Remediation Checklist & Audit Report
# Note Portability Audit: Knowledge Vault

> **Date:** 2026-11-19  
> **Target Application:** obsidian  
> **Notice:** DISCLAIMER: This report is an observational diagnostic checklist based on self-reported inputs and local pattern scanning. It does NOT constitute a certified score, legal audit, or guaranteed migration warranty. Portability requires continuous verification against raw filesystem files.

## Diagnostic Summary by Dimension

| Dimension | Risk Classification | Observation / Self-Reported Evidence | Status |
| :--- | :--- | :--- | :--- |
| **Storage & Filesystem Location** | Independent (Open Standard) | Plain folder on my local drive (accessible via Finder/Explorer without running the app) | self-reported-verified |
| **Underlying Note File Format** | Independent (Open Standard) | Standard UTF-8 Markdown (.md or .txt files) | self-reported-verified |
| **Cross-Note Hyperlinking Syntax** | Manageable Coupling | Short wikilinks [[Target Note]] or [[Target Note|Alias]] | self-reported-warning |
| **Images, PDFs, & Attachment Assets** | Independent (Open Standard) | Local folder within vault or relative directory alongside note files | self-reported-verified |
| **App-Specific Syntax & Query Plugins** | Manageable Coupling | Fenced code blocks for queries (e.g., dataview, mermaid) inside standard markdown fences | self-reported-warning |
| **Air-Gapped & Offline Operability** | Independent (Open Standard) | Fully functional without any network connectivity (zero feature loss) | self-reported-verified |

## Step-by-Step Remediation Checklist

### Cross-Note Hyperlinking Syntax
- [ ] **Action:** Minor vendor coupling: Use automated batch utilities to translate app-specific structures into plain CommonMark.
- *Observed condition:* Short wikilinks [[Target Note]] or [[Target Note|Alias]]

### App-Specific Syntax & Query Plugins
- [ ] **Action:** Minor vendor coupling: Use automated batch utilities to translate app-specific structures into plain CommonMark.
- *Observed condition:* Fenced code blocks for queries (e.g., dataview, mermaid) inside standard markdown fences

The Physics of Note Portability: Building Knowledge Vaults That Outlive Applications

Digital notes represent years of intellectual compounding. You document architectural decisions, research findings, meeting insights, personal reflections, and long-term project plans. Yet the vast majority of note applications are designed around short-term convenience rather than decades-long preservation.

When an application stores your writing in an opaque cloud database, converts images into authenticated remote URLs, or wraps paragraphs in proprietary syntax, you do not truly own your notes. You are merely renting an interface. If the company changes its pricing structure, pivots its product strategy, suffers a service outage, or is acquired by a competitor, your life's work becomes held hostage to migration friction.

The Offline Note Portability Checklist provides an objective, transparent framework for diagnosing software dependence. By evaluating six fundamental dimensions of data custody, this tool helps you identify subtle vendor coupling before it becomes insurmountable.

1. The Six Dimensions of Note Autonomy

A truly sovereign note collection satisfies six independent criteria. Evaluating your setup across these pillars reveals exactly where migration friction hides:

  1. Physical Filesystem Custody: Your notes must exist as individual files in an ordinary directory on your hard drive. You must be able to open Finder or File Explorer, right-click any note, and view it with standard text editors without the parent application running. Hidden SQLite databases or cloud-only web applications fail this test immediately.
  2. Universal File Encoding: Text must be stored in standard UTF-8 plain Markdown (.md) or plain text (.txt). Binary containers, proprietary JSON trees, and HTML wrappers require complex extraction scripts that frequently discard metadata and formatting.
  3. Standardized Cross-Note Hyperlinking: Cross-references between notes should use either RFC-standard relative file paths ([Target](./subfolder/Target.md)) or clean wikilinks ([[Target Note]]). Proprietary deep-link URIs (such as app://open?id=123) break completely the moment you change software.
  4. Local Media Asset Custody: Embedded images, voice recordings, and PDFs must reside in a local /assets directory alongside your notes. Applications that store images as expiring Amazon S3 URLs or authenticated CDN links leave your notes permanently broken once an account is closed.
  5. Syntax Hygiene & Plugin Containment: Advanced workflows often utilize query plugins (such as Dataview) or diagram tools (like Mermaid). These extensions are acceptable only when contained inside standard Markdown code fences (```dataview). Non-standard block IDs (^block-id) injected into prose corrupt document portability.
  6. Air-Gapped Offline Durability: The software must be 100% operational with your network hardware disabled. If disconnecting your Wi-Fi prevents you from reading, editing, searching, or exporting your files, your notes are not truly local-first.

2. The Non-Certification Principle: Why Vanity Scores Deceive

Many technology evaluations attempt to flatten nuanced technical realities into a single numerical score (e.g., "94% Portability Score!"). In data engineering and knowledge management, such scores are dangerously misleading. A vault could achieve a "90%" score across formatting and links, yet if all embedded images are hosted on expiring cloud buckets, an exported archive loses all visual data the day the subscription lapses.

Our engine operates on strict epistemic neutrality. We refuse to issue certified scores or rubber-stamp guarantees. Instead, we generate transparent observational checklists that categorize every finding into specific risk tiers (Independent, Manageable Coupling, Severe Lock-In, or Unverified). This diagnostic honesty empowers you to take targeted technical action.

3. Mitigating Manageable Coupling: Pragmatic Migration Steps

Achieving total portability does not mean you must abandon helpful features. It simply requires containing those features within portable boundaries:

4. Comparative Portability Matrix: Popular Note Systems

Application EcosystemPrimary Storage ModelLink FormatMedia CustodyAir-Gap Resilience
Plain-Text MarkdownDirect local filesystem folderRelative paths or clean wikilinksLocal assets directory100% indefinite offline operation
ObsidianLocal Markdown files on diskWikilinks or relative pathsLocal attachment foldersFull offline functionality
NotionProprietary cloud database blocksInternal cloud block URLsExpiring remote cloud CDN linksNon-functional when air-gapped
Apple NotesLocal SQLite / Cloud containerInternal proprietary URIsLocal database blob storageOffline reading with local cache
EvernoteCloud service databaseProprietary note linksRemote cloud storageDegraded without cloud access

Complement your vault hygiene with our related data sovereignty tools: inspect your vault health with the Note Maintenance Checklist Builder, verify round-trip export fidelity with the Export Round-Trip Comparator, translate vendor callouts with the Callout Portability Converter, and normalize link notation with the Wikilink-to-Markdown Converter.

Questions

Why does this tool emphasize that answers are self-reported rather than a certified score?

Software lock-in cannot be reduced to a single accredited percentage or vanity score. True portability is determined by physical file access on your hard drive, media custody, and plain text syntax. We present transparent diagnostic evidence and step-by-step remediation rather than misleading commercial certification labels.

What is the 30-day air-gap test for personal notes?

The air-gap test asks whether you can disconnect your computer from all internet access for a full month and still open, search, edit, link, and export your entire knowledge base. Applications that degrade, refuse sign-in, or fail to load search indices offline introduce severe availability risk.

How does proprietary block referencing harm future readability?

When an application assigns random IDs to individual paragraphs (such as ^block-id-123) and links to them internally, those references become unreadable outside that specific app. Standard heading anchors (#heading-slug) are universally supported across standard Markdown tools.

Are my notes or sample text uploaded to any remote server?

No. The evaluation engine and pattern scanner execute entirely client-side inside your browser sandbox. Zero data, vault titles, or text snippets are transmitted over the network.

Can I export the resulting portability report to my note vault?

Yes. You can copy or download the complete remediation checklist as a clean Markdown file or export the tabular findings as a formula-safe CSV spreadsheet.

Own Your Notes Permanently on Oyma

Your thinking deserves absolute longevity. Store your thoughts in clean, portable Markdown on your personal drive with zero cloud surveillance.

offline note portability checklist downloadDownload for Mac

No account needed. Intel Mac build