work-maplisted

# work-map: the map for multi-session efforts A `session` handoff carries one session's baton. Across many sessions or agents, the work map preserves the stable route: one file per effort, read for durable orientation and changed only when that route changes. The project's work tracker owns live work state. In Provenant, GitHub issues own the current owner, dependencies and user gates, while Project Status owns workflow state. An effort map links those owners and never restates current status, owner, dependencies or user gates. ## The map file Use the project's canonical effort file. If no owner exists, propose `docs/efforts/EFFORT-<slug>.md` only when project-write authority allows it; otherwise return the map without writing. Structure: ```markdown # EFFORT: <name> ## Destination What the route is intended to deliver. Link the owning specification. ## Route - [Programme issue](https://example.invalid/issues/1) - [Related delivery](https://example.invalid/pull/2) ## Invariants - [Governing decision](https://example.invalid/decisions/1) ``` ## Rules - **Link, never restate live work state.** Do not add status fields, task checkboxes, completion claims, owner names, dependencies, blockers or user gates. Readers follow the linked issue and its Project Status field. - **Route entries are links, not task summaries.** Stable grouping and ordering are allowed; issue and pull-request prose carries changing detail. - **Resume order:** project state file → issue and Pr