Skip to main content
Version: 3.0 (Next)

V4.0+ — Long-Horizon Backlog

:::info Prerequisite: v3.0 fully delivered (per-item prerequisites noted individually below) Everything in this file has zero code footprint as of 2026-08-14 — verified by absence of any translation/RAG/enrichment/XML-output module under engine/ude/. Sources: .antigravitycli/planned.md "UDE v4.0 Requirements" §1–4, plus items pulled here from future_v2.md's former deferred-roadmap section that depend on V3.0 tracks not yet built. :::

A. AI-powered enrichment​

None of the items in this section have any implementation. translation_service in ude_global_config.json remains a reserved, inert field since v1.0.

REQ-BUS-05​

LLM Docstring Generation

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: REQ-FUN-09 (context-rich ingestion for the enrichment prompt)
  • Traces to: REQ-BUS-05
  • Evidence: no LLM client, enrichment CLI subcommand, or ude-enrich module exists anywhere under engine/ude/.

auto-document mode writes LLM-generated English docstrings directly back to source files; verify-document mode generates PR proposals or draft branches requiring developer approval before merge. Both modes must be non-interactive and CI/CD-compatible. Prerequisite: the v2.0 coverage gate (REQ-V2-08) — met. REQ-FUN-09 (Context-Rich Source Ingestion & Decoupled Tooling): the ude-enrich module/script must extract both the declaration (signature) and the definition (implementation body) for any undocumented entity, sending both as context to the LLM so generated docstrings reflect real internal logic, exceptions, and side effects — writing back only the resulting docstring, never touching functional code.

REQ-FUN-08 (split across two versions)​

Server-Side Push-Gate Enforcement Modes

  • Status: PARTIAL
  • Target: v2.0 (delivered half) / v4.0+ (remaining half)
  • Alias: —
  • Traces to: REQ-BUS-08
  • Evidence: engine/ude/coverage.py (apply_coverage_gate); REQ-V2-08 in v2.0-shipped.md.

Original scope: four --push-gate-mode values — reject, allow, auto-document, verify-document. reject/allow are delivered as REQ-V2-08's reject-undocumented/allow-undocumented modes (v2.0). auto-document/verify-document remain unimplemented, identical in scope to the two modes described under REQ-BUS-05 immediately above — this entry exists to keep REQ-FUN-08's id traceable to both halves rather than letting it silently disappear into REQ-BUS-05's text.

REQ-BUS-06​

Multi-Language Translation

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: REQ-FUN-06 (translation lifecycle & states)
  • Traces to: REQ-BUS-06
  • Evidence: no translation cache, override schema, or LLM integration exists; translation_service confirmed reserved through v1.0 and v2.0 per REQ-V2-01 in v2.0-shipped.md.

REQ-FUN-06 (AI Translation Lifecycle & States): each translation cache entry must carry a state flag, draft (default, AI-generated) or verified (promoted after Translation Manager review or XLIFF import). The translation generator must run only on commits/merges to the primary production branch; standard feature-branch builds run in secure read-only mode with no live LLM calls.

Incremental, gzip-compressed translation cache committed to Git, keyed by source-string hash, with human-override files for manual quality control. Activates the translation_service global-config field. Zero developer overhead for standard compilation runs — draft translations render with an optional "AI-translated draft" banner or fall back to source English.

REQ-FUN-10​

XLIFF Export/Import CLI Subcommands

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: —
  • Traces to: REQ-BUS-06

ude translation export <lang> --output <file.xlf> / ude translation import <file.xlf> for standard .xlf (v1.2/2.0) interchange with professional translation services, auto-promoting imported entries from draft to verified status.

REQ-FUN-18​

Asynchronous Non-Blocking Translation CLI

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: Q-2.1 / Q-2.3
  • Traces to: REQ-BUS-06

--read-only-cache (default for general CI/CD builds) parses and renders using existing translation files without writes; --write-cache (restricted to authorized Translation Manager sessions) commits updates and state promotion. CI-driven cache sync.

REQ-FUN-17​

Offline Local Gate Fallbacks

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: —
  • Traces to: REQ-BUS-05

When executed outside CI/CD, enforce an offline-by-default policy using local cache databases or mock placeholders instead of billing live LLM APIs.

REQ-FUN-11 (extension)​

Translation Cache Compression

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: —
  • Traces to: REQ-BUS-03

