docs(agents): the manifest shape is also a provenance signal #40

Merged
jlxq0 merged 1 commit from docs/manifest-shape-as-provenance into main 2026-09-01 18:14:39 +00:00
Owner

A second use for the index-versus-single-manifest fact, beside avoiding a false rollback. Refs #14. Docs only, no version bump.

Every image this repository's CI builds is an index, because the buildctl path attaches an attestation. So a single-manifest jmap-mcp image did not come out of .forgejo/workflows/ci.yml.

v0.2.5 and v0.2.6 are single manifests, which is a third independent signal beside:

  • no OCI labels, so no org.opencontainers.image.revision to read
  • no Actions run that could have built them: six tasks on 2026-08-16, all cargo, all failure, no docker job at all

None of the three shares a failure mode with the others, which is what makes them corroboration rather than one observation counted three times.

Gate: cargo +1.93.0 fmt --all --check rc=0, cargo +1.93.0 test --all-features --locked rc=0, 197 passed.

A second use for the index-versus-single-manifest fact, beside avoiding a false rollback. Refs #14. Docs only, no version bump. Every image this repository's CI builds is an **index**, because the `buildctl` path attaches an attestation. So a **single-manifest** `jmap-mcp` image did not come out of `.forgejo/workflows/ci.yml`. `v0.2.5` and `v0.2.6` are single manifests, which is a **third independent signal** beside: - no OCI labels, so no `org.opencontainers.image.revision` to read - no Actions run that could have built them: six tasks on 2026-08-16, all `cargo`, all `failure`, no `docker` job at all None of the three shares a failure mode with the others, which is what makes them corroboration rather than one observation counted three times. Gate: `cargo +1.93.0 fmt --all --check` rc=0, `cargo +1.93.0 test --all-features --locked` rc=0, 197 passed.
docs(agents): the manifest shape is also a provenance signal
All checks were successful
CI / tag-ancestry (pull_request) Successful in 3s
CI / cargo (pull_request) Successful in 56s
CI / docker (pull_request) Successful in 14s
75c6d7e10d
Every image this repository's CI builds is an index, because the buildctl path
attaches an attestation. So a single-manifest jmap-mcp image did not come out of
.forgejo/workflows/ci.yml.

v0.2.5 and v0.2.6 are single manifests. That is a third independent signal
beside their absent OCI labels and the absence of any Actions run that could
have built them, and none of the three shares a failure mode with the others,
which is what makes them corroboration rather than one observation counted three
times.

A second use for the index-versus-single-manifest fact, beside avoiding a false
rollback.

Refs #14

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jlxq0 merged commit f0b67d5f30 into main 2026-09-01 18:14:39 +00:00
jlxq0 deleted branch docs/manifest-shape-as-provenance 2026-09-01 18:14:40 +00:00
Sign in to join this conversation.
No reviewers
No labels
waiting-on-julian
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jlxq0/jmap-mcp!40
No description provided.