Skip to content

Revise README for Consent-Aware HTTP Framework#25

Merged
hyperpolymath merged 1 commit intomainfrom
hyperpolymath-patch-1
Mar 26, 2026
Merged

Revise README for Consent-Aware HTTP Framework#25
hyperpolymath merged 1 commit intomainfrom
hyperpolymath-patch-1

Conversation

@hyperpolymath
Copy link
Owner

Updated the README to reflect new framework name and author, and revised content for clarity and structure.

Updated the README to reflect new framework name and author, and revised content for clarity and structure.

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
@hyperpolymath hyperpolymath merged commit 207e56c into main Mar 26, 2026
15 of 17 checks passed
@hyperpolymath hyperpolymath deleted the hyperpolymath-patch-1 branch March 26, 2026 22:27
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6c83cb27ac

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

== License

See link:RSR-COMPLIANCE.md[RSR-COMPLIANCE.md] for Rhodium Standard Repository compliance status.
See IETF Trust Legal Provisions (BCP 78 and BCP 79).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore accurate license attribution in README

The README now tells readers to use IETF Trust Legal Provisions for licensing, but the repository’s actual license artifacts define different terms (e.g., the root LICENSE file). This can cause adopters and distributors to apply the wrong legal obligations, which is a material compliance regression.

Useful? React with 👍 / 👎.

Comment on lines +81 to +85
/http-430/ HTTP 430 Consent Required
/agent-identification/ AI Agent Identification Protocol
/content-provenance/ Content Provenance Protocol
/compliance-reporting/ AI Compliance Reporting Framework
/consent-management/ Web Consent Management Protocol (planned / draft)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge List only existing paths in repository structure

This structure map enumerates top-level directories that do not exist in the current repository (for example /http-430/, /agent-identification/, and /content-provenance/). Contributors using this section to navigate will be sent to dead paths, so the section should either match the real tree or clearly mark entries as future-only.

Useful? React with 👍 / 👎.

* Ethical AI practitioners
* IETF working groups
* Journalism ethics communities
All components are currently Internet-Drafts (Work in Progress).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Avoid overstating draft status for all components

The status text claims all framework components are currently Internet-Drafts, but this repo only contains draft files for a subset of the protocols described earlier. That mismatch overstates publication maturity and can mislead readers evaluating what has actually been drafted.

Useful? React with 👍 / 👎.

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