Product
MOD-01 · Thread conduction
Behavior and limits for thread conduction, based on the reviewed product catalog.
FEAT-001 · Threads and phases
Each request has its own thread, state and ledger. The default list shows open threads; the full cycle retains six phases.
With worktree.por_thread: true, which ork init writes, ork thread new creates the thread’s worktree and branch without a flag; --sem-worktree creates the thread without them, and --dry-run shows the worktree that would be created. With the key false or absent, a worktree is only created with --worktree auto.
FEAT-002 · Conduction modes
#Classic, #Maestro and #Auto change the HITL points. #Fast runs only GO and does not authorize push or public contract changes.
FEAT-003 · Phase dispatch
The core assembles the prompt and records its hash and effective runtime, model and effort. Failures follow configured fallback; an agent cannot choose another identity on its own.
FEAT-023 · Project onboarding
The interview records public answers and credential references. Publishing to memory is optional; secret values stay out of the interview.
FEAT-025 · Portfolio catalog
Products, projects and initiatives have explicit parents and scope. Missing parents and incompatible scope are rejected.
FEAT-026 · Cross-machine reservations
Reservations coordinate who takes an item through an atomic remote write. Conflicts identify the responsible machine; authorized network access is required. Closing a thread releases its reservation or passes it to another open thread on the same item; orphaned reservations are flagged and released with --soltar-orfas. ork roadmap feat reserves the next FEAT number across machines, and a reserved number is never reused.
FEAT-027 · Shared factory
Each machine that has joined the factory (ork fabrica entrar, or ORK_FABRICA_COMPARTILHADA=1) publishes its snapshot to a dedicated state branch; fabrica.compartilhada: true in the manifest is only the team’s request, which ork doctor flags. Offline reads use the last copy with a warning; they do not assume current data. The snapshot shows each thread’s runtime, model and effort from its last dispatch; a thread without a dispatch shows no runtime rather than an invented one.
FEAT-029 · Multichannel conduction
Channels share core authority. A second concurrent execution in the same worktree is rejected with the current conductor identified.
Leases and the collision queue live in the project’s canonical state: the root and the worktrees contend for the same files.
FEAT-031 · Orkastery Network
Each machine publishes a secret-free snapshot to a private repository of the person on the forge, and ork network status shows all of them, from any directory, with the source and the gaps. Membership belongs to the machine, explicit or inherited from ork fabrica entrar; ork network sair overrides the inheritance, and the project manifest enrolls no one. Publishing requires a private home, checked before each publication; a public repository is refused with rede.repositorio-publico.
The snapshot is an allowlist: a field that looks like a secret refuses the publication, and a project that looks like a secret is left out with a warning. Each machine writes only its own snapshot; a name taken by another installation becomes rede.nome-em-uso, and --forcar takes it with a record in the commit. A gap never becomes an empty list. Released in version 0.5.3; the catalog still lists the page as in development.
Since version 0.6.2, the snapshot publishes only the generic machine alias, also in the legacy hostname field, and without an alias joining refuses with rede.maquina-generica; the real hostname is never published.
ork network entrar --maquina maquina-a
ork network status --jsonFEAT-032 · Network roadmap
From any directory, ork network roadmap combines the remote base roadmap, reservations and each machine’s threads, with the source and time of every part. Without a clone, it only queries the forge through the already authenticated CLI; anything not read appears as a typed gap, never as empty. In hosts, ork_network_roadmap passes this result through unchanged. Current: released in version 0.5.0. Since version 0.5.3, slice 3 also reads the per-person network: the Network by person section shows the home and each machine; a machine seen only in the network appears with unread threads and the maquina.sem-fabrica gap, never with zero threads. ork_network_status reaches OpenClaw, Hermes and MCP, and gh and glab are found outside the short PATH of the gateway and cron.