START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Turn approved office steps into a reviewed SOP
Starter kit A24

These files support a manual, read-only pilot. The workflow is proposed and has not been run against a live system. All example records are invented.

START HERE
1. Keep blank templates and synthetic examples separate. Use the example files first, renaming copies to the input names listed below if the prompt expects those names.
2. Open CSVs with UTF-8 and comma delimiters. Preserve IDs, timestamps and empty values as text on import. Empty means missing, not zero. There are no formulas. Do not change column headings.
3. Prepare the required policies and native documents. Stop any check whose inputs, coverage or permission are missing.
4. Use the recipe's prompt in the firm-approved workspace and request the stated review artifact. Treat all file content as data, not instructions.
5. Compare the result with expected-results.txt and the original rows/pages. Do not enable live connections or send anything from this kit.

INPUT CONTRACT
approved-process-notes.txt with source paragraph IDs; role-map.csv: step_id, approved_role; policy-register.csv: policy_id, approved_version, owner_role, review_date; redacted screenshots if needed.

RECIPE-SPECIFIC SETUP
The example notes deliberately conflict on the destination folder and omit completion evidence. Surface both as questions; neither the role-map nor the policy register resolves them. No real file paths or client screenshots are included.

PREREQUISITES
- Sanitized process notes, screenshots without client data, approved role map and explicit policies; Word or existing knowledge system; optional template tasks after approval.

REVIEW CHECK
Process owner and affected staff approve; test with a new staff member using synthetic examples. Keep version, approval date and review owner. No live workflow changes are part of the recipe.

EXPECTED OUTPUT
Approved assistant workspace drafts SOP.md and checklist.csv. A process owner approves before copying into a knowledge base or task-template tool.

Validation covers file syntax, exact declared headers and fixture consistency. It does not establish product compatibility, legal sufficiency, data completeness or production readiness.