Developer infrastructure
Orthic Labs builds local-first tools for teams using coding agents: durable context, evidence-backed delivery, live coordination & a repository map that includes both code and documentation.
Local data plane · explicit proof · portable recordsThese are systems for operating AI-assisted development—not a prompt bundle. Each makes a different part of engineering work inspectable, recoverable & useful across sessions.
Context infrastructure that gathers scoped evidence, ranks freshness and authority, fits it into one budget, then returns a context packet with a receipt for what was admitted, omitted, stale or unavailable. MemRight keeps durable memory local in SQLite.
Context with a receiptAn evidence ledger for engineering claims. It binds a claim to source hashes, checks & policy; required proof must be present before signoff. When inputs change, dependency-aware invalidation makes old proof fail instead of silently passing.
Proof before signoffA local hub for steering live Codex & Claude work between seats. Its SQLite WAL store records messages, approvals, handoffs, leases, delivery & deduplication, while session bridges keep provider credentials and hidden context outside the hub.
Live work, coordinated locallyA local SQLite evidence graph for repositories. It maps symbols, files, tests, configuration, plans & ADRs together, then compares documentation claims with current code so a team can find what is true, stale, contradictory or unknown.
Code + document truthA review-gated learning layer that turns accepted corrections into durable preferences. It distinguishes standing rules from one-off facts, keeps an audit receipt, supports rollback & stores accepted records through MemRight’s local SQLite memory.
Corrections that stickRun a second isolated Claude or Codex session beside your subscribed desktop app. Your primary session stays untouched; a local proxy routes separate model slots, credentials & profile state for the second instance.
Explore ClaudeCodeX ↗