motif64
Log in

Capsule format

A capsule is a folder:

my-capsule/
  capsule.toml   manifest: kinds, hardware, runtime, network needs, params, secrets
  Dockerfile     builds the server (or set an image in capsule.toml)
  start.sh       starts it
  AGENT.md       how an agent should use it
  human/         the page for humans
  ...            whatever the server needs

The id

A capsule has no name. Its id is the SHA-256 git tree hash of its folder (.git and __pycache__ ignored), written m64_<64 hex>. The same files always give the same id, and any change gives a new one. m64 hash <folder> prints it.

Pages and lists show m64_ plus the first 12 hex characters, e.g. m64_3f9a0c41be72. Any unique prefix of at least 12 hex works wherever an id is expected.

capsule.toml

schema = "m64/capsule@1"
description = "Kromoss + DMD2 8-step LoRA text-to-image on GB10 (diffusers)."
kinds = ["image.generate"]
authors = ["dh7"]
license = "apache-2.0"

[hardware]
platform = "linux-aarch64"
gpu = "NVIDIA GB10"
gpu_count = 1
vram_gb = 40
disk_gb = 40

[network]
needs = []
why = ""
  • kinds is the API the capsule serves. Categories, used for browsing, are set on motif64.sh, not here.
  • hardware, secrets.required and network.needs become the prerequisites shown on the capsule's page.
  • authors is shown as credits, unverified: the publisher on motif64.sh is the account that pushed it.
  • No tags, category, model or engine in the manifest. They are site metadata, editable at any time without changing the id.

Lineage

m64 fork writes parent = "m64_<64 hex>": the capsule you copied. It is part of the hash, so it can't change after publication.

On push, motif64.sh also compares the files with every published capsule and records the one sharing the most (at least half of the new capsule's files) as "derived from", whatever parent says. A declared parent that shares few files shows as such: "claims m64_..., 3% shared files".

Claiming to replace a capsule

A capsule can claim to replace others. Each claim says why it is better and what was changed:

[[replaces]]
id      = "m64_<64 hex>"
why     = "2x faster on Basalt at 32k context"
changes = "engine vLLM -> Basalt; same model and weights; start.sh flags for 32k"

The replaced capsule's page then lists it under "capsules claim to replace this one", and anyone can compare the changes text with the real file diff. A claim is shown with who made it; motif64 endorses none.

m64 lint checks a capsule against the format before you push it.