System overview
Theseus has an engineering side and an operating side. Engineers maintain an App in Desktop; a Runtime target receives and runs a delivered version; operators use the App through a runtime page or Player. This page gives the overall model, while task guides own the procedures.
Four user entry points
| Entry point | Main tasks | What it does not own |
|---|---|---|
| App Hub | Create, open, or clone projects and manage explicitly ordered project and AI-session lists | Editing a specific App |
| Editor | Maintain Pages, Objects, QG, data, and settings; inspect Problems; use Build, Start, and Debug | Acting as the field runtime terminal |
| Runtime target | Receive and run one App version | Project source, Git history, or AI conversations |
| Runtime page / Player | Display and operate an App that has already been delivered | Project creation, engineering edits, or Build |
Switching Runtime targets changes only where Build, Start, and Debug act. The current App's project files, version history, settings, and AI conversations remain on the development computer.
Core project resources
| Task | Main resource |
|---|---|
| Design an operator screen | Page; use a Component for reusable visual sections |
| Express equipment or business capabilities | Object |
| Orchestrate sequences, conditions, waits, and fault paths | QG |
| Store small state or parameter sets | Variable, Object, or TableStore |
| Call MES, ERP, or another external system | Query |
| Manage images, models, and translations | Asset and i18n |
A typical relationship is: a Page displays Object and Variable state; user actions call an Object, Query, or QG; QG owns sequencing, timeouts, and recovery across several actions. See Apps and core resources for detailed definitions.
How a project reaches the runtime
Project files → Build → Runtime target → Start / Debug → runtime page or Player
- Save updates project files only.
- Build checks the saved project and delivers a new version to the current target.
- Design checks local source pages and basic interaction without Object / Query execution.
- Start / Debug starts a version that has already been delivered.
- Stop ends the current run or preview.
See From Save to runtime for action and state meanings. Build and runtime acceptance is the authoritative procedure.
Continue by task
| What do you need to do? | Documentation |
|---|---|
| Create and run an App locally for the first time | Local quickstart |
| Find editor and project capabilities | User manual |
| Build, Start, Debug, or Stop | Build and debug |
| Connect field equipment or configure Player | Runtime and field delivery |
| Choose between a Qixin account, target account, or App user | Account and permission boundaries |
| Diagnose from a visible symptom | Troubleshooting |