Reference
Technical reference for the public OpenFactory platform. The console and API responses are the source of truth for the state of a particular build.
Quick links
| Reference | Description |
|---|---|
| MCP integration | Connect an MCP client to OpenFactory |
| Recipe schema | Canonical BuildRecipe fields |
| Assertion types | Executable VM-test assertions |
| ServiceNow integration | Optional, disabled-by-default ITSM hooks |
Build records have separate outcomes
Do not infer verification from the image-build status alone. A build record tracks at least three distinct concerns:
| Concern | Typical values | Meaning |
|---|---|---|
| Image build | queued, planning, configured, building, finalizing, completed/built, failed | Whether image production reached a terminal result |
| Tests | not_run, running, passed, failed, error, or skipped | Whether the attached verification run executed and what it found |
| Certification | certified, uncertified, repairing, or another explicit gate state | Whether the artifact met the current certification contract |
A completed image with failed, errored, skipped, or absent tests is not a certified image. Use all three fields when automating promotion or download decisions.
Build outputs
Outputs depend on the build target and on which stages completed. A record may provide an ISO or disk image, the normalized recipe, build logs, and test evidence. Treat an item as available only when the build response supplies its artifact metadata and the download endpoint succeeds.
Zone 2 snapshots in VM management capture the governed persistent overlay. They are not full libvirt memory-and-disk snapshots and are not build artifacts.
Base images
Selectable versions change as upstream sources and OpenFactory adapters change. Use the console’s current base-image picker or the validated recipe response, not a copied version list, when creating automation. See Base images for selection guidance and limitations.
Support
- Console: console.openfactory.tech
- Email: support@openfactory.tech