setspec 0.4.0__tar.gz → 0.6.0__tar.gz

{setspec-0.4.0 → setspec-0.6.0}/CHANGELOG.md

@@ -7,6 +7,94 @@ packaging and release standards §3.
 
 ## [Unreleased]
 
+## [0.6.0] — 2026-09-02
+
+### Added
+
+- **`benchmark.evidence_bundle` `1.1`** (Phase 7, ADR-0068 rule 5): the adapter axis carried one
+  payload out from `capability.evidence` `1.1`, so an exported bundle can hold adapter-bearing
+  evidence records. `EvidenceBundleV1_1Fields` overrides exactly one inherited field — `evidence`
+  becomes `WireSequence[CapabilityEvidenceV1_1Fields]` in place of the `1.0` element type — on a
+  new sibling class (`EvidenceBundleV1_1Out`/`EvidenceBundleV1_1In`) rather than an edit to the
+  existing `EvidenceBundleFields`/`EvidenceBundleOut`/`EvidenceBundleIn`, which keep meaning `1.0`
+  permanently. A bundle whose records carry no adapter dumps byte-for-byte what `1.0` writes today,
+  because a `1.1` evidence record with no adapter already dumps byte-identically to its `1.0`
+  counterpart — proved over the *existing* committed `1.0` goldens by the new
+  `tests/contract/test_bundle_minor_is_additive.py`, the bundle's own analogue of the `1.1` I15
+  exit-condition test. Mixed bundles — bare-base and adapter-bearing records in the same complete
+  export, the shape FreeWeight 1.1's actual export (H4, LA3) produces — are the intended semantics,
+  golden-tested as `goldens/benchmark.evidence_bundle/1.1/mixed.json`.
+
+### Changed
+- Every prose reference to the planned "SpotCheck" package renamed to its actual name,
+  **Commissioner** — `spotcheck` collided with an unrelated, already-published PyPI package.
+  Cosmetic only: `governance.egress_decision`'s committed `1.0` JSON Schema snapshot regenerated
+  because two nested-type docstrings (`EgressVerdict`, `EgressRequestFields`) named the package;
+  no property, type or required field moved, confirmed by a description-stripped structural diff
+  before committing (the same check `docs/schemas.md` §5 documents for a dependency-docstring
+  ripple). Goldens are untouched — no wire value changed.
+
+## [0.5.0] — 2026-09-02
+
+### Added
+
+- **`capability.evidence` `1.1`** (Phase 6, ADR-0058): an optional `adapter` field naming the
+  adapter axis a measurement was taken under. Absent — and byte-for-byte identical to `1.0` — on
+  every record measured on the bare base; a `@model_serializer` drops the field from the dump
+  entirely when unset, rather than emitting `"adapter": null`, so a non-adapter record written
+  through the new model is indistinguishable from what `0.4.0` writes (LA0 exit condition I15).
+  Lives on a new sibling class, `CapabilityEvidenceV1_1Fields`
+  (`CapabilityEvidenceV1_1Out`/`CapabilityEvidenceV1_1In`), rather than an edit to the existing
+  `CapabilityEvidenceFields`/`CapabilityEvidenceOut`/`CapabilityEvidenceIn`, which keep meaning
+  `1.0`: `benchmark.evidence_bundle` nests the `capability.evidence` shape by reference, so an
+  edit in place would have silently moved that schema's own committed `1.0` snapshot too. The
+  mechanism and the naming rule it implies — a bare exported name keeps the version it was frozen
+  at, so adopting `1.1` is an explicit import of `CapabilityEvidenceV1_1Out`/`In` and never
+  something a dependency upgrade delivers — are ADR-0068.
+- **`model.adapter_manifest` `1.0`** (Phase 6, ADR-0061): the operator-reviewed record behind one
+  adapter — `name`, `artifact_file`, `artifact_sha256`, optional `source_sha256`, `base` (a
+  provider model name plus an optional artifact digest, at `digest`-or-`name_only` confidence),
+  `declared_capabilities`, `data_classification`, `format`, `created_at`, `notes`. `name` and the
+  two digest fields are validated by reconstructing a `baseaicore.AdapterIdentity`, reusing that
+  type's own name-pattern and digest-normalization rules rather than a second implementation.
+  **`data_classification` is required, with no schema default** (ADR-0065 rule 1): a manifest that
+  omits it is invalid, never silently defaulted closed.
+- **`governance.egress_decision` `1.0`** (Phase 6, ADR-0051 §4, ADR-0054): one recorded egress
+  verdict — `decision_id`, an embedded request (`run_id`, `source_ref`, `data_classification`,
+  `target{name, remote, max_data_classification, provider_kind}`, `requested_at`), `verdict`
+  (`approved`/`denied`/`violation`), `reason`, `policy_name`, `policy_version`, `decided_at`.
+  SetSpec's first payload under a root other than `benchmark`/`capability`/`machine`/`model` —
+  added because the shape has a named second reader (IdeaPress's S4 egress badge reads decisions
+  PromptCadence exported, with Commissioner not installed). Two nullable fields, both one level down.
+  `target.max_data_classification` is deliberate: "remote with no declared ceiling" is the
+  fail-closed case a policy must be able to deny and record. `request.requested_at` mirrors
+  Commissioner spec §7's own `None` default and is on the wire so that its §11 contract 4 —
+  `from_payload(to_payload(d))` preserves **every** field — is keepable: a value-object field with
+  nowhere to land makes that round trip silently lossy. It is not a second record timestamp;
+  `decided_at` is the record's, and it stays required. Commissioner does not exist as code yet;
+  nothing here imports it.
+- JSON Schema and goldens for all three: `capability.evidence/1.1.json` (`minimal`, `full`,
+  `unsupported`), `model.adapter_manifest/1.0.json` (`minimal`, `full`, `name_only`),
+  `governance.egress_decision/1.0.json` (`minimal`, `full`, `denied_no_ceiling`, `violation`).
+  The `capability.evidence/1.0` and `benchmark.evidence_bundle/1.0` schemas and goldens are
+  byte-for-byte unchanged — asserted by a dedicated contract test (I15) rather than by inspection.
+
+### Changed
+
+- **`baseaicore>=0.4.1,<0.5`** (was `>=0.4,<0.5`). `setspec.governance.v1` and
+  `setspec.model.v1` import `DataClassification` and the adapter value objects at module scope,
+  and neither name exists in `baseaicore 0.4.0` — the old floor permitted an install that raises
+  `ImportError` on import. The same floor is what makes the snapshots below reproducible.
+- Five already-committed `1.0` JSON Schema snapshots (`model.identity`, `benchmark.result`,
+  `benchmark.run_summary`, `capability.evidence`, `benchmark.evidence_bundle`) were regenerated to
+  pick up two `baseaicore 0.4.1` enum docstring edits (`IdentityConfidence`,
+  `ModelCapabilityFlag`) that the raised floor above surfaces in their nested `$defs`
+  descriptions. **Structurally identical** — no property, type or required-field changed,
+  confirmed by a description-stripped diff before committing; the regeneration is a byproduct of
+  the dependency bump, not a payload change (`docs/schemas.md` §5).
+- Bumped to 0.5.0 for the `capability.evidence` `1.1` addition and the two new payload types
+  (packaging standards §3: additive, non-breaking).
+
 ## [0.4.0] — 2026-08-29
 
 ### Added

