Athena Knowledge Platform
In this Engineering System, Athena means the open-source projectjannismilz/athena that we evaluated and adopted.
It is not a generic industry name for all knowledge platforms, and Data Relay Labs did not create the base Athena platform. We maintain a fork at xdr-labs/athena so we can adapt the upstream project to our Engineering System.
- Upstream: https://github.com/jannismilz/athena
- Our fork: https://github.com/xdr-labs/athena
Athena is not Wiki.js
Wiki.js is only one component inside Athena. Think of Athena as the whole adopted knowledge platform and Wiki.js as its human-facing wiki UI.What comes from upstream Athena
The following are already part of the upstream Athena architecture; they were not invented for this Engineering System.What our fork adds
Our fork adapts Athena to the Data Relay Engineering System.- GitHub/OpenSpec → Athena synchronization and generated knowledge projections
projects/<project>/...organization and project-scoped retrieval- provenance back to repository, ref, source path, and Git blob
- safer read-only MCP use for AI clients
- dependency and CI hardening for our operating model
RATIONALE_UNKNOWN is an Engineering System usage rule tested in the POC, not a built-in Athena feature. AI clients use it when the indexed engineering material does not contain the reason for a decision.
These additions do not change the role of each system: GitHub/OpenSpec holds the durable engineering record, while Athena remains a search and retrieval layer.
What is already running in the POC
These components are not merely planned. They were already started and exercised on thedev-dp-mirror POC host.
The POC is temporary. The production server is still being provisioned and the above stack has not yet been migrated to the final OVHcloud host.
Source-of-truth rule
Athena is intentionally derived.What the POC proved
The Data Relay Link POC validated the workflows that matter most for this Engineering System:- Cursor can connect to Athena through MCP.
- Semantic search works for Korean and English questions.
- Athena can retrieve a design rationale separately from the current contract.
- Cursor can return Wiki paths and original OpenSpec source paths.
- When the indexed material does not contain the reason for a decision, return
RATIONALE_UNKNOWNinstead of inventing an explanation. - Current specifications and archived decisions can be indexed together without turning Athena into a competing system of record.
Production deployment target
The current production target is an OVHcloud Singapore VPS. Selected baseline:
The hosting provider is an implementation choice, not an Engineering System rule. Moving to another provider should not change Athena’s role or the use of GitHub for durable engineering records.