Start with your first cycle

Install and check

Use Node.js 20 or later, Git and a working repository. The package is @orkastery/cli; its executable is ork. The core contains no AI model. Your configured agent runtime executes the phases. @orkastery/cli 0.5.0.

npm install -g @orkastery/cli
ork doctor
ork demo

Prepare the project

Run init at the root of your repository. The manifest defines checks, conduction mode and runtime integration. Then complete onboarding. Record credential variable names only; keep their values in the protected environment.

The onboarding maestro stage also offers conversation preferences: language, timezone and depth, or opt-out. Check the effective values with ork experiencia show --json; the orchestration experience guide explains installation in each host.

ork init --name "meu-produto" --abbrev prd
ork onboarding
ork experiencia show --json
ork doctor

Create a thread

A thread brings together the goal, plan, implementation, verification and delivery. Start with a small request and an observable criterion. Use the returned ID in subsequent commands; the example ID is not a real receipt.

ork thread new "corrigir o filtro de data" --modo classic
ork thread status <thread>
ork phase list <thread>

Confirm before proceeding

A blocked doctor prevents a new dispatch. Resolve the reported cause and rerun it. The demo is a local exercise in a claim that fails and then passes; it does not establish that your project is ready for publication.

Try it without an account

ork demo runs offline without an account: it shows a false claim failing and its correction passing. The hermetic core CI suite requires no agent runtime. Running phases uses the project’s configured runtime and profile.

ork demo
ork --version