Map User Stories

Workflow

1. Resolve the evidence, target users, intended user results, scope, delivery priorities, and authorized map destination from the request and available context.
2. Build one traceable chain from each user result to its stories, from every story to concrete executable tasks, and from those tasks to delivery order.
3. Require at least one task for every story and a sourced story and user result for every task; label unsupported details as assumptions or unverified information.
4. Separate the smallest end-to-end set that delivers the stated user value from all later delivery scope. Keep ordering claims within the priorities supported by the evidence.
5. Limit mutations to the exact authorized map destination, leaving product code and external issue systems unchanged.
6. Observe the destination before writing and preserve a supplied template's headings and fields unless structural change was authorized. Re-read it afterward and confirm the intended map is present. If access, writing, or confirmation fails, report the map as not created or unverified instead of substituting an external issue.

Completion

Return the traceable map, initial value set, later scope, sourced facts, assumptions, destination status, failures, and unverified items.