Artemis Intelligence
Artemis Intelligence is the set of AI-assisted capabilities implemented in Artemis and the integration contracts through which Artemis uses external EduTelligence services. This page identifies ownership and boundaries; the developer AI pipeline catalog records the Artemis control plane in more detail.
Ecosystem map
| Component | Ownership and role | Artemis boundary | Learn more |
|---|---|---|---|
| Hyperion | Artemis-native AI-assisted authoring for programming exercises, FAQs, problem statements, checklists, quizzes, and staged code generation | Runs through Artemis services and Spring AI. Enablement and model-provider settings are Artemis configuration. | Hyperion setup, consistency-check architecture, Spring AI development |
| Atlas agents and orchestration | Artemis-native companion agents, competency orchestration, and tool callbacks | Artemis owns the course, competency, authorization, persistence, and tool contracts. Artemis Atlas configuration gates these paths; competency orchestration additionally requires the Atlas agent feature. | Developer AI pipeline catalog |
| Artemis Global Search | Artemis-native keyword and semantic search across Artemis entities | Artemis owns its Weaviate schemas, indexing/query flow, and authorization filters. It is independent of Iris RAG and lecture-answer retrieval. | Global Search & Weaviate setup, developer Weaviate setup |
| Iris / Pyris | External EduTelligence virtual-tutor service | Artemis creates typed requests and tracked jobs, receives authenticated callbacks, and delivers applicable results over WebSockets. Iris owns tutoring, ingestion, retrieval, and answer-pipeline internals. | Artemis integration catalog, Iris pipeline system, Iris RAG pipeline |
| Athena | External EduTelligence assessment service | Artemis selects/configures modules, forwards feedback and submission data, schedules applicable due-date work, and offers an authenticated repository-data boundary for authorized programming modules. | Artemis integration catalog, Athena module structure |
| AtlasML | Optional external EduTelligence ML service | Artemis has an optional, configuration-gated REST integration for competency-related calls and notifications. Selected user-facing paths additionally require the AtlasML feature. Artemis remains the owner of its competency data. | Artemis integration catalog, AtlasML pipelines |
| Memiris | Memory subsystem used through Iris | Artemis exposes a feature-gated, authenticated management boundary for memory data and deletion. Memory creation, retrieval, relationships, and sleep processing remain owned by Iris and Memiris. | Artemis integration catalog, Iris pipeline system |
| Logos | External model gateway/orchestrator | Logos is service-side infrastructure used only when a consumer is configured for it; this catalog makes no claim that Artemis integrates with Logos. | Logos source documentation |
| Weaviate | Shared vector infrastructure | Artemis Global Search and Iris can use one Weaviate instance with distinct collection namespaces. Their schemas and retrieval flows remain separate. | Global Search & Weaviate setup |
Ownership and operational scope
The table deliberately separates Artemis-native capabilities from external service integration contracts:
- Artemis-native: Hyperion, Atlas agents/orchestration, and Artemis Global Search. Artemis owns their application-level workflows, authorization, and persisted Artemis data.
- External services: Iris/Pyris and Athena execute their own service pipelines. Artemis owns request construction, authenticated boundaries, callback handling, and client delivery where applicable.
- Optional integration: AtlasML is not a prerequisite for the Artemis Atlas module. Its client boundary is available only when Artemis configuration enables it; selected user-facing operations also require the AtlasML feature.
- Shared infrastructure: A shared Weaviate instance does not merge Artemis Global Search with Iris RAG. Keep their collection namespaces separate when sharing an instance.
Configuration versus implementation constraints
Feature flags and properties control whether Artemis loads or invokes these capabilities. They are not evidence of a particular deployment, model provider, endpoint, credential, capacity, or rollout state. For example, Hyperion and Atlas model access is configured through Artemis and Spring AI, while per-request AI-selection information can be forwarded at supported Iris boundaries.
Conversely, source-level implementation choices such as Artemis Global Search schemas, callback routes, job tracking, and feature gates are part of the integration contract. Consult the developer AI pipeline catalog before changing an Artemis-side boundary, and use the linked service documentation for service-owned implementation details.