Org2 vs Org Mode

Short version: Org2 is a local-first knowledge compiler that keeps Org's durable plain-text strengths while making the semantic/runtime layer portable across editors, automation, and publishing workflows.

Feature scan

Capability	Org Mode	Org2
---	---	---
Best default use	Deep Org workflows inside Emacs	Portable Org-shaped corpus across editors/tools
Runtime center	Emacs Lisp and Emacs buffers	Standalone parser, CLI, compiler, optional LSP
Editor experience	Best-in-class inside Emacs	Strongest today in VS Code; designed for more editors
Existing ecosystem	Mature, broad, battle-tested	Early, focused on portable shared infrastructure
File compatibility	Native `.org`	Reads `.org`; recommends `.org2` for new files
Compatibility goal	Defines the historical behavior	Practical compatibility with clearer modern semantics
Planning/agenda	Deep, mature, highly configurable	Core TODO/planning/agenda model with rich filters
Publishing	Mature Org export ecosystem	Built-in HTML export and project publishing
Automation boundary	Usually Emacs runtime or exported data	CLI/JSON/compiler outputs usable outside an editor
AI/provenance workflows	Possible through user configuration	Explicit corpus-flow, artifact metadata, and source-citation direction
Portability	Files are portable; runtime strongest in Emacs	Runtime designed to be portable from day one

High-level differences

Runtime model
- Org Mode: deeply integrated with Emacs runtime.
- Org2: standalone parser/CLI/compiler model, with editor integrations on top.

Workflow center
- Org Mode: Emacs commands and buffers first.
- Org2: editor integrations, workspace clients, publishing, and agents share one backend.

Portability
- Org Mode: strongest inside Emacs.
- Org2: designed for cross-editor usage from day one.

Compatibility stance

Existing .org files are supported as an everyday workflow.
New files are recommended as .org2.
Org Mode compatibility is valuable, especially for migration and shared plain-text habits.
Org2 favors clear portable behavior over feature-for-feature cloning.

What Org2 has today

Core syntax parsing: headings, drawers/properties, links, lists, blocks, tables, timestamps.
Task workflows: TODO state changes, planning updates.
Agenda querying with rich filtering.
Roam-adjacent workflows (IDs, backlinks, node creation, wiki links).
HTML export/publish pipeline.

Current gaps

Full Org Mode feature parity.
Mature habits/clocking/recurrence ecosystem.
Equivalent depth of ecosystem integrations.

Direction

Org2 is meant to make a plain-text knowledge corpus more computable, maintainable, and portable.

Keep the battle-tested core ideas that made Org great.
Make structured semantics, derived artifacts, and local knowledge operations the primary value proposition.
Drop accumulated cruft that slows down portability and adoption.
Support more editors natively, while also supporting Emacs well.
Keep portability as the non-negotiable center.
Treat CLI capabilities as shared infrastructure for editor integrations, publishing, health checks, and automation.