Factory

The Factory is the S-Launch workflow engine. It models repeatable business processes — file preparation, prepress, automated emails, approvals — as graphs of steps that can be authored, scheduled, executed, and audited.

The Factory is split into four cooperating resources:

Resource	What it is	Lives at
Blueprints	Workflow templates — the definition of what a workflow does.	/api/factory/workflows/*
Tickets	Inbound requests to run a blueprint — the "this is what I want done" record.	/api/factory/tickets/*
Assemblies	Execution histories — every blueprint run produces one assembly with its outcome.	/api/factory/history/*
Tasks	The individual steps inside an assembly, plus their status and output.	/api/factory/tasks/*

The lifecycle is straightforward: a blueprint defines the workflow, a ticket kicks off a run, the runtime emits an assembly that contains the tasks executed for that run.

A small set of helper endpoints supports the blueprint authoring experience:

• Builder Helpers — smartnames, factory-side store access, factory mail templates, and the catalogue of scopes a blueprint's UCS (User Calling Steps) can request.

Scopes

Scope	Reach
blueprints:read	Reading blueprints and tickets.
blueprints:write	Creating/updating/deleting blueprints, uploading thumbnails.
assemblies:read	Reading assembly histories, tasks, and the factory's mail template view.
assemblies:write	Deleting assemblies and tasks, plus access to builder helpers (smartnames, factory store, UCS scopes).

See also

• Mail Templates — the canonical mail-template management endpoints (the factory exposes a read-only view of the same data).
• Conventions — pagination, filtering, and error patterns used by every factory endpoint.
• Scopes › Blueprints & Factory Assemblies — the canonical scope list.