Java customer development workflow

K2 + Codex Java Development Workflow

Interactive view of how Codex uses K2 collections, Agents, Knowledge Feed, and Pipeline context before producing a Java patch for a legacy-style R&D workflow.

View architecture

3collections

15documents

4agents

1Knowledge Feed

Architecture diagram

How K2 turns private Java knowledge into Codex context

K2 does not replace Codex. It gives the coding agent a controlled path to private, versioned, and source-grounded evidence before planning or editing.

Evidence path is inspectable

Developer surface

Codex / Claude Code

The coding agent runs in a terminal or IDE and receives a Java feature request.

Local integration

stdio MCP server

A repo-local MCP process exposes K2 tools while keeping credentials in environment variables.

K2 platform

Hybrid retrieval + Agents

K2 applies metadata filters, dense/sparse retrieval, and specialized guide, docs, code, and architect agents.

Customer knowledge

Guides, code, docs, tests

Confluence-style rules, legacy Java source, tests, ADRs, API docs, and examples stay in separate corpora.

Agent output

Cited plan, patch, tests

Codex receives evidence-backed context before producing a patch and a verification trail.

Customer knowledge boundaryConfluence guides, legacy Java modules, tests, API docs, ADRs, and examples are ingested into separate K2 collections with metadata for framework, version, source kind, package, class, and path.

Retrieval and orchestration boundaryK2 metadata filters, hybrid dense/sparse search, Agents, Knowledge Feed, and Pipeline keep the context scoped, repeatable, and auditable.

Agent output boundaryCodex receives cited implementation context, then produces a plan, Java patch, focused test result, and reviewer evidence trail.

Add a Flink REST endpoint for checkpoint summary

Codex should identify guardrails, Flink 2.2 docs, Java implementation anchors, route registration, message classes, and tests before editing code.

Collections

Agents

Orchestration

Codex output

Select a step or node to inspect how evidence moves from K2 into Codex.Live smoke: 4 agent steps returned sources