VLS: a vendor-neutral verification artifact spec
VLS is a vendor-neutral wire format for verification artifacts produced by AI coding agents and verification tools.
- apply-valid-code
- reject-expired-code
- stack-with-sale-price
- ui-shows-discount-line
Four pieces
A calibrated, per-case verdict referencing the task, acceptance results, and evidence.
Artifacts validate against published schemas, so any tool can produce or consume them.
A shared set of fixtures an implementation must satisfy to claim conformance.
Timaeus in TypeScript, with room for a second independent implementation.
A TaskScore is just data
Because artifacts are plain validated JSON, they move through CI, dashboards, and review tools without lock-in.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "TaskScore",
"type": "object",
"required": ["case", "claim", "verdict", "evidence"],
"properties": {
"case": { "type": "string" },
"claim": { "type": "string" },
"verdict": { "enum": ["merge", "warn", "block"] },
"confidence": { "type": "number", "minimum": 0, "maximum": 1 },
"acceptance": {
"type": "object",
"properties": {
"passed": { "type": "integer" },
"failed": { "type": "integer" }
}
},
"evidence": { "type": "array", "items": { "type": "string" } }
}
}Designed to fit existing pipelines
VLS is meant to interoperate with the tools teams already run, not replace them.
An open standard, owned by no single tool
VLS is built to stay vendor-neutral: published schemas, a conformance corpus, and room for independent implementations, so the artifact format is never locked to a single tool.
Private beta repository. Public VLS/Timaeus release in progress.