Skip to content

Product

MOD-04 · Human attention

Behavior and limits for human attention, based on the reviewed product catalog.

FEAT-011 · Layered human attention

ork.hitl-curto/v1 presents a short question, blocker, options, recommendation and response instructions. Unambiguous owner text can select an action; ambiguity asks for clarification. Standalone words require an open listening window and a single pending request, and cannot authorize irreversible actions. Codes remain stable when reopening the same context.

FEAT-012 · Accountable decisions

Delegated choices record rationale, reversal and the cost of change. The owner can revisit them; irreversible acts follow required authorization.

FEAT-013 · Owner timezone

Presentation uses owner.timezone. The ledger, hashes and receipts retain UTC ISO; an invalid timezone raises a warning.

FEAT-014 · Monitor, board and pulse

State comes from threads, the ledger and queues. ork roadmap status is read-only: it groups the report in the owner’s timezone, marks pending decisions with #HITL and shows next steps. The orchestrator handles technical blockers; ended sessions are not presented as able to receive a response.

Work stalled with the conductor after delivery, for more than 30 minutes, appears as one line per thread in the pulse, with the next step and outside “Waiting for you”: an unpushed branch, a branch without a PR, a green PR not merged, or a merge not recorded. ork roadmap status states the real delivery state of each item’s thread and, with a shared factory, flags a machine with no heartbeat for more than 3 hours.

In version 0.6.10, when a thread that does not drive a roadmap item is waiting for the owner (a gate, a session or a dispatch blocker, as in ork pulse), the closing part of ork roadmap status that lists what needs you gains a line with how many threads outside the roadmap are waiting for you (ork pulse), and --json gains the optional, additive foraDoRoadmap field. Without such a thread, the output stays the same byte for byte.

ork pulse and ork roadmap status include the time blocked by conduction HITL (hitlDeConducao): the open questions, with how long each one has been blocking the thread, in the owner’s timezone, and the median over the last 7 days against the 5-minute target. The summary gains a line only above the target, without becoming news that breaks the cadence.

In #Auto, a CHECK finished without a verdict stays with the conductor, which dispatches the CHECK phase again; outside #Auto, it goes to the owner. A forge whose PRs cannot be read, such as GitLab, a local remote or a host without a gh login, raises the prs.sem-leitura warning once per remote, and the next step says to check the PR on the forge.

ork roadmap status

FEAT-015 · MASTER and conduction index

MASTER records a postmortem and a ledger-derived index. ork master pedir requests a score and reason through authenticated Telegram. The record includes sender, channel, message and proof hash; the agent cannot sign for the owner. A later human score replaces acceptance by omission without erasing history. The MCP score dialog remains unavailable.

ork master <thread> --aceitar-omissao accepts by default only the delivery of the given thread; without a thread, the command accepts every delivered thread in the project, including other workstreams, and an agent running it with more than one gets the master.omissao-sem-thread warning. --dry-run lists what it would close without recording anything. A human score requires --por with a person’s name.

ork master pedir <thread> --formato telegram
ork master <thread> --aceitar-omissao --dry-run