Factory Master
Understand the limited installed Factory Master preview for workspace-local production systems without implying public publishing or commerce.
Last reviewed
Availability and public boundary
Factory Master is Coming Soon for public access and is currently a limited installed preview. The canonical product registry keeps it behind a local pilot gate. Public production, publishing, spending, identity linkage, and royalties are not open.
Factory Master is designed to organize repeatable, workspace-local production systems. A factory can represent a structured way to create, inspect, stage, or schedule a recurring output. The preview communicates that direction without turning a local record into a public listing, paid service, or approved automation.
The gate defaults locked. An explicit local marker and the corresponding founder-only switch are both required for the current pilot. Seeing documentation for the preview does not grant access or change that gate.
Factory index and discovery
The Factory index is the starting view. It can show source-backed factories, counts, ownership, and operational state. Search accepts factory names, owners, or state-related terms. Filters narrow the list to all factories, running factories, or factories that need attention.
Each row should answer:
- What production system is this?
- Who owns it?
- Is it running, stopped, or asking for attention?
- What can the operator safely inspect next?
If search or filters return no match, the page offers a clear-filter recovery action. An empty result does not delete the factory or prove that no source record exists.
Detail view and workspace-local controls
Opening a factory moves from the index into a detail view. The detail header includes the factory name, description, owner, operating mode, telemetry, and a local engine control. Tabs and the main stage provide the factory-specific workflow or records.
Start, pause, and stop apply to the selected factory only. They must not be interpreted as global workspace controls. The visible summary explains whether records are moving, while the inspection stage provides the evidence needed to understand the current line.
Because this is a limited preview, use the controls only inside the approved installed pilot. Do not infer that a stopped factory has cancelled external work, or that a running label means content has been published.
What the preview does not authorize
Factory Master does not authorize public publication, marketplace submission, paid promotion, outreach, account creation, or spending. It also does not create royalty rights or attach a production line to a public identity.
A source-backed factory record is workspace evidence. A published deliverable is a separate outcome. External actions still require their own explicit approval and proof.
The public website does not expose Factory Master as a browser application. The canonical surface is the installed Pulse extension shell. Historical browser prototypes are not evidence for current Factory behavior.
When Factory looks wrong
If Factory remains locked, confirm that you are using the approved installed pilot and do not change the local access marker unless the founder has authorized that specific pilot.
If the index is empty, clear search and filters, then confirm that the current workspace has valid factory sources. If a factory displays the wrong owner or state, inspect its source record before using an engine control.
If a control changes visually without a matching workspace receipt, treat the action as unverified. Preserve the visible state, record the factory name and local status, and use the review path without publishing or spending.