Skip to content

Releases: Lightmaze/agent-image

Agent Image v0.1.0-alpha.2

Pre-release

Choose a tag to compare

@Lightmaze Lightmaze released this 08 Sep 01:40

Agent Image v0.1.0-alpha.2

Date: 2026-09-03

Channel: public technical preview / GitHub prerelease

This is the first public Agent Image release. It delivers a complete operator
path for a bounded but real claim: install the CLI, verify and inspect a public
developed-state artifact, restore it into a fresh Hermes profile, and use the
restored Agent.

The release intentionally remains alpha. It does not claim that the current
archive captures an isolated execution and cognitive world, or that its image
digest is already a complete computational-author identity. Those broader
vHarness, object-graph, resume, fork, replay, and reproduce semantics will be
introduced through forward protocol versions rather than retroactively changing
this immutable release.

Included experience

The public procurement-negotiator-v1.aimg contains seven explicitly public
layers derived only from synthetic procurement practice. A fresh-restored Agent
scored 1.000000 on 24 new synthetic decisions, compared with 0.481521 for a
fresh Agent using the same deepseek-v4-flash model and parameters. Neither arm
revealed the private limit. This is bounded same-harness evidence, not real-world
procurement competence or cross-harness P3.

Assets

  • agent_image-0.1.0a2-py3-none-any.whl
  • agent_image-0.1.0a2.tar.gz
  • procurement-negotiator-v1.aimg
  • registry-v0.1.json
  • v0.1.0-alpha.2.md
  • v0.1.0-alpha.2.sha256

Verified scope

  • Deterministic build, inspect, verify, redact, and diff.
  • Native P1 restore for pinned Hermes, OpenClaw, DSH, and the scoped vHarness
    reference Guest.
  • Dry-run-first Hermes to OpenClaw semantic P2 migration with explicit loss.
  • Private-by-default state, structured secret rejection, and no-overwrite
    restore/migration behavior.
  • A third-party adapter entry point proven without a Core schema fork.
  • Fresh wheel and source-distribution installation without PYTHONPATH.

The release-file SHA-256 and the alpha protocol's canonical layer payload-root
digest are deliberately separate identities. See the README, capability matrix,
and limitations for the exact observed platforms and claim boundaries.