Work Map

work-map: the map for multi-session efforts

A session handoff carries one session's baton. A work map preserves one canonical route per effort: the sufficient parent issue, a declared project document or a link-only fallback.

Read the repository's Repository process declaration first. If absent, use an existing owner or propose the route in chat; never invent one. Its declared workflow-state owner holds live state; this map never does. In issue-tracker mode, if the parent issue has enough destination, route and invariant detail, the parent tracker issue is the work map: link to it and do not create a duplicate file. In project-docs mode, use its named map or story home. A link-only file is only an unavailable-tracker or cross-tracker fallback. It links owners and never restates current status, owner, dependencies or user gates.

Optional link-only map

Create a file only for project-docs or an unavailable/cross-tracker fallback. A docs fallback may use docs/efforts/EFFORT-<slug>.md when authorised.

# 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 declared workflow-state owner.
• Route entries are links, not task summaries. Stable ordering is allowed; Route and Invariants contain links only.
• Resume order: declared scope/story and workflow-state owners → fallback or cross-tracker map → claimed session handoff. Never reconstruct from transcripts or piled-up handoffs.
• Handoffs stay temporary. They carry continuity for an active session or run, are not linked as route state, and are archived by session when consumed; never delete them.
• One map writer. One chair updates the route after checking declared owners.
• Archive a route map under the project's archival policy only when the declared workflow-state owner records that disposition.
• Before handoff, check the map keeps the three headings, links only, and no red flag below.

Red flags

• Status:, task checkboxes or an "Updated" freshness claim → delete them and link the declared workflow-state owner.
• Map restates a specification, decision or issue → link, don't copy.
• A handoff appears as route state → keep it in the temporary continuity layer.
• Re-planning changes accepted scope → return to scope, then update stable route links after the declared scope/story owner records the decision.

Portable artifact

When the declared tracker is unavailable, use the named project-docs home or a link-only fallback; never invent rolling project state. Use the skill-owned effort map schema.