SALP Flow Playbooks
[!note] This site publishes the public playbook surface generated from tracked files under
flow/playbooks/. Canonical implementation specs stay in the repository and are linked from playbooks when deeper contract detail is needed.
Use these playbooks as the public, operator-friendly path through SALP Flow.
Playbooks
Section titled “Playbooks”- Acceptance Review Loop: Use this playbook after implementation validation is already recorded with wap-flow complete.
- Flow Code Quality Audit: Last reviewed: 2026-04-25
- Flow Relay Status Summary: Use this status memo when deciding whether to finish the remaining relay runtime features first or proceed with a narrower relay gate around the current control-plane surface.
- Flow Status Summary: Use this status memo when evaluating flow as a workflow contract for engineers and operators.
- GitHub-Backed Happy Path: Use this flow when the task authority is a structured GitHub task issue or sub-issue.
- Install And Upgrade: Use this playbook when you want a consumer repository to run wap-flow from an installed binary instead of a vendored Rust workspace.
- Live Sandbox Validation: This playbook is the operator-friendly companion to flow/specs/flow-acceptance-sandbox-contract.md.
- Local-Private Happy Path: Use this flow when the task starts as a local record under flow/state/tasks/.
- Managed CLI Relay: Use this playbook when you want to adopt the current local relay control-plane surface quickly.
- Release Readiness: Repo-Pack GA means the flow mechanism is safe to install into other repositories, not only usable inside this source repository.
- Troubleshooting: Use the smallest read-only surface that answers the question before changing workflow state.