9258a0739f
The apps branch's documents join the version contract. The answer layer's documents (wai.quantum.answer/1: an answer read, carried out, a seal's request and result, a stored answer checked), described as a draft whose form may change before the extension settles; a correctness record and its corpus (wai.quantum.telemetry/1); the views page's manifest (wai.quantum.views-bundle/1); and the command line's harness report, corpus and token counts (wai.quantum.eval-report/1, eval-answers/1, token-cost/1). The engine's test holds every answer of the layer's conformance set (read, carried out, half arrived, and stored and verified), records, the corpus and the committed manifest to them; the eval tests hold a scripted run's report, a model server's, the corpus and the committed token counts; check_schemas.py holds the committed documents too. The tool and diagnostic schemas take the answer layer's outcomes, dropped and defaulted. The result view's own tool, poll_quantum_job, listed only to a host that draws views, answers to the job's schema, and the strict test holds it. The basis rename reaches the views: a compile's words and its view name the gate set by its basis (both read the certificate's old target), and a test in each holds it. The service's job summary now lives in engine::views (the apps branch moved it there); it carries the durable branch's set summary and the processor packages' energy wording with it. The answer set's stored seal was made at 0.6.16; the values it seals name their engine, so it is written again at 0.7.0 (WAI_ANSWER_BUNDLE_WRITE=1). The views crate's lock moves to wai-quantum 0.7.0. Co-Authored-By: Claude Opus 5.5 <[email protected]>
112 lines
2.7 KiB
JSON
112 lines
2.7 KiB
JSON
{
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$id": "https://git.transaction.science/Transaction-Science/open-standards/raw/branch/main/wai/wai-quantum-cli/schemas/token-cost.v1.json",
|
|
"title": "wai.quantum.token-cost/1",
|
|
"description": "What a task set's answers (wai.quantum.eval-answers/1) take in tokens, each written four ways, as wai/quantum-conformance/eval/token_cost.py counts them: their bytes, and for each tokenizer its vocabulary, the totals, the means and the ratios against the program alone.",
|
|
"type": "object",
|
|
"required": [
|
|
"format",
|
|
"answers",
|
|
"bytes",
|
|
"tokenizers"
|
|
],
|
|
"properties": {
|
|
"format": {
|
|
"const": "wai.quantum.token-cost/1"
|
|
},
|
|
"about": {
|
|
"type": "string"
|
|
},
|
|
"answers": {
|
|
"type": "integer",
|
|
"minimum": 0
|
|
},
|
|
"bytes": {
|
|
"type": "object",
|
|
"properties": {
|
|
"plain": {
|
|
"type": "number"
|
|
},
|
|
"views": {
|
|
"type": "number"
|
|
},
|
|
"views_request": {
|
|
"type": "number"
|
|
},
|
|
"job": {
|
|
"type": "number"
|
|
}
|
|
}
|
|
},
|
|
"tokenizers": {
|
|
"type": "array",
|
|
"items": {
|
|
"type": "object",
|
|
"required": [
|
|
"name"
|
|
],
|
|
"properties": {
|
|
"name": {
|
|
"type": "string"
|
|
},
|
|
"vocabulary": {
|
|
"type": "integer"
|
|
},
|
|
"totals": {
|
|
"type": "object",
|
|
"properties": {
|
|
"plain": {
|
|
"type": "number"
|
|
},
|
|
"views": {
|
|
"type": "number"
|
|
},
|
|
"views_request": {
|
|
"type": "number"
|
|
},
|
|
"job": {
|
|
"type": "number"
|
|
}
|
|
}
|
|
},
|
|
"mean": {
|
|
"type": "object",
|
|
"properties": {
|
|
"plain": {
|
|
"type": "number"
|
|
},
|
|
"views": {
|
|
"type": "number"
|
|
},
|
|
"views_request": {
|
|
"type": "number"
|
|
},
|
|
"job": {
|
|
"type": "number"
|
|
}
|
|
}
|
|
},
|
|
"against_plain": {
|
|
"type": "object",
|
|
"properties": {
|
|
"plain": {
|
|
"type": "number"
|
|
},
|
|
"views": {
|
|
"type": "number"
|
|
},
|
|
"views_request": {
|
|
"type": "number"
|
|
},
|
|
"job": {
|
|
"type": "number"
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"additionalProperties": true
|
|
}
|
|
}
|
|
},
|
|
"additionalProperties": true
|
|
}
|