Product overview#

A desktop workspace for AOTX conversations and persistent CCIR runtimes.

AOTX-PRISM brings conversations, project history, runtime setup and memory evidence into one desktop application. Connect an existing AOTX gateway or start a local installation. Choose ordinary conversations or persistent CCIR spaces, with explicit instructions for each new conversation.

The interface uses silver panel headers, a restrained amber accent and dockable windows. A graphite theme provides the same layout on dark surfaces. Fonts and application assets are local.

Version 0.1.0 is a public early release. Get the source from the PRISM repository. See installation, changes and support boundaries.

Capabilities#

Area	Current behavior
Conversations	Text, advertised JPEG/WAV input, incremental output and exact cancellation.
Conversation setup	Editable neutral instructions for new ordinary and CCIR conversations.
Projects	Local history, conversation names, archives, JSON exports and read-only file previews.
Runtime setup	Installation checks, GPU selection, saved profiles and owned process shutdown.
Shared CCIR	Complete file creation, verification, activation, saved shutdown and stopped-file copies.
Persistent spaces	Participant membership, scoped conversations, ordered events and exact request recovery.
Affect and controls	Qualified model controls, permitted runtime settings and scoped state readback.
Evidence and activity	Typed memory, source references, explicit publication, policy counters and controls.
Workspace	Floating or docked panels, resizing, maximize/restore and saved layout.

Project folders do not grant model file access. Model-driven file edits and command execution are outside this version. AOTX owns inference and persistent memory; PRISM displays the interfaces advertised by the connected gateway.

Install or build#

The desktop target is Linux x86-64. A packaged installation includes Electron and does not require Node.js. It still requires a graphical session, system desktop libraries, a working Chromium sandbox and Python for installation.

For a supplied package, follow Linux installation. AOTX executables, model files and gateway dependencies are separate installations. PRISM does not download them. An external gateway can run inference on another machine.

For a source checkout, use Node.js 22.16 or later, npm and Python 3.12 or later:

npm ci
npm run build
npm start

Run these commands from the repository root. Source builds need the same desktop libraries and sandbox support as installed packages.

Start a conversation#

Open Project and select an existing folder for local history.
Open Connection and enter the gateway URL and bearer token.
Select Connect.
Open Models, select an advertised model and apply generation settings.
Select + New conversation.
Set a name and review the neutral system prompt.
Select Create conversation, enter a message and select Send message.

Use HTTPS for a remote gateway, or HTTP through a loopback SSH tunnel. The bearer token stays in process memory. Enter it again after restarting PRISM.

First use covers the full procedure. Runtime setup covers starting an installed local backend.

Use persistent CCIR conversations#

Connect a complete shared runtime, then open CCIR workspace. Register the participant, select a space and create a conversation. New CCIR conversation opens the same prompt editor with the runtime's supported byte limit.

CCIR instructions remain fixed for that conversation. Runtime memory rules and authenticated actor context still apply. Existing conversations retain their original instructions; a new default does not rewrite them.

A local history entry, completed response and saved CCIR result are different states. Inspect the save receipt before relying on recovery. Stop a writer before copying its complete file. See shared workspaces.

Documentation#

The manual index provides a reading order and shared terms.

Task	Guide
Install, upgrade or remove PRISM	Installation
Choose a project and send the first message	First use
Manage folders, history, exports and media	Projects and files
Select a GPU, runtime or generation profile	Runtime setup
Save and restore persistent work	Shared CCIR
Configure controls and runtime affect	Affect and model controls
Inspect sources and background work	Evidence and activity
Recover a failed connection or request	Troubleshooting
Understand data and permission boundaries	Architecture and security

Development#

Use the locked dependencies. Run checks appropriate to the changed surface; testing distinguishes source, protocol, visible desktop and native runtime checks. Contribution rules describe branches, review and pull requests.

Source layout

text

src/        React views, Dockview layout and local styles
desktop/    gateway adapters, project storage and runtime supervision
shared/     typed commands, bounded data and protocol validation
public/     application marks, fonts and font licenses
docs/       user guides, reference and documentation artwork
tests/      protocol, storage, lifecycle, package and desktop checks
tools/      source gates and committed-source package builder
packaging/  package verification, per-user installer and launcher

Apache License, Version 2.0. See LICENSE, NOTICE and dependency notices.