feat(spec): add the optional origin block, and stop software-only meaning two things

[imran-siddique]

Prerequisite for the third-party control-plane adapters (response plan list 2, item 3). Ships as 0.7.0.

The problem

runtime.platform: "software-only" is the honest value in two situations that are not the same claim:

• a dev-mode record, unattested because nothing attested it;
• a record transcribed from another vendor's control plane, unattested because the party asserting the evidence also wrote the log.

A consumer weighing a record cannot tell those apart from platform alone. That gap is about to become load-bearing: an adapter that emits a record indistinguishable from a dev-mode one destroys the argument the adapters exist to make.

The block

"origin": {
  "kind": "third-party-control-plane",
  "producer": "vendor-gateway/2.1",
  "source_event_id": "evt-7f3a",
  "ingested_at": 1760000000
}

Optional and additive, under the same v0.2 profile URI. Same shape of change as delegation in 0.4.0: existing records stay valid, and absence means self, so every hardware profile in the spec is unaffected.

kind is a closed set (self, third-party-control-plane, log-import) rather than free text, because the entire value of the field is that a verifier can key on it.

The rule that makes it worth having

A record whose kind is not self MUST carry runtime.platform: "software-only".

An importer holding someone else's log has no quote to present, so a hardware platform value there is untrue rather than stronger. It is also precisely what an adapter produces by starting from a hardware example and editing the fields it understood, which is why it is a MUST.

Enforced in two places so they cannot drift, and tested from both directions in each:

• models.py, a cross-field model_validator;
• schema/trace-claim.json and the packaged schema, via if/then, so a validator that never loads the Python rejects it too.

What it does not do

It launders assurance in neither direction. Naming your producer does not make unattested evidence attested. A record with a verified hardware quote is what it is whether or not it says origin: self.

Also here

docs/schema.md still described transparency as required, with an empty string for unanchored records. 0.5.1 made it optional below Level 2 and rejects "".

Checks

202 passed, 1 skipped. ruff clean, mypy clean. 11 new tests across the model and the schema.

Note for downstreams: TrustRecord is extra="forbid", so a verifier older than 0.7.0 rejects a record carrying origin, the same one-directional break cmcp took with gateway.attestation_evidence. Producers should not emit origin until their consumers are on 0.7.0.

🤖 Generated with Claude Code