The Oynix Manifesto
Organizations don't lose code. They lose context.
A record of what we believe, and why Oynix exists. Read it once. If you have run a team through the loss it describes, you already agree.
I
Knowledge dies quietly
Code survives. Documentation survives. People don't. A senior engineer leaves, and six months later nobody remembers why the retry logic exists, why that service was split in two, or which outage the workaround was written for.
It never fails with an alarm. It erodes. The decision lived in a Slack thread. The rationale left with the person. The Jira ticket got closed. What remains is code that works and no one who knows why.
II
What we believe
Memory should be a byproduct of doing the work, not a second job piled on top of it. Nobody writes the doc that would have saved the next person a day. They are busy building. So the memory has to form on its own, from the work that already happens.
Memory, not documentation
Documentation explains what happened. Memory explains why, and stays true as the code changes.
The engine, not the vault
Your code and your graph stay in your infrastructure. We ship the software. We never hold the data.
III
AI is blind, not stupid
AI coding agents are astonishing. They also start every session from zero. They understand code. They do not understand your organization. They don't know who owns this, why it was built, what Slack decided, or what changed last week.
So the agent guesses. It rewrites what someone already solved. It reintroduces the bug the workaround was fixing. Not because it is weak, but because it is blind. Oynix is the memory it has been missing.
IV
The same question, asked twice
A new engineer asks why the webhook retries three times. Someone explains it in a thread. Three months later another new engineer asks the same question, and someone explains it again. The answer was never wrong. It was just never kept.
Oynix writes the answer back where the question was asked, into the graph the next agent already reads. So the first person to work something out is the last person who has to. A read-only knowledge base decays. Memory that writes back compounds. Every session leaves it better than it found it, and the work of explaining your codebase happens once.
V
Oy plus Nix
Oy, from the Greek article: the. Nix, from the Latin: nothing. Oynix is the layer that makes sure nothing your team builds or decides ever disappears. Not for the humans who move on, and not for the AI that starts each conversation new.
Preserve the why. Let the what evolve.