Architecture & Roadmap
How the Operational Intelligence System works.
What This Is
An AI-powered operational intelligence system that tracks what Morfoo is doing across every workstream. It ingests information from meetings, engineering tickets, documents, code commits, and team communication — then surfaces a truthful picture of delivery, decisions, and blockers. Nobody compiles status reports. The system watches everything and tells the story.
Information Sources
Google Meet / Gemini
Meeting transcripts with auto-correction, speaker attribution, and HR content filtering.
Jira
Engineering ticket status across 17 projects in 4 monitoring tiers.
Google Drive
Contracts, playbooks, spreadsheets. Documents classified as BI, status, or skip.
GitHub
Code commits — concrete delivery evidence. 4 repos actively monitored.
Notion
Project management layer. Tasks, initiatives, and decisions.
Slack
Team signals — wins, blockers, status updates. Full workspace search via user token.
How the Sweep Works
Health Check & Load State
Verify all connections (Notion, Drive, Jira, Slack, Neo4j, GitHub). Query the graph for baseline metrics.
Fan Out Discovery
7 parallel agents scan transcripts, Jira, documents, GitHub, Slack, and the knowledge graph simultaneously.
Resolve, Classify & Cross-Reference
Documents classified (BI/status/skip). Drive searched for mentioned artifacts. Content matched against graph entities.
Quality Check & Graph Write
Temporal ordering, 7-day rule, completion checking, dedup. Then write to Neo4j. Notion updates queued for review.
Patterns & Present
Graph-powered pattern detection: blocking chains, evidence gaps, owner workload, delivery rates. Findings presented.
Processing Principles
Evidence Over Assertion
Code commits and Jira tickets outweigh verbal statements.
Propose, Don't Act
The system proposes with evidence. Humans approve.
Latest Wins
Later information supersedes earlier. Old data becomes context.
Complete Picture
Every document, meeting, and commit gets ingested into the graph.
Roadmap
Now
Knowledge Graph Live
Neo4j on Railway with 100+ nodes. Sweep V2 writes to the graph. Document classification. Slack monitoring. Docker deployed.
May 2026
Daily Sweeps & Semantic Search
Neo4j accumulating knowledge. pgvector for internal semantic search. Proactive Drive discovery. Evidence verification.
Jun–Jul 2026
Executive Access
Marc gets conversational access via Slack. Graph-powered queries. Content filtering. Owner confirmation pings.
Q3 2026
Scheduled Autonomy
Daily cron sweeps. Auto-apply for low-risk updates. Agent activity logging. Cost visibility.
Q4 2026+
Intelligence & Proactive Insights
Pattern detection. Cross-initiative impact. Proactive Slack alerts. Meeting prep automation.
Technical Stack
| Component | Technology | Status |
|---|---|---|
| Orchestration | Claude Code (Anthropic Claude Opus) | Live |
| Project Management | Notion (MCP + API) | Live |
| Knowledge Graph | Neo4j Community Edition (Railway) | Live |
| Meeting Ingestion | Google Workspace MCP + Gemini | Live |
| Engineering Monitoring | Atlassian MCP (Jira) | Live |
| Document Monitoring | Google Workspace MCP | Live |
| Code Monitoring | Git / GitHub | Live |
| Team Communication | Slack MCP (user + bot tokens) | Live |
| Internal Semantic Search | pgvector (Postgres, behind firewall) | Next |
| Support Context | Pinecone (read-only, morfoo-rag) | Live |
| Deployment | Docker on Railway (ECS-ready) | Live |
The Vision
Information at Morfoo is scattered across meetings, documents, Jira tickets, code repos, and conversations. The people who need it to make decisions often don't have it — or get it too late. The OIS exists to solve that permanently. Every piece of company information flows into a single knowledge graph. Every stakeholder can access the context they need, when they need it, through a conversational interface that understands the full picture. The goal isn't dashboards or reports — it's ensuring that every decision at Morfoo is the best-informed version of itself.