docs

Versioning & changelog

Current skill and protocol compatibility, dated changes, deprecations, and how to report an issue.

View as Markdown
On this page

Semel’s protocol is at 1.1 (supported major: 1). Compatibility is based on protocol major; additive minor changes appear through live tools/list. The exact current skill version, hash, signed statement, and immutable artifact URL are published by the production manifest.

Current compatibility

  • Protocol: 1.1 (supported major: 1). A skill outside the supported major fails with PROTOCOL_VERSION_UNSUPPORTED; revoked bytes must not mutate.
  • Skill: semel-bootstrap. Read https://mcp.semel.ai/.well-known/semel-skill.json for its current version, protocol range, SHA-256, immutable download URL, and Ed25519 release signature.
  • Clients: Claude Code and Codex are launch-supported. Generic MCP clients and OpenClaw remain experimental until their full install/auth/reload traces pass.

Changes

  • 2026-09 — Agent activation contract: production-only public URLs, exact Claude Code and Codex commands, readiness classification, and all fourteen schema-validated recipes.
  • 2026-09 — Signed skill distribution: inspectable Node.js installer at https://docs.semel.ai/downloads/semel-install.mjs, content-addressed artifacts, pinned Ed25519 verification, atomic activation, and rollback.
  • 2026-09 — Rich operation discovery: nested input/output schemas, conditional scopes, risk and confirmation metadata, typed control blocks, and representative response fixtures generated from the live registry.
  • 2026-09 — Local review execution: grant request, claim, pinned-skill fetch, heartbeat/checkpoint, question, release/submit, synchronization, and certificate flows are represented in the MCP catalog.

Deprecations

brief_export_markdown is deprecated compatibility output. It does not create a verified implementation handoff and must not be used as fallback after brief_export_package fails. The live tool description points callers to brief_export_package.

Support & reporting

Found something wrong or missing? Reach the team through your Semel workspace. Include the protocol version, skill version/hash, client and version, stable error code, current state, and safe reproduction steps. Never attach tokens, OAuth parameters, customer brief content, repository source, or chain-of-thought. See Troubleshooting.