# RBEK CLI — Developer Adoption Path

This document defines the shortest certified path from discovery to a successful first RBEK execution.

## 1. Install

```bash
curl -fsSL https://releases.rbekplatform.com/cli/stable/install.sh | bash
```

## 2. Confirm the CLI

```bash
rbek version
rbek doctor
```

The stable public version is `0.1.3`.

`rbek` is the primary command. `rbek-cli` remains available as a compatibility command.

## 3. Create a project

```bash
mkdir hello-rbek
cd hello-rbek
rbek init
```

## 4. Diagnose the project

```bash
rbek doctor
```

## 5. Execute the first workflow

```bash
rbek run
```

Expected output includes:

```text
Hello from RBEK
```

## 6. Understand the first-run boundary

The certified first workflow is local and deterministic. It is designed to prove installation, project discovery, workflow loading, execution, and output without requiring credentials, a database, an external API, or a provider connection.

## 7. Useful public resources

- Commercial entrypoint: `https://releases.rbekplatform.com/cli/stable/`
- Start Here: `https://releases.rbekplatform.com/cli/stable/START-HERE.md`
- Quickstart: `https://releases.rbekplatform.com/cli/stable/QUICKSTART.md`
- Developer experience manifest: `https://releases.rbekplatform.com/cli/stable/developer-experience.json`
- Release metadata: `https://releases.rbekplatform.com/cli/stable/versions/0.1.3/release.json`