@mrkt_frwd/job

A scene compiler for Blender. You write one small JSON file; it produces the .blend, the .glb, the stills, and a checksum manifest that says what it made.

npx @mrkt_frwd/job

That prints the manual. There is nothing to install and nothing to clone.

What it is for

Getting a 3D scene out of an agent without the agent writing Blender Python. A prompt writes a job.json — a declarative description of blocks, materials, cameras and lights — and Job turns that into artifacts. The scene file is the source of truth, so it can be diffed, reviewed, and re-run.

The claim, and the evidence for it

1,290 bytes in. Everything else derived:

| artifact | size | digest | |---|---|---| | collar-01.glb | 862 KB | 5e507bc0 — reproducible | | collar-01.blend | 1.3 MB | per-run | | hero.png · front.png · side.png | 504 / 542 / 417 KB | per-run | | manifest.json | 851 B | records all six |

Try it without installing Blender — the reference .glb ships in the package:

npx @mrkt_frwd/job examples pull collar-01 --output-dir ./out
npx @mrkt_frwd/job check ./out/job.json

The .glb is the one digest that reproduces: export it on another machine and it is still 5e507bc0. The .blend and the stills embed per-run state, so the manifest records what your export actually produced instead of claiming they are fixed. Saying which of the two is reproducible is the point — a checksum you cannot match is worse than no checksum.

What it refuses to do

• An unchecked Job does not run. check validates against schema job/1 first.
• It will not guess a material or a camera it does not have. Unknown entries are an error, not a silent default. A scene that quietly substituted something is harder to debug than one that stopped.
• Export never rewrites the Job it read. The checksums you pulled still describe the file on disk afterwards.

Commands

job                      print getting-started
job docs ls|cat|find     the whole manual, offline
job examples pull <id>   a verified Job with its checksums
job check <job.json>     validate against schema job/1
job export <job.json>    drive Blender, emit artifacts + manifest
job mcp --output-dir <d> local MCP server (writes only with --output-dir)

Read-only hosted MCP: https://joeasare.com/api/job/mcp

Requirements

Node 18+. Blender is needed for export only — docs, examples and check run on a bare Node install.

MIT © Joe Asare. Built at Joe Asare Studio, where it compiles the scenes the rest of the work is made from.