Skip to content

Publish hardened HTMLTrust standards drafts - #5

Merged
jt55401 merged 7 commits into
mainfrom
fix/protocol-hardening
Aug 27, 2026
Merged

Publish hardened HTMLTrust standards drafts#5
jt55401 merged 7 commits into
mainfrom
fix/protocol-hardening

Conversation

@jt55401

@jt55401 jt55401 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add the IETF wire-protocol draft, W3C browser-integration draft, rendered IETF artifacts, and security review dispositions
  • close parser, origin, signature encoding, key-document, failure-vocabulary, mutation, and directory-submission ambiguities
  • add reproducible vectors and top-down build, validation, preview, and paper guides
  • complete the research paper bibliography and extend CI to rebuild both standards drafts

Validation

  • make check
  • make ietf
  • make w3c-check
  • fresh 9-page paper build with pdflatex and biber; every rendered page inspected
  • endorsement Ed25519 signature, JCS hash, claim escaping, and origin vectors independently reproduced

jt55401 and others added 7 commits July 30, 2026 15:06
…ults

Replace the fictional canonicalization description (SimHash, attribute-sorting)
with the algorithm as actually specified and implemented; correct the
endorsement format, algorithm identifiers, and timestamp format to match the
draft; and turn "Planned Work" into an Implementation and Results section that
reports the Study 1 measurement on 5,146 real Common Crawl pages (byte-identical
agreement 20% -> 100% only when every binding runs one shared core; ~88-90%
cross-parser stability). Add an honest limitations discussion and an arXiv
submission kit.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jt55401
jt55401 merged commit 68d2d9d into main Aug 27, 2026
2 checks passed
@jt55401
jt55401 deleted the fix/protocol-hardening branch August 27, 2026 23:19
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