Skip to content
Artemis Omni

ArtemisIX · Registry

Modules, dimensions & departments

Every Artemis demonstrator, classified along the dimensional ladder and routed to a department. The registry scans the apps folder on each request — drop in a new app and it self-registers.

11live modules
5departments
5active dimensions
Live registry API →

The dimensional ladder

D2Documentation1

Drawings, dimensioned shop cards, print-safe output.

D3Geometry5

Parametric 3D models and fabrication geometry.

D4Assembly1

Connectors, joinery, and sequence of erection.

D5Commercial0

BOM, takeoff, mass, and cost/forecast telemetry.

D6Geospatial3

Mapbox/satellite command atlases and GIS.

D7Identity1

Brand marks and cinematic identity systems.

Autonomous operation — multiple AI & connections

ArtemisIX orchestrates several providers and a self-maintaining registry. Each connection upgrades from simulation to live the moment its key is present.

Connections

  • Anthropic (Claude)
    Reasoning & languageAuto-prompt, plot, movie treatments, six-dialect translation
    ANTHROPIC_API_KEY
    key-required
  • Higgsfield / Replicate
    Media synthesisImage, video, render, sound generators
    HIGGSFIELD_API_KEY / REPLICATE_API_TOKEN
    key-required
  • model-viewer (WebGL)
    3D presentationLive GLB conceptual model + bundled three.js workbenches
    built-in
    live
  • Mapbox GL
    GeospatialAtlas department — 3D satellite command atlases
    NEXT_PUBLIC_MAPBOX_TOKEN
    key-required
  • Self-discovering registry
    Autonomous maintenanceScans public/artemisix/apps and auto-classifies new modules
    built-in
    live
  • Artemis simulation engine
    Key-free fallbackDeterministic SVG/WAV/text when no provider key is present
    built-in
    live

Self-maintenance loop

  1. 1
    Discover
    On each request the registry scans the apps folder — new HTML demonstrators appear automatically.
  2. 2
    Classify
    Each app is assigned a dimension, department, and module code — known apps via overrides, unknown via keyword inference.
  3. 3
    Generate
    The studio engine produces prompts/media/3D/dialects; provider keys upgrade simulation output to live.
  4. 4
    Expose
    The registry is published at /api/artemisix/registry so other agents and connections can read live state.