Reuses the v1.0 IR Gzip-compression mechanism (v1.0-mvp.md) for the translation cache database once it exists.

LLM token/cost accounting (sub-item of REQ-V3-12)​

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Traces to: REQ-BUS-07

The token-usage/cost-estimation half of v3.0-next.md's REQ-V3-12 build report — inert until an LLM integration exists to meter.

B. Expanded output formats​

REQ-BUS-02 (remainder)​

Structured XML Output

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: —
  • Traces to: REQ-BUS-02
  • Evidence: no XML renderer exists under engine/ude/renderers/.

API catalog rendered as structured XML with a documented, stable schema. (HTML and Hugo Markdown, the other two formats named in REQ-BUS-02, are v1.0-delivered; RAG JSON is REQ-V3-05, scoped V3.0.)

C. Advanced QA​

TEST-INT-12​

Wrapper Boundary Parameter Integrity

  • Status: UNIMPLEMENTED
  • Target: v4.0+
  • Alias: TEST-INT-12
  • Traces to: TSK-RND-09
  • Full spec: srs/integration_tests_specification.md.

Validates parameter lists, data types, and default values across the C++ → Python/Java/C# SWIG transformation boundary; alerts on renames, drops, or type remappings. Gated on REQ-V3-10 (SWIG wrapper-aware parsing) — this cannot precede its own prerequisite, which is why it sits in V4.0+ while TEST-INT-10/TEST-INT-11 (no such prerequisite) sit in V3.0.

Multi-language test instrumentation​

  • Status: UNIMPLEMENTED
  • Target: v4.0+

Auxiliary test tooling and data generators written natively in C++, C#, Java.

Graduation of REQ-V3-18/REQ-V3-19 to permanent gates​

  • Status: UNIMPLEMENTED
  • Target: v4.0+

Promote the V3.0 CSS visual-regression and search-index/anchor-integrity suites from pilot status to permanent, blocking CI gates once they have run long enough to be trusted.

D. Navigation & layout​

Visual layout upgrades​

  • Status: UNIMPLEMENTED
  • Target: v4.0+

:::caution Placeholder, not a specification This is the least-specified item in either source document — both planned.md and future_v2.md represent it as a single unelaborated bullet ("visual layout upgrades / new documentation sections"). Record it here as an explicit placeholder requiring requirements to be authored from scratch when V4.0 planning begins. Do not treat this bullet as if it already describes a real scope. :::

E. Server mode & its security envelope (contingent)​

:::danger Contingent on an unmade product decision Every item below presupposes a server-side execution mode that does not exist and has not been committed to as a product direction. Default placement here, marked contingent — see .antigravitycli/requirements_restructuring/opus_requirements_plan.md §12 decision 2. If the answer is "no, never," this entire section should be deleted, not perpetually deferred. :::

Public API surface​

  • Status: UNIMPLEMENTED / contingent
  • Target: v4.0+
  • Traces to: REQ-BUS-09

A server-side API surface accepting source code or project references for remote documentation generation — the prerequisite every item below depends on.

Sandboxed / ephemeral parsing containers​

  • Status: UNIMPLEMENTED / contingent
  • Target: v4.0+

Process and parse incoming source code in strictly isolated sandboxes or ephemeral containers to prevent sandbox-escape vulnerabilities.

Rate limiting & resource quotas​

  • Status: UNIMPLEMENTED / contingent
  • Target: v4.0+

Enforce strict CPU/memory quotas per request and API rate limiting against resource exhaustion.

Deep upload validation​

  • Status: UNIMPLEMENTED / contingent
  • Target: v4.0+

Deep validation of uploaded archives and files to prevent path traversal (e.g. malicious #include directives) and parser exploitation.

Ephemeral storage, TLS & encrypted caching​

  • Status: UNIMPLEMENTED / contingent
  • Target: v4.0+

Guarantee secure, immediate destruction of third-party proprietary source code post-processing; enforce TLS/HTTPS in transit and encryption for temporary caching.

Authentication, RBAC & audit logging​

  • Status: UNIMPLEMENTED / contingent
  • Target: v4.0+

Robust authentication (API keys, OAuth2/JWT) and Role-Based Access Control for all external API endpoints; secure audit logs of all incoming requests (user, timestamp, IP, payload size) for incident investigation and anomaly monitoring.