Record findings from completed offline human tasks (interviews, observations, outreach) back into the canvas. The re-entry point after /handoff.
The re-entry point after offline human work. Takes raw conversation notes, observations, or survey results and integrates them into the canvas with proper provenance.
canvas/human-tasks.ymlCheck pending tasks:
canvas/human-tasks.yml for pending_tasksGuided evidence capture (if user doesn't have a filled template):
Classify the evidence on Gilad's ladder:
anecdotal (0.3)anecdotal (0.3), note convergencedata-supported (0.5-0.6)Update canvas provenance:
canvas_refs)provenance:
evidence_type: anecdotal # single conversation
evidence_sources:
- "interview-YYYY-MM-DD-[role-descriptor]"
source_classes:
- external_human
captured_at: "YYYY-MM-DDTHH:MM:SSZ"
confidence: 0.3
evidence_sources and source_classes arraysevidence_type if the new evidence strengthens itconfidence score with explicit reasoningcaptured_at timestampUpdate canvas/human-tasks.yml:
pending_tasks to completed_taskscompleted_at, evidence_logged_to, key_findings, source_class: external_humanIf the user reports a task couldn't be completed (contact unavailable, timing didn't work, etc.):
Ask: "Should we cancel this task or reschedule it?"
If cancel: move to completed_tasks with source_class: cancelled and a note explaining why
If reschedule: update the task's objective or target_persona if needed, keep in pending_tasks
Either way: "The evidence gap still exists. Consider /handoff to plan an alternative approach."
Check for contradictions:
/devils-advocate to stress-test this assumption, or update the canvas with /canvas-update."Recalculate confidence:
Suggest next steps:
/handoff for 1-2 more to reach triangulation."/diamond-progress to attempt the next transition."/devils-advocate or revisit the canvas."canvas/human-tasks.yml (moves task to completed)canvas/opportunities.yml, canvas/user-needs.yml, canvas/jobs-to-be-done.yml depending on findings