Kendriala
AI-Native Organizational Operating System
Kendriala is an AI-native organizational operating system: a research project exploring whether software can become an organization's long-term memory.
Kendriala represents the central repository of an organization's operational intelligence: a place where knowledge, decisions, relationships and context come together to create a living organizational memory.
Unified workspace where every piece of work is connected and context is automatically captured.
The Problem
Organizations don't suffer from a lack of software: they suffer from a lack of context. Customer conversations, decisions, project history, and institutional knowledge are scattered across a dozen disconnected tools, and the relationships between them exist only in people's heads.
When people leave, context leaves with them. AI makes this problem impossible to ignore: models can now reason remarkably well, but they can't reason about information they can't see.
The Hypothesis
If organizational software is designed from the ground up to generate context as a byproduct of everyday work: meetings producing structured decisions, projects preserving their own history, every action strengthening a graph of how things connect, then organizational memory becomes something software does, not something people are asked to maintain.
Every architectural decision in the build is registered as a testable hypothesis. Findings: including the failures, are published as working papers under The Organizational Context Project.
How Kendriala Works
Key Features (In Progress)
Making money move.
Kendriala's first slice is deliberately unglamorous: invoicing and payments (Razorpay for domestic clients, Wise for cross-border), running on an append-only event log with full audit infrastructure. Starting with billing is a research position, not a limitation: financial events are the most ground-truthed context any system will ever capture, and a platform asking to become an organization's memory should prove it can handle the organization's money first.
Next: moving daily delivery work, projects, milestones, decisions: into the system, which is where the core adoption hypothesis faces its first real test.
My Role
This is a 100% self-initiated project. I'm responsible for the entire product lifecycle.
- ✓ Product Vision & Strategy
- ✓ User Research & Problem Discovery
- ✓ Product Architecture
- ✓ Information Architecture
- ✓ UX & Interaction Design
- ✓ Feature Prioritization
- ✓ AI Workflow Design
- ✓ Database & System Design
- ✓ Full-stack Development
- ✓ Functional Specifications
- ✓ Roadmap & Execution
- ✓ Continuous Iteration
Tech Stack
What's actually built: registered decisions, not aspirations.
Graph engine deferred: relational spine with graph semantics until measured query latency demands otherwise. See WP-001 §5.2.
Two working papers published.
Every architectural decision in the build is registered as a testable hypothesis and published as a working paper: before results exist, so they can confirm or embarrass the design when they arrive.