Write a template

A template is a signed manifest that tells the agent which images to run, which settings to ask for, and how to expose the result. You write it against the spec, submit it on the registry site, and it gets reviewed before it shows up in the catalogue.

The spec

The manifest format is obacht.dev/v2, currently version 2.9. The spec and the authoring guide (docs/AUTHORING.md) are on GitHub at obacht-dev/obacht-template-spec. minSpecVersion is mandatory.

Three runtimes exist. container ("Single") runs one image. compose ("Bundle") runs a Compose file under a strict allowlist: no build, no privileged, no host ports, no host bind mounts, no cap_add or devices. x-obacht-data: true on a volume is accepted but has no effect yet. Uninstalling deletes every volume of the bundle. system ("System") installs onto the host itself, Raspberry Pi only, and needs Power Mode.

Write imageDigests: {} in the manifest. Registry CI resolves and pins the digests, and the agent refuses a manifest with unpinned images. Every publish bumps the semver. Images must exist for linux/arm64 (Pi, Mac) and linux/amd64 (Linux PC) to run everywhere.

Submit it

Sign in on registry.obacht.dev/contribute. The form asks for Template name and Repository URL (both required), Proposed ID, Manifest URL, Description, Suggested category, Runs on, Tags, Contact email, and Notes for the reviewer. Submissions are reviewed by hand. Accepted manifests are signed by the registry (obacht-registry-prod-1) and get a trust level: official, community or unverified.

Money

Where an upstream project has a payout channel, a template fee goes to that project. No payout channel, no fee, and the template is free. How that works is on obacht.dev/open-source.