Skip to content

docs: cite platform-ceremonies 4.1 for the attested-data bytes - #23

Merged
xgreenx merged 2 commits into
mainfrom
docs/attested-data-citation
Oct 5, 2026
Merged

xgreenx merged 2 commits into
mainfrom
docs/attested-data-citation

Conversation

@xgreenx

@xgreenx xgreenx commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Three comments cite ceremony-common §9.1 for the attested-data bytes; §9.1 holds verification and fee rules, the byte format is platform-ceremonies §4.1 "Attested data", added by libid-org/libID#112.

Changes

  • src/jwks/mod.rs:23: NotarizedSession doc cites platform-ceremonies section 4.1.
  • src/proof.rs:5: module doc cites platform-ceremonies section 4.1.
  • tests/e2e_real.rs:140: created_at doc cites platform-ceremonies section 4.1.
  • Rewrap: "section 4.1" stays on one line, so grep 'section 4.1' finds all three.

Verified

  • Bytes 32..40 big-endian createdAt matches libid-transcript v0.6.0 (the Cargo.lock pin) and the §4.1 table on docs(specs): define the attested-data format X and GitHub pin libID#112.
  • No other §9.1 citation left in src, tests, README.md.
  • cargo +nightly-2026-08-10 fmt --all -- --check and cargo build --all-targets pass.
  • Comment-only diff; Rust skill rules checked: comments carry the why only, describe the thing.

Not verified / known issues

🤖 Generated with Claude Code

Ceremony-common section 9.1 holds the attestation verification and fee
rules and fixes no byte layout. The attested-data format the notary
signs and GoogleJwtRoots.rotate decodes is platform-ceremonies section
4.1, "Attested data".

Assisted-by: Claude Opus 5.5
Signed-off-by: xgreenx <xgreenx9999@gmail.com>
A citation split across a line break escapes `grep 'section 4.1'`, so
a later sweep of spec references would miss two of the three.

Assisted-by: Claude Opus 5.5
Signed-off-by: xgreenx <xgreenx9999@gmail.com>
@xgreenx
xgreenx merged commit 026c642 into main Oct 5, 2026
4 checks passed
@xgreenx
xgreenx deleted the docs/attested-data-citation branch October 5, 2026 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant