Docs / print
Print (FGF)
Rig names pellet / FGF machine meaning as rig.print.*. G-code files and slicer processes stay host mappings at the boundary - same rule as IDML in idml.md.
Not these
| Nearby id | Why it is different |
|---|---|
Envelope pdfX / outputCondition / trapped |
Press / PDF/X job - document.md |
rig.layout.page / frame |
Print spread (pages, type). Not a bed |
rig.dev.machine |
VM / CI recipe - dev.md |
rig.art.material |
CDWA medium / technique |
rig.render.material |
Shader |
rigGCode CPaths |
Plotter toolpaths. FGF G-code is asset_ref / rig.media.code language gcode |
rig.cad.* |
Authored solid. The part to slice is mesh / CAD + transform |
Map
| Idea | Rig |
|---|---|
| Printer envelope | rig.print.machine |
| Pellet / filament grade | rig.print.material |
| Slice knobs | rig.print.process |
| Hot-stack sag | rig.print.compression |
| One job | rig.print.job input / output names asset entities |
| Part pose | rig.spatial.transform |
| Mesh / STEP / 3MF / G-code file | rig.media.asset_ref |
Do not store slicer executables, last-slice ok/error, or host paths on rig.print.job.
Example: examples/print-fgf.json.