Skip to content

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.

Since version 0.6.2, the same core serves Claude Code, Codex and Grok Build over MCP, each host with the enumerated grants of the tools it uses. Verify over MCP is asynchronous: ork_verify starts the round and returns a rodadaId at once, and ork_verify_status follows queue, lane and verdict, under the ork.verify-mcp/v1 contract.

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. Current: released in version 0.5.0.

In version 0.6.10, slice 2 completes the honest answer. A command that does not build its own header ends with the “Projeto consultado” line on stderr, once per command, when the reader cannot tell which project was read (in a host, or with the project outside the current directory); on failure, the line comes before the error. A dispatched session (phase, retry and ork audit run) and the ork fabrica publicar child process read the project from their own cwd: the dispatch carries an empty ORK_PROJETO and ORK_PROJETO_EXPLICITO=0. ork roadmap reservas without the remote, or with a silent remote and no local copy, says nothing was read from ork/roadmap-reservas, never that no item is reserved. In the answer, the remote carries no credential, query or fragment, and the local path shows ~ in place of the account folder.

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. Current: released in version 0.5.0.