JarvisIndependent work · Recorded SAMPLE

A conversation.
Its sources in view.

Explore four recorded SAMPLE conversations for briefing, source research, market information and a music request. The annular interface brings the reply, source context and connected-app descriptions into one voice workspace.

Recorded demonstration. No live model, microphone capture, visitor accounts or authenticated app actions.

Jarvis SAMPLE voice workspace with the cyan annular interface and app cards.
Static preview of the existing public SAMPLE. Recorded replies play in the separate demonstration.

The task

Keep the conversation legible.

A voice workspace needs to show what was asked, how the reply relates to its sources and which application a request refers to. This independent product study presents those steps through recorded examples.

The contribution

Interface, extensions and demonstration.

Designed the original cyan annular interface and conversation presentation around OpenJarvis. Developed voice and source extensions for the separate local application, then packaged four recorded SAMPLE scenarios as a static public demonstration. The public page describes connected-app workflows; it does not run the private integrations.

Built on OpenJarvis · Apache-2.0 (opens in a new tab)

Read the preserved OpenJarvis licence →

Independent work by Imad A. Adel. No client commission or upstream-provider endorsement is claimed.

Inside the recorded SAMPLE

Four requests. Four recorded replies.

01

Daily briefing

A recorded briefing demonstrates how a conversation can present daily context in one view.

02

Source research

A recorded research request connects the conversation presentation to its source context.

03

Market overview

A scripted market-information request demonstrates the presentation of a market reply. It is not a current quote service.

04

Music request

A recorded music request describes a connected-app workflow. It does not authenticate or control a visitor's music account.

David and Zira provide recorded previews and scenario replies. Model choices are SAMPLE labels with no inference endpoint or provider connection. App cards describe workflows without connecting accounts. The public package contains no private source library, runtime state or credentials; the private local runtime remains separate.

Your next project

Make the task
clear to its users.

Start with the conversation or workflow, who will use it and which sources or applications it needs. The brief helps scope an interface or prototype and its operating requirements.