fsl-businesslisted

# FSL Business Layer Use this skill to turn business process material into a `business Name { ... }` FSL file. Keep the output at the business/consulting level: process stages, business transitions, policies, KPIs, goals, and control preservation evidence. Before writing syntax, read `../fsl/SKILL.md` and `../fsl/reference.md` for the shared FSL verifier workflow and language rules. When working inside this repository, read `examples/consulting/` for As-Is/To-Be work, `examples/pm/cancel_flow.fsl` for a PM-friendly business flow, and `examples/e2e/1_business.fsl` when this business layer will be chained downstream. ## Boundary Produce business-layer artifacts only: - A `business` spec with `actor`, `entity`, `process`, `transition`, optional `control`, `policy`, `kpi`, and `goal`, plus a top-level `verify { instances Entity = N }` bound - Optional standalone `governance` catalog when the same controls must be traced across multiple business specs - Verification commands/results, usually `fslc verify ... --engine induction` - Optional As-Is/To-Be control preservation using `fslc refine` and a mapping file Do not write system requirements, acceptance criteria, UI states, service/API shape, data models, queues, outboxes, retry algorithms, implementation adapters, or design refinement maps from business material. If the source asks for those, route the work to `fsl-requirements` or `fsl-design` after the business layer is agreed. ## Workflow 1. Extract a business fo