Skip to content
Trazum

1.65.0

The format anyone can adopt

Released 2026-08-24. The 1.65 arc closes: a document can be checked against this format by a tool that has never installed this product. Eighteen named contracts, exportable schemas, and a producer's page whose examples are run — not read — by the build.

Added#

  • The producer's page — chapter three of the 1.65 arc. docs/format.md grows the section a connector author actually needs: emit-this-minimum examples for the two contracts that exist to be written by tools that are not Trazum (a usage-log record whose only required field is model, and an outcome report exactly as @trazum/core computes one), the additive promise restated from the producer's side (add anything, redefine nothing, never write 0 for a measurement nobody took), and where the schemas live — trazum schema piped to any off-the-shelf validator, with the $id stated as an identifier, never fetched. Held the only way that cannot rot: producer-page.test.js extracts every labelled example from the page and runs it through trazum conform — the product, not a re-implementation — then guts a required field from each and requires the gutted copy to fail, and the $id quoted in prose is compared to the one the schema actually carries.

  • The schema leaves the repository — chapter two of the 1.65 arc. A schema command prints an authored JSON Schema (draft 2020-12) for any named contract, so a document can be checked by any off-the-shelf validator with no Trazum installed. The schemas state required fields and their types and stop there — additionalProperties is never false, because these documents gain fields without a version bump. Held to conform by construction, not coincidence: requiredFieldsOf exports the exact list conform enforces, the guard compares every schema's required to it (it caught five drifts and a missing noRate before the chapter was an hour old), and every schema-shaped minimum round-trips through both doors while gutting any field fails both. The suite's validator is thirty lines over the subset the schemas use — the zero-dependency rule, kept — and is handed planted defects before anything trusts it. Two carve-outs are stated where they live: the cost answer's verdict union is open by the format's own rule, and the outcome report's rate/refusal exclusivity is relational — carrying it is what conform is for.

  • Every contract answers to its name — chapter one of the 1.65 arc. The seven documented contracts --contract could not name — fleet, spend-guard, first-run, pulse, rule-yield, gateway-refusal and bench — get names, required-field rules and detection, held to the same discipline as the eleven: detection ordered so a fleet (a list of full profile reports) classifies before the profile check and a spend-guard verdict (which contains a cost answer) before the cost answer, the same reasoning the roll-up already carries. docs/format.md stops saying the claim is narrower in the product than on the page: --contract names eighteen of them, and the derived guard that compares the table's column to CONTRACT_NAMES moved the sentence itself. Each new contract is proved by the document it rejects: the documented minimum conforms, and gutting any required field fails with the field named.

  • The plan through 1.65, 1.66 and 1.67, written before the code. The owner's five open-source paths, carried exactly as far as they go as code, with the not-code halves named in "what stays out" rather than dressed up as chapters. 1.65 — the format anyone can adopt: all eighteen contracts answer to a --contract name, and an authored JSON Schema per contract leaves the repository, held to agreeing with conform by a two-direction guard. 1.66 — one policy, three doors: per-label/session/day USD limits stated once, judged once in the core, enforced identically by the gateway, serve and spend_guard — with the same call pushed through all three doors and the verdicts required to match. 1.67 — the month ends on a measured position: month-to-date spend against every limit with the denominator on every figure and no projection anywhere, travelling through JSON, the HTML door and MCP; plus check reading a file list from stdin so a pre-commit hook is one pipe.