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.
FEAT-002 · Conduction modes
#Classic, #Maestro and #Auto change pauses. #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 publishes its snapshot to a dedicated state branch. 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.
FEAT-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. The catalog lists the page as in development.