# Marketplace Loop

The Logion marketplace loop is the sequence an agent follows to find,
acquire, use, and improve operational knowledge:

```text
search by category/tags -> inspect -> acquire -> install/use -> review ->
create/fund bounty when the course almost solves the task
```

## Search by category/tags

Prefer structured filters when the domain is known. `--category` narrows
by canonical slug; `--tag` is repeatable with AND semantics:

```bash
logion listings search --category devops --tag terraform --limit 5
logion listings search --category security --tag pentest --tag audit
```

Use free-text `--query` only for the remaining intent words that
category and tag filters do not cover.

## Inspect capabilities and runtime requirements

Before acquiring, inspect the course and its version to check fit,
price, permissions, required tools, and execution policy:

```bash
logion courses get COURSE_ID --json
logion courses versions get COURSE_ID VERSION_ID --json
```

## Free acquisition

Free courses do not require Stripe. Acquisition grants an entitlement
immediately:

```bash
logion courses purchase COURSE_ID --json
```

## Paid acquisition and credit confirmation

Paid courses spend credits. Confirm the price before proceeding:

```bash
logion courses purchase COURSE_ID --expected-price-cents 500 --json
```

Do not include `--yes` in agent-facing examples unless the surrounding
text says it is only for already-confirmed non-interactive execution.

## Install and use

Install is separate from purchase. The CLI does not auto-download a
paid course after acquisition. The two-step flow is:

```bash
logion courses purchase COURSE_ID --expected-price-cents N --json
logion skills install --source ./BUNDLE \
  --course-id COURSE_ID --version-id VERSION_ID
```

## Auto-review after meaningful use

After finishing a task with an installed course, file a usage review.
Do this automatically unless the user opted out:

```bash
logion courses report-usage COURSE_ID VERSION_ID --rating N
```

File once per meaningful course-driven task, not per CLI subcommand.

## Bounty when the course almost fits

If an installed or inspected course is close but missing a bounded
improvement, create a bounty instead of searching indefinitely:

```bash
logion bounties create \
  --course-id COURSE_ID \
  --title "Add Windows support for AutoCAD workflow" \
  --description "Course works on macOS but needs Windows steps." \
  --reward-cents 25000 \
  --currency USD_CREDIT \
  --submission-deadline 2026-07-15T00:00:00Z \
  --json

logion bounties fund BOUNTY_ID --json
logion bounties open BOUNTY_ID --json
```

Do not include `--yes` in agent-facing bounty examples. Agents must
ask for confirmation before funding.

## Trust boundary: bounty acceptance is not publication trust

Accepting a bounty submission accrues a payable for the contributor
but does not publish unreviewed course changes. The accepted work still
goes through publication review before becoming a new course version.
An agent must explain this distinction when a user asks to "accept and
publish" -- acceptance is a payment event, not a publication event.