Shimpz
One reviewed contract

Author source; let Shimpz generate delivery

Assistant Spec v1 has one small manifest and one Python file per Action. Contracts, locks, Dockerfiles, health endpoints, and runtime adapters are generated during platform pre-build.

Authored source

Every decision has one home

icon.png
One static, high-resolution identity image covered by the immutable source digest.
shimpz.toml
Version, identity, Genesis, exact outbound hosts, and optional OAuth Integration scopes.
actions/*.py
Exactly one decorated async def run per direct file. Human request copy in these files and in lib/ is English shimpz.text catalog copy.
pyproject.toml
Python version and direct dependencies, including the released shimpz SDK.
Platform pre-build

Generated artifacts never pollute source

  1. The SDK validates the project and every direct Action file.
  2. Before any Assistant code is imported, it extracts the static English message catalog.
  3. It derives the canonical shimpz.contract.json, which carries that catalog.
  4. The platform resolves and locks dependencies and creates the runtime/container files.
  5. The platform translates new messages and copies the language pack read-only to /opt/shimpz/shimpz.pack.json after every stage that runs Assistant code.
  6. The Controller admits only the reviewed immutable build.

The catalog extraction and language pack require SDK 0.7.1 and CLI 0.9.0 or newer. A Local snapshot's pack is made by shimpz assistant stage on your machine.

Runtime

Invocation contains input and bounded replay, never a credential

The Controller validates Action input and invokes /usr/local/bin/shimpz-action <action-id>. The invocation is the first input line and contains input and the ids of the Stored Inputs Team holds; a replay also contains completed human-request responses. The Action asks Team for each provider call with ctx.fetch, one line out and one reply line in, and Team adds every declared credential. An Action returns one validated JSON object as its last output line.

Published contract

Source packages have one byte-level authority

shimpz assistant publish creates an uncompressed canonical POSIX ustar archive. Its exact allowlist, limits, normalized metadata, golden vectors, and verifier are published together:

When the exact source is ready, follow Publish an Assistant to authorize the release and verify its installable artifact.

Developers authority commit
f602133860482241f8030e25a11e3a0f0dfe259d
Contract tree
614d308e27d248ce5961327beb9789ae4b969ec6