Architecture & Terms
Architecture & Terms
Section titled “Architecture & Terms”This page gives a compact vocabulary for readers who want more precision than the product pages provide.
Key terms
Section titled “Key terms”Platform
Section titled “Platform”The shared layer that connects authoring, publication, runtime, workflow execution, operator surfaces, and governance.
Module
Section titled “Module”A named product area with a clear operational responsibility inside the current workflow. In the current public release, the named modules are Lead Intake, Campaign Manager, and Outbound.
Authoring
Section titled “Authoring”The private working-state environment where applications, flows, and product behavior are shaped before publication.
Published runtime
Section titled “Published runtime”The runtime experience that is meant to be used after a specific version has been published, rather than edited live.
Operator shell
Section titled “Operator shell”The part of the system that ties thread context, actions, workflow execution, and review posture together for human operators.
Workflow execution
Section titled “Workflow execution”The backend model for jobs, runs, approvals, and durable execution state that sits under the visible product surfaces.
Public architecture posture
Section titled “Public architecture posture”The public website intentionally compresses the internal architecture into a more readable shape:
- one platform story
- several named modules
- a curated docs layer
That compression is editorial, not deceptive. The goal is clarity for buyers and technical evaluators who need a usable mental model before they study deeper implementation detail.
Reading guidance
Section titled “Reading guidance”Use this page when a product page mentions shared concepts such as publication, runtime, workflow state, or operator review and you want a concise explanation of what those mean in the psi* vocabulary.