Record a drift score
drift_recordLog a 0-100 fidelity score per ticket to detect drift from intent, with derived verdicts (aligned, partial, drift) and an optional gap note.
Instructions
Record a 0–100 fidelity score for one ticket in a drift run (verdict is derived: >=80 aligned, 50–79 partial, <50 drift — or pass your own). Provide a short gap explaining any shortfall, and optionally the files you checked. Upserts by ticket.
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": {
"project": "<project>",
"ticket": "<ticket>",
"score": "<score>"
},
"name": "drift_record"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| gap | No | What drifted / what's missing (for partial/drift). | |
| files | No | Files/paths inspected for this ticket. | |
| runId | No | Drift run id (defaults to the latest run). | |
| score | Yes | Fidelity 0–100 of implementation vs the ticket's intent. | |
| ticket | Yes | ||
| project | Yes | ||
| verdict | No |