Get started with the Sley public workflow

Step-by-step

1. Read the public release boundary first, then open `/readme` and `/docs` for scope and constraints.
2. Run a baseline posture check with `sley doctor --json .` and capture the context.
3. Inspect the smallest relevant slice with `sley ast --json .` and `sley graph --json --slice <node-id> .`
4. Draft edits with structure-first plans using `sley plan --json --graft-templates .`
5. Dry-run repair candidates before write operations using `sley fix --json --kind <kind> --dry-run .`
6. Promote only stable actions after `sley lint --json .` and `sley verify --json .`.

Sample intent sketch

language Sley:
  project        -> explicit_contract
  intent         -> bounded_plan
  edit           -> compiler_checked_mutation
  authority      -> declared_capability
  verify         -> deterministic_receipt

Hands-on walkthrough

# 1) Baseline checks
sley doctor --json .

# 2) Understand shape and flow
sley ast --json .
sley graph --json --slice <node-id> .

# 3) Build a bounded edit plan
sley plan --json --graft-templates .

# 4) Dry-run repairs and re-verify
sley fix --json --kind add_module_declaration --dry-run .
sley lint --json .
sley verify --json .

Next actions

Continue from the docs page and use OpenForge + release links as your anchor. This keeps public claims consistent while minimizing repeated context and overpromising.