Memtrace
Memtrace code search & Code Graph
Section titled “Memtrace code search & Code Graph”The Memtrace top-row mode, the Code Intelligence sidebar drawer, and the project window’s Code Graph tab. An auto-started Memtrace daemon (localhost:4848 / 4848-mcp) indexes all project paths for live semantic code search; a parent-directory workspace traces sibling repos, with status, version, and update controls in the drawer.
MCP tool: orbit_code_search (plus the Memtrace MCP tools).
Cortex governance and decision lineage
Section titled “Cortex governance and decision lineage”Settings → Memtrace → Governance intake; the Pipeline Code Impact Check. Cortex is Memtrace’s decision-memory layer: managed rule changes are previewed into Cortex before they take effect, decision IDs stay stable over time, and an agent (or you) can ask why a symbol exists, verify a decision’s current detail, and see governing decisions surfaced during approval. None of this blocks approval when Cortex happens to be unavailable — it degrades to no extra context rather than stalling the run.
MCP tools: orbit_recall_decision, orbit_why_here, orbit_decision_detail.
Memtrace Fleet observation log
Section titled “Memtrace Fleet observation log”Memtrace panel → Fleet log; conflict warnings; Needs You. When Memtrace is healthy, Orbit records prompt intents and edit episodes across agents working the same project, and surfaces overlap warnings by severity class — Class B overlaps are shown for awareness, Class C collisions route to Needs You for a human look. Neither class gates launch, integration, or shipping on its own.
File locks
Section titled “File locks”Pipeline advisory chips plus preamble enforcement. Mark files or globs that queued prompts must not touch; agents self-enforce via their preamble, and Orbit rejects a completion (❌ Failed) if the commit modified a locked file — the commit itself is never rolled back. Surfaced in orbit_status as fileLocks.
MCP tools: orbit_lock_file, orbit_list_locks, orbit_unlock_file.