logos-documented-scenarios

name	logos-documented-scenarios
description	Use when the user wants to run a documented Logos operator flow such as the LEZ wallet and token workflows, blockchain node quickstart, delivery API compose stack, chat demo, AnonComms mixnet demo, app-alpha build, or headless-node logoscore subset. Covers all docs-backed journeys with explicit gap handling.

Logos Documented Scenarios

This skill covers all documented operator flows from logos-docs journeys. Each scenario has explicit gap handling -- when the docs are stubs or incomplete, this skill says so rather than inventing commands.

Quick start

• Read references/lez-wallet-flows.md for LEZ wallet, token, and AMM commands.
• Read references/blockchain-node-flows.md for the blockchain node quickstart.
• Read references/messaging-and-demos.md for delivery API, chat demo, and AnonComms mixnet demo flows.
• Read references/stubbed-journeys.md for app-alpha and headless-node journeys that are explicitly incomplete.

Scenario routing

User ask	Reference file	Confidence
Set up the LEZ wallet	lez-wallet-flows.md	medium
Transfer tokens on LEZ	lez-wallet-flows.md	medium
Create a token on LEZ	lez-wallet-flows.md	medium
Use the AMM	lez-wallet-flows.md	medium
Run a blockchain node	blockchain-node-flows.md	medium
Use the delivery API	messaging-and-demos.md	low-to-medium
Run the chat demo	messaging-and-demos.md	low (stub)
Run the mixnet demo	messaging-and-demos.md	medium
Build the app alpha	stubbed-journeys.md	low (stub)
Run headless node	stubbed-journeys.md	low (stub)

Workflow

1. Match the user's request to a scenario from the routing table above.
2. Read the matching reference file for commands, checkpoints, and known gaps.
3. Give the documented command subset directly when the confidence is medium or higher.
4. For low-confidence scenarios (stubs), give only the safe documented subset and make the gaps visible.
5. If the request grows beyond the documented flow, route to:
   • logos-discovery for broader stack routing
   • logos-core-module-builder or logos-ui-qml-builder for implementation work
   • logos-module-build-loop for operational build/package/install work
   • logos-scaffold-bootstrap for standalone LEZ app bootstrap

Quality rules

• These are doc-grounded operator snapshots, not substitutes for local code checkouts.
• Do not invent commands that aren't in the referenced documentation.
• Keep placeholder semantics visible (e.g. Public/<account-id>, <release>, <peer1>).
• When a journey is a stub, say that explicitly and route to the appropriate builder skill.
• Distinguish local compose flows from Logos-testnet-specific behavior.
• Present release examples as documented examples, not guarantees of current versions.