Skip to content

docs(temporal): Java EE / Jakarta EE edge-resolver spec + design + plan#94

Open
avfirsov wants to merge 3 commits into
zzet:mainfrom
avfirsov:pr/javaee-docs
Open

docs(temporal): Java EE / Jakarta EE edge-resolver spec + design + plan#94
avfirsov wants to merge 3 commits into
zzet:mainfrom
avfirsov:pr/javaee-docs

Conversation

@avfirsov

Copy link
Copy Markdown
Contributor

What

Adds the Java EE / Jakarta EE edge-resolver design docs (no code):

  • docs/java-ee-edge-resolvers.md — the spec/ТЗ: problem (Java EE wires components declaratively via annotations/descriptors → ~30% lost edges on a large monolith), per-subsystem rules (JMS, EJB, REST, SOAP, Servlet, CDI), synthetic nodes, edge-origin classification, priorities, acceptance criteria + metrics.
  • docs/design/06-javaee-synthesizer.md — how it maps onto gortex internals: the FrameworkSynthesizer extract→resolve split, layer-ownership table (EJB/CDI/JMS = synthesizer EdgeCalls; REST/SOAP = contract enrichment EdgeMatches; filter-chain = ordered-edge pass), EdgeImplements/EdgeExtends subtype resolution, contract-matcher reuse for cross-repo, confidence tiers, and settled decisions (ambiguity → hidden-speculative; @Resource signal-priority; @Alternative/@Specializes; audience via MetaSpeculative).
  • docs/design/07-javaee-implementation-plan.md — phased execution plan (0 shared infra, A EJB+CDI, B REST/Servlet, C JMS, D XML descriptors, E SOAP) with file touch-points, edge tiers, tests, sequencing and risk gates.

Why

Captures the design + roadmap for closing gortex's Java EE blind spots (today Java symbols index via tree-sitter but CDI/EJB/JMS/JAX-RS dispatch edges are missing) so the implementation can land as reviewable, independently-shippable PRs. Grounded in the actual gortex synthesizer/contract machinery (file:line touch-points in §12 of doc 06).

Docs-only — no code changes.

AVFirsov and others added 3 commits June 15, 2026 08:07
Merges docs/java-ee-edge-resolvers.md (problem/corpus/priorities/acceptance)
with the gortex integration design (FrameworkSynthesizer extract→resolve,
contract reuse, layer-ownership table) and architecture-review fixes
(InferImplements interface-only+repo-gated, Cartesian matcher, @Alternative/
@resource traps). Decisions D1–D4 resolved with rationale.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Buildable execution plan derived from docs/design/06-javaee-synthesizer.md:
Phase 0 shared infra, A (EJB+CDI), B (REST/Servlet), C (JMS), D (XML
descriptors), E (SOAP). Atomic tasks with file touch-points, edge tiers,
tests, acceptance, sequencing, and risk gates.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@zzet zzet added the documentation Improvements or additions to documentation label Jun 15, 2026
@avfirsov

Copy link
Copy Markdown
Contributor Author

Friendly ping @zzet 🙂 — CI is green (9/9) and the branch is MERGEABLE / CLEAN (no conflicts, not behind main). This one is docs-only (Java EE / Jakarta EE edge-resolver spec + design + plan), so it's low-risk to land. Happy to rebase or address any feedback whenever you get a chance. Thanks!

@zzet

zzet commented Jun 16, 2026

Copy link
Copy Markdown
Owner

Hey @avfirsov, I prefer to keep the documents in English in the repository. As well as I have to think if such type of docs are necessary to have in git or better to have a different format. Problem with those docs that they have to be maintained (not outdated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants