Skip to content

Engineering ​

Engineering pages cover how Orion is built: its architecture, its public interfaces, and proposals for changing them.

An audit or proposal is a snapshot. It recommends changes as of the day it was written, and once a change is settled, the call moves into the decisions. For what Orion accepts today, see the CLI and MCP reference.

Threads ​

  • Architecture: how the CLI, server, app, desktop shell, MCP server, and sources fit together.
  • CLI and agents: the CLI as the one implementation, its queries and batch edits, and the MCP server that wraps it.
  • Data and sync: one document per canvas under a shared lock, backups, merges, undo, and the move toward operations and files.
  • Interface audit: what stays, changes, or goes on each public surface before the first release.
  • Performance: the 1,000-card target, the work that keeps the canvas responsive, and the perf harness that checks each pull request.

Timeline ​

Each date is when the pull request was opened. Pull requests still open are marked as in review.

October 5, 2026 ​

October 6, 2026 ​

October 7, 2026 ​

October 8, 2026 ​

October 9, 2026 ​

October 10, 2026 ​

October 11, 2026 ​

October 12, 2026 ​

October 13, 2026 ​

October 14, 2026 ​

October 15, 2026 ​

October 16, 2026 ​

October 17, 2026 ​