Compare vs a wiki
A wiki is where knowledge goes to be written once and read never.
It asks people to stop building and write documentation. So the page is written at launch, drifts from the code within weeks, and the next engineer trusts the code over the doc. Correctly.
A wiki
Oynix
Who writes it
People, on their own time, as a second job.
It forms from the work already happening.
How current
As current as its most diligent author.
Updated as the code and tickets change.
Trust
You verify against the code anyway.
Linked to the code, so it cannot silently drift.
Cross-source
Prose someone typed.
Code, tickets and threads, connected.
For an agent
A page to be scraped and hoped over.
An MCP server returning exact facts.
Over time
Rots unless someone tends it.
Every session leaves it better.
Where a wiki still wins
It is the right home for things humans write for humans: onboarding narrative, culture, the long-form how we think. Oynix is not trying to be your handbook. It remembers the engineering context a handbook never captures.
Keep the wiki for the story. Let Oynix keep the facts.
Other comparisons