Operational Reasoning and Coordination Architecture

Run your company on infrastructure you own.

ORCA is open-source organisational infrastructure for small teams — governed memory in Git, request-driven coordination with approvals, and AI-assisted operations through AVA in Slack. Not a SaaS platform. Not an AI workforce.

What ORCA is

A company operating system you own.

Three pillars that work together — governed memory, visible requests, and AI-assisted coordination through functional systems.

Memory

Governed organisational artifacts in Git — the durable source of truth for decisions, policies, and context.

Requests

Work tracked with UIDs, status lifecycle, and approval policy. Visible, auditable, and human-accountable.

AVA

Coordination in Slack — capture, Q&A with citations, transcript ingestion, daily briefings, L2 proposals, and focus protection.

What ORCA is not

Deliberate boundaries.

Not an AI workforce
Not a virtual executive team
Not another SaaS product locking your knowledge away
A day with ORCA

The full daily loop.

From Slack capture to meeting ingestion to your morning briefing — every step lands in governed Git memory.

Step 1

Capture

#orca-operator
You Customer asked for Xero integration
AVA Captured as L1 memory in Git with provenance.
Step 2

Govern

#orca-approvals
AVA Pricing policy proposal — Awaiting Approval
Approve Reject
AVA Approved → L2 write committed to Git.
Step 3

Ingest

ingest/transcripts/
monday-standup.vtt
AVA Extracted 4 L1 captures · 1 L2 proposal → inbox

Drop a meeting transcript. AVA extracts governed captures and routes decision candidates to the proposal inbox — the raw file never becomes canonical memory.

Step 4

Start the day

#orca-briefings
AVA Daily briefing · Mon 21 Jun
Priorities: Xero integration, pricing policy approved. Open actions: 3 from standup.
Full artifact: ava/briefings/daily/2026-06-21.md
You What matters this week?
AVA Based on your Git memory: Xero integration request, pricing policy update, and 3 open actions from Monday's standup. Sources: captures/2026-06-18-xero.md, policies/pricing-v2.md
Why it exists

Small teams have too much to hold in their heads.

Decisions get lost.

Risks drift.

Actions disappear into chat.

Customer notes are scattered.

Meeting outcomes are forgotten.

AI tools give answers, but company context does not survive.

As teams add AI, the problem gets worse unless memory, approvals and accountability are designed from the start.

How it's built

From Slack to durable company memory.

Operators work in Slack. AVA routes capture, Q&A, and proposals. The workflow engine tracks requests and approvals. Everything durable lands in Git — semantic search via Qdrant is rebuildable and subordinate to Git.

Product Code you install once
Instance Your org's isolated data
Secrets — MVP: local file
secrets.env.example secrets.env (chmod 600) secrets.backend: local loaded at runtime
Secret values never in Git — optional 1Password backend for Business plans
Human Operators
Operator Founder
Operator Co-founder
Interfaces
Slack MVP
API Roadmap
MCP Roadmap
Web UI Roadmap
AVA — Active System
AVA Coordination System
Capture Q&A Transcripts Briefings Proposals Focus Protection Request Routing Governance
Supporting Capabilities
Memory Write Gateway
  • Schema validation
  • Policy enforcement
  • Provenance tracking
  • Audit events
Request Engine + Qdrant
  • UID & status lifecycle
  • Approval policy
  • Semantic search
  • Git wins on conflict
Source of Truth
Git Memory Governed Organisational Memory
L1 Captures L0 Briefings Meeting Captures L2 Policies Decisions Requests Approvals Audit Trail
Specialist Systems — Proposed
AVA is the only active system in MVP. Others read memory, contribute insights, and execute approved work when built.
SEC Security
FIN Finance
ENG Engineering
PMO Projects
GTM Go to Market
CXM Customer Success
AVA is the active coordination system — capture, Q&A with citations, transcript ingestion, daily briefings, L2 proposals, and focus protection. API and MCP are on the roadmap.
Secrets: MVP uses a local secrets.env file (chmod 600, gitignored). Validate with orca secrets validate — slot names only, never values. Nothing sensitive in Git. Install walkthrough →
Governance model

Proportional approvals.

Automation expands only where traceability and approval policy exist.

L0

Generated outputs

Automatic

Daily briefings, meeting summaries

L1

Operational memory

Automatic capture

Customer notes, actions, dismissals

L2

Governance memory

Explicit operator approval

Decisions, policies, commitments

Core components

What ORCA is built from.

Functional systems, not employees. Each is open, configurable and inspectable.

Core

Git Memory

Version-controlled organisational artifacts; source of truth for all durable knowledge.

Core

Memory Write Gateway

Schema validation, policy enforcement, provenance tracking, commit, and audit events.

Core

Request Engine

UID, status lifecycle, assignees, and approval policy tracked in PostgreSQL.

System (active)

AVA

Coordination: capture, Q&A with citations, transcript ingestion, daily briefings, L2 proposals, and focus protection.

Adapter (MVP)

Slack Interface

Operator and approvals channels with Block Kit — the MVP operator surface.

Adapter

Qdrant Search

Semantic retrieval over company memory. Git wins on conflict.

Also shipped: model registry, local secrets backend (optional 1Password). On the roadmap: web control plane, specialist systems (SEC, FIN, PMO), MCP and additional adapters.

Open-source principles

Built to be understood. Made to be moved.

ORCA is not just open-source in licence. The design philosophy is open: inspectable systems, configurable models, readable memory and infrastructure your company controls.

View on GitHub
Free and open source under MIT
Self-hosted first
One organisation per instance
Git as source of truth
Human accountability built in
No vendor lock-in
Community extensible
Built to be understood, not hidden
Status & roadmap

MVP complete. Honest boundaries.

Product MVP shipped June 2026 · Epics 1–7

Shipped in MVP

  • CLI: install, instance create, upgrade, doctor, backup
  • Git memory with governance gateway and audit
  • Workflow engine with approvals in Slack
  • AVA: capture, Q&A with citations, L2 proposals, focus protection, voice guardrails
  • Qdrant semantic search with Git authority
  • Model registry and local secrets file (secrets.env)
  • Transcript ingestion — drop zone, L1 extraction, L2 proposal candidates
  • Daily briefings — scheduled L0 generation and Slack delivery

On the roadmap

  • Web control plane
  • Additional ORCA Systems (SEC, FIN, PMO, …)
  • MCP and additional adapters
  • Dedicated documentation site

MVP scope: Slack is the operator interface. One organisation per instance. AVA is the only active system.

Ready to run the full loop?

ORCA MVP is complete and open source. Install it, connect Slack, drop a transcript, and start tomorrow with a governed briefing.

Questions or feedback?
Email us at hello@orcateam.org