Product
MOD-06 · Host integration
Behavior and limits for host integration, based on the reviewed product catalog.
FEAT-020 · MCP and adapters
Installation produces receipts and hashes. The host forwards operations; mode interpretation and gate rules remain in the core.
FEAT-021 · Authenticated ingress
Telegram ingress validates the authenticated update and HMAC proof before recording a response. It accepts codes, numbered answers and unambiguous free text under the core’s conditions. The listening window only routes standalone words; it is not identity proof. Ambiguity never approves a request, and agent-fabricated envelopes are rejected.
FEAT-030 · Explicit target project
Every command and every ork_* tool reads the requested project, never the gateway directory’s project, and the answer states which project it read and what it did not read. OpenClaw and Hermes declare ORK_PROJETO_EXPLICITO=1: without a project and with more than one known, they return the choice. In a host, --projeto accepts only a name; MCP stays pinned to its installation and refuses another project with projeto.fora-do-servidor. The catalog lists the page as proposed.
FEAT-034 · Experience pack
Language, timezone and depth preferences shape the orchestration conversation, with opt-out and restoration of instruction files. Claude Code and Codex receive project blocks, and Hermes receives references through its existing skill; OpenClaw still lacks this distribution. MCP reservation and factory queries neither reserve nor publish. Opting out does not disable policies or gates, and no preference changes HITL HMAC provenance. The catalog lists the page as in development.