Mobpack

For the full guide, see Mobpack.

This page is intentionally deployment-focused and CLI-heavy. Use Examples: Mobs first if you want to understand the multi-agent runtime before packaging it, and continue to Examples: WASM if your next step is browser delivery.

Define the portable boundary

A source directory needs manifest.toml and definition.json. Optional archive sections are skills/, hooks/, mcp/, config/, adaptive/, and schemas/.

manifest.toml

surfaces = ["cli", "rpc"]

[mobpack]
name = "release-triage"
version = "1.0.0"

[requires]
capabilities = ["comms"]

[models]
default = "gpt-5.5"

definition.json

{
  "id": "release-triage",
  "orchestrator": {"profile": "lead"},
  "profiles": {
    "lead": {
      "model": "gpt-5.5",
      "external_addressable": true,
      "tools": {"comms": true}
    },
    "reviewer": {
      "model": "gpt-5.4-mini",
      "tools": {"comms": true}
    }
  },
  "flows": {
    "main": {
      "steps": {
        "triage": {
          "role": "lead",
          "message": "Triage severity {{ params.severity }}: {{ params.prompt }}"
        }
      }
    }
  }
}

To validate callable parameters, optionally add schemas/main-input.json:

schemas/main-input.json

{
  "type": "object",
  "properties": {
    "prompt": {"type": "string"},
    "severity": {"enum": ["low", "medium", "high", "critical"]}
  },
  "required": ["prompt", "severity"],
  "additionalProperties": false
}

If the pack needs defaults, keep config/defaults.toml inside the typed allow-list:

config/defaults.toml

max_tokens = 4096

[budget]
max_tokens = 200000
max_duration_secs = 900
max_tool_calls = 200

Arbitrary [agent], [tools], [shell], [realm], [comms], provider-key, and storage configuration is rejected. Mobpacks carry runtime intent and assets, not credentials or host infrastructure.

Pack a mob directory

Bundle the directory into one deterministic .mobpack artifact:

rkat mob pack ./mobs/release-triage -o ./dist/release-triage.mobpack

Sign a pack

Attach an Ed25519 signature at pack time for trust verification on deploy.

rkat mob pack ./mobs/release-triage \
  -o ./dist/release-triage.mobpack \
  --sign ./keys/release.key \
  --signer-id team@example.com

Signing embeds the public key but does not install the signer as trusted. The local commands below therefore use permissive mode; use strict only after installing that signer in the verifier’s trust configuration.

Inspect a pack

View the contents, metadata, and signature status of a .mobpack without deploying.

rkat mob inspect ./dist/release-triage.mobpack

Validate a pack

Check structural integrity, schema conformance, and signature validity.

rkat mob validate ./dist/release-triage.mobpack --trust-policy permissive

Validation checks archive safety and digest, typed surface and capability requirements, definition and skill references, typed deploy defaults, adaptive assets, and signature policy before any mob is created.

Deploy a pack with an objective

mob deploy runs the packaged team against one prompt. CLI model and budget flags remain host-owned overrides:

rkat mob deploy ./dist/release-triage.mobpack \
  "triage latest regressions" \
  --max-duration 15m \
  --trust-policy permissive

Run a pack

Invoke a .mobpack as a typed callable run. When schemas/main-input.json is present, parameters are validated before the flow starts. --prompt is sugar for --param prompt=<text>.

rkat mob run ./dist/release-triage.mobpack \
  --flow main \
  --prompt "triage latest regressions" \
  --param severity='"high"' \
  --trust-policy permissive \
  --json

The mob and run records use durable realm custody. Use --detach on a callable flow to get a run id, then inspect or attach to that run resource:

rkat mob run ./dist/release-triage.mobpack \
  --flow main \
  --prompt "triage latest regressions" \
  --param severity='"high"' \
  --detach \
  --trust-policy permissive
rkat mob runs release-triage --json
rkat mob status release-triage <RUN_ID> --json
rkat mob attach release-triage <RUN_ID> --json

--detach does not move execution into a daemon. The flow runs only while the CLI process lives; after it exits, the next hydration marks unfinished work canceled because execution custody was lost. The durable resource is still available for status and logs.

Package an adaptive flow

Adaptive packs add [adaptive] manifest metadata plus adaptive/policies.toml, adaptive/flowmaster.prompt.md, and a schemas/registry.json that points to required bundled schemas. Packing stamps the adaptive_flow capability and regenerates adaptive/layer-decision.schema.json; do not hand-maintain that generated schema. Validation fails on a policy digest mismatch, incomplete policy limits, missing schemas, or a target runtime without the adaptive capability.

Trust policies

Policy	Unsigned packs	Unknown signers	Invalid signatures
`permissive`	Allowed (warns)	Allowed (warns)	Rejected
`strict`	Rejected	Rejected	Rejected

For signed packs, both policies reject digest and signer-key mismatches. Permissive relaxes signer enrollment; it does not disable integrity verification. Trust policy resolution order:

CLI flag: --trust-policy permissive
Environment variable: RKAT_TRUST_POLICY=permissive
Config file: trust.policy field
Default: strict (fail closed)

Next step

After packaging and deploy flows, continue with Examples: WASM for the browser-target delivery path.

Getting started

Concepts

Guides: Models And Hosting

Guides: Runtime Behavior

Guides: Orchestration

Examples: Foundations

Examples: Capabilities

Examples: Orchestration And Deployment

Define the portable boundary

Pack a mob directory

Sign a pack

Inspect a pack

Validate a pack

Deploy a pack with an objective

Run a pack

Package an adaptive flow

Trust policies

Next step

​Define the portable boundary

​Pack a mob directory

​Sign a pack

​Inspect a pack

​Validate a pack

​Deploy a pack with an objective

​Run a pack

​Package an adaptive flow

​Trust policies

​Next step

Define the portable boundary

Pack a mob directory

Sign a pack

Inspect a pack

Validate a pack

Deploy a pack with an objective

Run a pack

Package an adaptive flow

Trust policies

Next step