Skip to content

Product

MOD-03 · Runtimes and accounts

Behavior and limits for runtimes and accounts, based on the reviewed product catalog.

FEAT-008 · Account rotation

Exhausted quota can follow rotation or fallback policy. Short rate limits wait in the queue; the operation does not copy credentials between profiles.

An exhausted profile stays unavailable until its quota resets; the next allowed dispatch or retry skips it, and the switch records runtime_profile_rotated. ork accounts esgotamentos measures exhaustions over a period (--desde 7d).

FEAT-009 · Reason-based retry

The typed cause determines the action. Attempt limits escalate in every mode; cost.violation never receives automatic retry.

FEAT-010 · Session observation

Sensors query the runtime to confirm state and completion. Adopting a session does not execute its prompt; a success report does not complete the phase.

FEAT-037 · Per-dispatch profile and sessions of each account

ork phase run --perfil <id> dispatches the phase on the chosen account, or refuses with a typed reason (runtime.profile-invalid, runtime.quota-exhausted, runtime.auth-missing) without switching profiles on its own. With runtime_profiles.distribuir: carga, ork picks the account with the fewest live sessions on this machine; without the key, the store order applies.

ork sessions shows the sessions of every account, with a PERFIL column (the id, never the account directory), and marks a session without a live process as a ghost. ork sessions limpar-fantasmas releases that session from ork, with a ledger record, without stopping anything in the runtime. Released in version 0.5.2; the catalog still lists the page as in development.

ork phase run <thread> GO --prompt "<texto>" --perfil <id>
ork sessions
ork sessions limpar-fantasmas --dry-run

FEAT-022 · Auditing and debt

Findings have reproducible claims and historical state. Deferral or dismissal requires a record; an auditor’s report is not itself evidence.