Skip to main content
Applications

01 · SENSE

MoLing

MoLing

MoShun AI Lab's interaction entry point — an exploration of how text, voice, vision, context and tool use can share a single space.

01Overview

What this is

MoLing is not a chat box but an interaction field you can see. Voice, text and visual signals enter one shared context, and the system’s state — listening, retrieving, answering — is expressed visually rather than hidden behind a spinner.

02Problem

The problem

Most AI interfaces compress rich capability into a single input box: you cannot see what the system is doing, or where an answer came from. When interaction is reduced to a stream of text, the value of voice, vision and context is wasted.

03Capability

Core capabilities

  • 01

    Multimodal input, one context

    Text and voice share one session and one knowledge scope; switching input mode never drops the thread.

  • 02

    Visible system state

    Listening, thinking, retrieving and answering each map to a distinct visual state, so the process itself is readable.

  • 03

    Bounded knowledge scope

    Answers are drawn from a configured knowledge scope rather than unbounded open generation.

  • 04

    Explicit device permission

    Microphone and camera activate only when the user turns them on, and can be switched off at any moment.

04Flow

How it works

  1. 01

    Enter

    The interface wakes, states that it is in integration mode, and shows which inputs are available.

  2. 02

    Input

    The user opens with text or voice; the visual state responds to input intensity.

  3. 03

    Understand

    Intent is parsed and, where needed, retrieved against the configured knowledge scope.

  4. 04

    Respond

    The answer returns, context is retained, and the user can follow up or switch modality.

05Position

Where it sits across the capability domains

InputOutcome
  1. 01 · SENSESense & InteractPrimary domain
  2. 02 · UNDERSTANDKnowledge & JudgementAlso touches
  3. 03 · CREATEContent & GenerationNot directly involved
  4. 04 · ACTAutomation & ExecutionNot directly involved
  5. 05 · ORCHESTRATEEnterprise OrchestrationNot directly involved
The primary domain defines what this application is responsible for; the domains it also touches show what it has to work with. The diagram describes position only — it is not a statement of delivery scope.
06Use cases

Use cases

  1. 01

    Brand narration on a website

    Moves a visitor from static reading into a brand experience they can talk to.

  2. 02

    Customer enquiry

    Answers questions on capability, use cases and partnership quickly.

  3. 03

    On-site exhibition displays

    Suits immersive large-format screens, product launches and client reception spaces.

07Connections

Enterprise system connections

  • Enterprise knowledge base
  • Product and documentation sources
  • Web and exhibition front-ends
  • Support ticketing
08Governance

Data, permission and deployment

Text and live voice connect to Mo-Voice with a one-time short-lived token; camera frames are never read, displayed, stored or uploaded. Microphone audio is sent only for the active session while the user has enabled it, and stops immediately when switched off. Knowledge scope and session retention are configured per engagement.

09Availability

What is open today

MoLing on this site runs in integration mode: text and live voice are connected to Mo-Voice, while the camera/vision channel remains unconnected. Full capability for enterprise scenarios is delivered as a project.

Experience Preview

Apply for access

Want to know what this does in your own context?

Tell us the scenario and the systems already in place. We will start by judging whether it is worth doing at all, then talk about how.

Openly explorable, still evolving, and not representative of the final product.