Max Connect
Max Connect · evidence atom

RMI integrations must be rewritten to REST APIs

MAXCONNECT-TECH-007 · TECH · amber · medium-high

← Pack hub

---

id: MAXCONNECT-TECH-007

title: RMI integrations must be rewritten to REST APIs

type: TECH

state: amber

area: F-feasibility

purpose: notebooklm-tier2-decomposition

priority: A

work_kind: A

provenance: research

confidence: medium-high

triangulated: true

engagement: maxconnect

sources:

- uri: file://notebooklm/answers/20260611T200650Z-01-product-workings.md

role: supporting

- uri: file://notebooklm/answers/20260611T200650Z-02-architecture-integrations.md

role: supporting

- uri: file://notebooklm/answers/20260611T200650Z-03-migration-risks.md

role: supporting

relates_to: []

feeds_atoms: []

open_questions: []

needs_validation: []

resolution_log:

- 2026-06-12: Decomposed from broad NotebookLM synthesis into pack-grade atom for Max Connect Discovery.

module:

---

Remote Method Invocation (RMI) is no longer supported in MAS. External applications or custom extensions that depend on RMI need to be rewritten around REST APIs before or during the migration.

Amendment log