Assemblies

The execution history of a Factory workflow. Every time a Blueprint runs (typically in response to a Ticket), one assembly record is produced. The assembly captures the run's start/finish times, the resolved input values, the per-step outcomes (Tasks), and any final artifacts.

Assemblies are read-mostly: they are produced by the runtime, not directly authored. The only write operation is deletion — useful for trimming history that is no longer needed.

Scopes

Scope	Reach
`assemblies:read`	Listing, reading, viewing filters.
`assemblies:write`	Deleting assemblies.

Endpoints

List Assemblies

GET /api/factory/history/

Returns a page of assembly records.

Required scope: assemblies:read · also accepts API key

Query parameters — standard pagination set; see Conventions › Pagination. Defaults: sort_by=started, sort_order=desc, hydrate=true.

Response 200 — AssemblyInDbCursorPage

Get Assembly Filter Metadata

GET /api/factory/history/filters

Returns filter/operator/sort options for List Assemblies.

Required scope: assemblies:read

Response 200 — open metadata object.

Get Assembly by ID

GET /api/factory/history/{id}

Returns a single assembly record, including its full step outcomes.

Required scope: assemblies:read · also accepts API key

Path parameters

Name	Type	Required	Description
`id`	string	yes	Assembly ID.

Response 200 — AssemblyRead

Delete Assembly by ID

DELETE /api/factory/history/{id}

Removes the assembly from history. Useful for trimming completed runs whose detail is no longer needed; does not affect the underlying Blueprint.

Required scope: assemblies:write

Path parameters

Name	Type	Required	Description
`id`	string	yes	Assembly ID.

Response 204 — empty.

Assemblies ​

Scopes ​

Endpoints ​

List Assemblies ​

Get Assembly Filter Metadata ​

Get Assembly by ID ​

Delete Assembly by ID ​

See also ​