Trace a record
trace_recordFollow a learning-design record forward and backward through its lifecycle: evidence, needs, objectives, assessments, datasets, metrics, notes, and findings, with each link naming its field.
Instructions
Where a record comes from and where it leads, both ways along the design's lifecycle: evidence and the need it supports, the objective the need generated, the items that assess it, their placements and assessments, and the datasets and metrics measured on them; with the notes and findings written on the records passed. Each link names the field it follows. The answer carries labels: read a note's or a relationship's rationale with get_record.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"type": "<type>",
"id": "<id>"
},
"name": "trace_record"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The record's id, as Type/local (LearningObjective/lateral-reading-check) or the local part alone. | |
| ref | No | A commit id to read at, as an earlier answer named it: pass the commit from your first answer to every follow-up, so the conversation reads one state of the design. Pass this or branch, not both. | |
| type | Yes | The record's class, such as LearningObjective, AssessmentItem, Module or DesignNote. | |
| branch | No | The branch to read at its latest commit. Leave out to read the default branch (main unless configured otherwise). Pass this or ref, not both. |