Draft: feat(okf): OKF Server pillar - knowledge/grounding layer
OKF Server — knowledge/grounding pillar
Pillar of the agentic-enablement initiative (umbrella PRD on main). The governed, versioned, multi-graph knowledge layer agents ground in and cite.
Artifacts: OKF PRD + architecture + ADRs (okf-001…018) + sprint tracker _bmad-output/implementation-artifacts/sprint-status-okf-server.yaml.
Status — implementation in progress on feat/okf-server
Node-side Epic 2 (ungated) builds first. Python multi-graph grounding (Epic 1) + dataprep wiring (2.6) inherit the OPEA 1.5 bump (!277 (merged)) when it merges to main.
✅ Done
-
Story 2.1 — OKF Server skeleton + deploy wiring (#877 (closed)): Node/Express
createApp()behind Kong at/api/okf, three-way deploy (compose/Ansible/CI), MELT-integrated (OTel → VictoriaMetrics/Traces/Logs → Grafana). Code-reviewed (3-layer) + deployed in the local build. -
Story 2.2 — ArangoDB OKF meta collections + repository CRUD API (#878 (closed)):
/api/okf/reposCRUD over four control-plane collections (same ArangoDB), via the shareddb-connection-service(no reinvented infra), DB-enforced uniqueness on(name, domain), audit,tools-adminauthz, MELT. 46 tests green. Code-reviewed (3-layer) + deployed.
🔜 Next (ungated, Node)
2.3 OKF parser · 2.4 conformance validation · 2.5 document-repository bundle ingest route · 2.7 source sync · 2.8 PII redaction · Epic 3 (Vue admin UI)
⛔ Gated (OPEA 1.5 bump !277 (merged))
2.6 dataprep graph_name wiring + graph creation/retract · Epic 1 multi-graph grounding
This is a long-lived WIP MR for the pillar; it stays Draft until the epic is mergeable. Story status is tracked in sprint-status-okf-server.yaml and mirrored to the okf-server::* issues.