3. Goals, Non-Goals, and Success Criteria

GoalsCopy Anchor Link

• Open an explicitly selected file and display useful content with minimal delay and chrome.
• Preserve editable text encoding, byte-order-mark intent, newline structure, and external revisions without silent data loss.
• Support up to 32 open documents through compact tabs while keeping one active document visually dominant.
• Expose available host, provider, embedded, derived, and renderer-specific metadata through a dismissible inspector.
• Provide one shared behavior contract across Windows, macOS, Linux, and Android, including provider-backed Android documents.
• Keep core viewing, editing, inspection, recovery, and diagnostics offline and account-free.
• Add format families through isolated renderer contracts, hostile-file limits, conformance tests, and truthful release gates.
• Support standalone and Markdown-embedded Mermaid diagrams without rewriting authored layout or requiring an online renderer.
• Produce signed, checksummed, licensed, testable artifacts at a zero-dollar application price.

Non-goalsCopy Anchor Link

• Workspaces, project trees, project indexing, project restore, or repository management.
• Language servers, compilation, debugging, terminals, refactoring, package management, or IDE extension systems.
• Browser extensions, browser-hosted file uploads, cloud conversion, accounts, synchronization, collaboration, or telemetry-dependent operation.
• A public plugin marketplace or third-party native-code loading surface.
• Rich document authoring, PDF editing, office-format editing, format conversion, or layout-publishing tools.
• Automatic loading of remote images, fonts, scripts, styles, documents, or office references.
• Electron or a bundled Chromium runtime.

Product success criteriaCopy Anchor Link

• v0.1.4 ships official Windows, macOS, Linux, and Android artifacts with Markdown, Mermaid, and text/source view/edit, tabs, metadata inspection, save conflict protection, and crash recovery.
• Every official support claim has automated evidence or an explicit, repeatable manual verification record.
• No save path silently overwrites a conflicting external revision or discards dirty editor state.
• A user can open a file, switch among tabs, inspect metadata, search, edit supported text, and save using keyboard alone on desktop and touch alone on Android.
• Core operation produces no file-content network request and requires no sign-in.