Skip to content

Conciseness pass: −380 lines, no normative change - #100

Open
dickhardt wants to merge 9 commits into
issue-batch-2026-08from
conciseness-cuts
Open

Conciseness pass: −380 lines, no normative change#100
dickhardt wants to merge 9 commits into
issue-batch-2026-08from
conciseness-cuts

Conversation

@dickhardt

Copy link
Copy Markdown
Owner

Based on #99 — review that first; this diff is everything after it.

Protocol draft goes from 3,867 lines (after #99) to 3,444. Every cut is a second copy of a rule, a duplicate example, or rationale that already existed elsewhere; per review decisions, Document History is untouched (it gains bullets for the batch instead). One commit per bucket:

  • Overview (−152): one paragraph per access mode instead of a walkthrough that re-specified each; the mode table, parties diagram, and the three- and four-party ladders stay; the mission creation/context/completion diagrams and Bootstrapping (all forward references) go. The PS's direct-channel sentence moved to Agent Governance; agent–person association was already in Agent-Person Binding.
  • Introduction (−31): the 12-bullet feature list and its 3-bullet negation; Why Not Extend OAuth? (now anchored) carries the OAuth argument.
  • Signature-header boilerplate (−47): 15 examples now show Signature-Key plus a one-line pointer; the canonical fully bound request in the signatures profile keeps complete headers.
  • Metadata (−53): per-role field lists carry only role-specific fields; the common-fields table was already normative.
  • 202 examples + clarification variants (−82): four identical 202 requirement=interaction blocks become references to the two defining sections; three clarification HTTP examples become one with body variants. Also fixes a stale agent claim recital the -11 pivot missed.
  • Design Rationale (−28): mission-hash, refresh-token, and downstream-scope arguments now appear once (body copy survives, each appendix-only clause grafted in); five one-sentence subsections merge into an In Brief list.
  • Security Considerations (−21): micro-sections merged with every MUST intact; Call Chaining Identity and Token Revocation and Lifecycle deleted as verbatim duplicates of normative text.
  • Section merges (−36): aud rule stated once; the three requirement challenges now adjacent with AAuth-Access/Resource-Managed following; Endpoint/Other URLs merged; Organization Visibility folded into PS-AS Collapse.

Anchors kept or newly added where content moved (#overview-*, #requirement-interaction, #ps-to-as-token-request, #why-not-extend-oauth); mmark + xml2rfc build clean with no unresolved references.

Not taken (from the audit, by decision or judgment): Document History (−40, per review), PS endpoint example body trims (−15, the examples earn their space).

🤖 Generated with Claude Code

https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k

dickhardt and others added 9 commits August 14, 2026 18:19
…strapping

The Protocol Overview walked through every access mode and every
mission operation in detail before the normative sections did the
same. The mode table, parties diagram, and the three-party and
four-party ladders stay; the three trivial ladders (one request, one
response) and the mission creation/context/completion diagrams go —
each duplicated a normative section. The three-party paragraph
restated the aud rule, the authorization_endpoint-or-401 fork, and
the identity-claims list, each of which appears three to five times
elsewhere.

Bootstrapping is deleted: every bullet was a forward reference. Its
two pieces of unique content survive — the PS's optional direct
channel to the person moved to Agent Governance, and the agent-person
association was already covered by Agent-Person Binding.

Part of the conciseness pass; no normative content removed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
What AAuth Provides was a 12-bullet restatement of the Protocol
Overview, and What AAuth Does Not Do restated three of those bullets
negatively. The client-identity argument keeps its two-paragraph core
and points at Why Not Extend OAuth? (now anchored) for the long form.

Part of the conciseness pass; no normative content removed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
The nine common fields are defined once in the common-fields table;
the four per-role sections re-listed them as bullets with the same
wording, including the sanitize-Markdown MUST four times. The examples
still show them; the bullets now carry only role-specific fields and
divergences (AP's issuer doubling as the agent-identifier domain, the
resource's conditional jwks_uri).

Part of the conciseness pass; no normative content removed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
Fifteen HTTP examples carried the same Content-Digest /
Signature-Input / Signature block. The canonical fully bound request
in the HTTP Message Signatures profile keeps the complete headers;
every other example shows Signature-Key (the credential being
presented, which is the point of each example) plus a one-line pointer
to the profile.

Part of the conciseness pass; no normative content removed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
…variants

Four structurally identical 202+requirement=interaction example
blocks reduced to cross-references at the two defining sections
(Interaction Required, now anchored, and Pending Response). The three
clarification response subsections — three full HTTP requests
differing only in body — become one example with the three variants
as bullets. Also drops a stale reference to the removed agent claim
in the updated-request recital.

Part of the conciseness pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
The mission-hash, refresh-token, and downstream-scope rationales
appeared near-verbatim in both a body section and the appendix; the
body copy survives (grafting the one clause each appendix copy added).
The posture line in Why No Agent Identifier Reaches a Resource now
references PS-to-AS Token Request (newly anchored) instead of
repeating it. Five one-sentence subsections merge into an In Brief
list.

Part of the conciseness pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
Proof-of-Possession/Token Security and Pending URL/Clarification Chat
merge pairwise with every MUST intact. Call Chaining Identity and
Token Revocation and Lifecycle are deleted — both restated rules that
appear verbatim in Call Chaining and Token Revocation. The
layered-control argument now appears once (Token Revocation) with the
Policy Evaluation Points overview pointing at it, and the third-party
login start_path rationale rides on the normative parameter definition
instead of a second bullet.

Part of the conciseness pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
The resource token aud rule is stated once, in the section intro,
with Response with Resource Token pointing at it. The three
requirement challenges (agent-token, person-token, auth-token) now
sit adjacent, with AAuth-Access and Resource-Managed Authorization
following them, and the agent-token/auth-token contrast paragraph
reduced to its unique Accept-Signature-Scheme point. Endpoint URLs
and Other URLs merge into one subsection; Organization Visibility
(covered by the Roles org-wide bundle bullet) folds into PS-AS
Collapse; the second problem+json example goes.

Part of the conciseness pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01423n5qBejmzaktmbofnr5k
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