panel
Summarize supplied human or model elicitation records without inventing missing answers.
Contract
Respondent IDs must be unique. At least one probability is needed. The returned range is disagreement, not calibrated uncertainty; this command does not contact respondents.
Fields
| Field | Type | Required |
|---|---|---|
op | "panel" | Yes |
responses | array of Elicitation | Yes |
This operation needs no existing question or forecast. Use --memory for a calculation-only session.
Request
Send this object on one line. It is expanded below for readability.
{
"version": 1,
"id": "example",
"command": {
"op": "panel",
"responses": [
{
"respondent_id": "a",
"respondent": {
"kind": "human",
"pseudonym": "A"
},
"probability": 0.3,
"supporting_reason": "relevant reference cases",
"opposing_reason": "integration risk"
},
{
"respondent_id": "b",
"respondent": {
"kind": "human",
"pseudonym": "B"
},
"probability": null,
"supporting_reason": "",
"opposing_reason": ""
}
]
}
}
Response
This response is generated by executing the example against the current binary. Commit timestamps, when present, are shown as <runtime UTC seconds>; the actual protocol returns integer UTC seconds.
{
"version": 1,
"id": "example",
"result": {
"invited": 2,
"maximum": 0.3,
"median": 0.3,
"minimum": 0.3,
"missing": 1,
"responded": 1
}
}
Verification
The documentation gate executes the setup and request, then checks the following result fields against independently specified expectations:
JSON pointer within result | Expected |
|---|---|
/invited | 2 |
/responded | 1 |
/missing | 1 |
/median | 0.3 |
Float comparisons use a 1e-12 tolerance. Request schema validation and cross-record validation still apply. See errors and recovery for failure handling.