{setspec-0.4.0 → setspec-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: setspec
-Version: 0.4.0
+Version: 0.6.0
 Summary: Every versioned data contract that crosses an application boundary: benchmark results, capability evidence, event/error envelopes, prompt records.
 Project-URL: Homepage, https://github.com/JPKell/SetSpec
 Project-URL: Documentation, https://github.com/JPKell/SetSpec/tree/main/docs
@@ -16,7 +16,7 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Typing :: Typed
 Requires-Python: >=3.12
-Requires-Dist: baseaicore<0.5,>=0.4
+Requires-Dist: baseaicore<0.5,>=0.4.1
 Requires-Dist: jinja2<4,>=3.1
 Requires-Dist: pydantic<3,>=2.9
 Provides-Extra: dev
@@ -35,18 +35,32 @@ Description-Content-Type: text/markdown
 
 Every versioned data contract that crosses an application boundary: benchmark results, capability evidence, event/error envelopes, prompt records.
 
-**Status:** `0.3.0` — Phases 1–2, 3A and 4 complete, and **the v1.0 contracts are frozen.** Eight
-payload types are published at `1.0` — `model.identity`, `machine.profile`, `benchmark.result`,
-`benchmark.run_summary`, `capability.evidence`, `benchmark.evidence_bundle`,
+**Status:** `0.6.0` — Phases 1–2, 3A, 4, 5, 6 and 7 complete, and **the v1.0 contracts are frozen**,
+with two additive minors now published on top of that freeze. Six payload types remain frozen at
+`1.0` only — `model.identity`, `machine.profile`, `benchmark.result`, `benchmark.run_summary`,
 `benchmark.goal_pack` and `benchmark.calibration_report` — each with generated JSON Schema and at
 least three golden payloads shipped as package data. `setspec.DRAFT_SCHEMAS` is empty, which is
 where the freeze is readable at runtime rather than only stated here; from now on a new optional
 field is a minor bump and anything else is a major, enforced by a snapshot diff in CI.
 
+Phase 6 (the adapter arc's LA0 checkpoint) adds three things without touching any of the above:
+`capability.evidence` gains an additive `1.1` (an optional `adapter` field, absent — and
+byte-identical to `1.0` — on every record with no adapter); `model.adapter_manifest` `1.0`
+publishes the operator-reviewed record behind one adapter; and `governance.egress_decision` `1.0`
+is the package's first payload under a root other than `benchmark`/`capability`/`machine`/`model`,
+carrying a recorded egress verdict for a reader that has Commissioner installed or not. Phase 7
+carries that same minor one payload out: `benchmark.evidence_bundle` gains its own additive `1.1`,
+nesting `capability.evidence` `1.1` in place of the `1.0` element type its frozen `1.0` still
+nests, so an exported bundle can now carry adapter-bearing evidence — absent any adapter,
+byte-identical to `1.0`. `capability.evidence` and `benchmark.evidence_bundle` are therefore the
+two payload types with a second published minor; every other payload type remains exactly `1.0`.
+
 The [schema catalogue](docs/schemas.md) lists every payload type, its artifacts, and the
-cross-field rules the JSON Schema cannot express. Event and error envelopes (Phase 3) and prompt
-records (Phase 5) are not yet written and are therefore not part of the freeze. See the
-[development plan](docs/packages/setspec/development-plan.md) for what each phase adds.
+cross-field rules the JSON Schema cannot express. Event and error envelopes (Phase 3) are not yet
+written and are therefore not part of the freeze. Prompt records (`setspec.prompts`, Phase 5,
+added in 0.4.0) are shipped: prompt packs with their three content hashes and sandboxed
+rendering; they carry their own record schema version rather than joining the frozen payload types.
+See the [development plan](docs/packages/setspec/development-plan.md) for what each phase adds.
 
 Part of the **Local AI Suite**.
 

{setspec-0.4.0 → setspec-0.6.0}/README.md

@@ -2,18 +2,32 @@
 
 Every versioned data contract that crosses an application boundary: benchmark results, capability evidence, event/error envelopes, prompt records.
 
-**Status:** `0.3.0` — Phases 1–2, 3A and 4 complete, and **the v1.0 contracts are frozen.** Eight
-payload types are published at `1.0` — `model.identity`, `machine.profile`, `benchmark.result`,
-`benchmark.run_summary`, `capability.evidence`, `benchmark.evidence_bundle`,
+**Status:** `0.6.0` — Phases 1–2, 3A, 4, 5, 6 and 7 complete, and **the v1.0 contracts are frozen**,
+with two additive minors now published on top of that freeze. Six payload types remain frozen at
+`1.0` only — `model.identity`, `machine.profile`, `benchmark.result`, `benchmark.run_summary`,
 `benchmark.goal_pack` and `benchmark.calibration_report` — each with generated JSON Schema and at
 least three golden payloads shipped as package data. `setspec.DRAFT_SCHEMAS` is empty, which is
 where the freeze is readable at runtime rather than only stated here; from now on a new optional
 field is a minor bump and anything else is a major, enforced by a snapshot diff in CI.
 
+Phase 6 (the adapter arc's LA0 checkpoint) adds three things without touching any of the above:
+`capability.evidence` gains an additive `1.1` (an optional `adapter` field, absent — and
+byte-identical to `1.0` — on every record with no adapter); `model.adapter_manifest` `1.0`
+publishes the operator-reviewed record behind one adapter; and `governance.egress_decision` `1.0`
+is the package's first payload under a root other than `benchmark`/`capability`/`machine`/`model`,
+carrying a recorded egress verdict for a reader that has Commissioner installed or not. Phase 7
+carries that same minor one payload out: `benchmark.evidence_bundle` gains its own additive `1.1`,
+nesting `capability.evidence` `1.1` in place of the `1.0` element type its frozen `1.0` still
+nests, so an exported bundle can now carry adapter-bearing evidence — absent any adapter,
+byte-identical to `1.0`. `capability.evidence` and `benchmark.evidence_bundle` are therefore the
+two payload types with a second published minor; every other payload type remains exactly `1.0`.
+
 The [schema catalogue](docs/schemas.md) lists every payload type, its artifacts, and the
-cross-field rules the JSON Schema cannot express. Event and error envelopes (Phase 3) and prompt
-records (Phase 5) are not yet written and are therefore not part of the freeze. See the
-[development plan](docs/packages/setspec/development-plan.md) for what each phase adds.
+cross-field rules the JSON Schema cannot express. Event and error envelopes (Phase 3) are not yet
+written and are therefore not part of the freeze. Prompt records (`setspec.prompts`, Phase 5,
+added in 0.4.0) are shipped: prompt packs with their three content hashes and sandboxed
+rendering; they carry their own record schema version rather than joining the frozen payload types.
+See the [development plan](docs/packages/setspec/development-plan.md) for what each phase adds.
 
 Part of the **Local AI Suite**.