MotusArtium - Semantic Art History Atlas

Manifest

Navigate art history through live query surfaces and multilingual semantics.

MotusArtium is designed as a cultural instrument rather than a dashboard: a place where GraphQL documents, semantic relationships, and language-aware exploration are visible at the same time.

Featured Journey

Impressionism → Claude Monet → Water Lilies → Musee de l'Orangerie

Semantic Compass

Lens

The semantic compass replaces flat filters with interactive lenses: emphasize movement, artist, work, place, time, or influence and let the atlas reorganize itself dynamically.

Quick Lens Presets

Current Lens

Emphasis: Influence-aware, movement-centered, French surface
Goal: Make GraphQL and Multilingual visible at the same time, not hidden under a generic graph interface.

Observatory Constellation

The central visualization brings entities, query logic, and language context into one visible field. Interact with nodes to explore relationships and navigate through art history.

Current Trail Selection should always produce a visual focus, a GraphQL document shift, and a language-aware summary. This overlay is where we can narrate those transitions.

Multilingual mount: this panel is reserved for embedded Multilingual UI fragments and diagnostics as we progressively connect more of the original runtime into the Observatory shell.

Interface Surface

The shell changes prompts, labels, and interpretation text with the active language.

Entity Surface

Selected entities can be read through different language surfaces while keeping the same Wikidata identity.

Source Lens

asynchrone déf charger_mouvement(id):
    attendre ui.etat.charger_mouvement(id)

Query Mirror

movement_details.graphql

Session Flow

Bootstrapping Awaiting first live GraphQL request.

Variables

{
  "id": "Q40415",
  "languageCode": "fr"
}

Document

Loading document...

Response Shape

{
  item: {
    id,
    label,
    statements(...)
  }
}

Interpretation

This panel turns the data layer into part of the experience: the app should always be able to show which GraphQL document is active, which variables are in play, and what semantic shape is being retrieved.