Documentation menu

AHP-NNNN: Short descriptive title

  • Status: Draft
  • Authors: GitHub handles or names
  • Tracking issue: Link
  • Created: YYYY-MM-DD
  • Review period: Not started
  • Supersedes: None
  • Superseded by: None

Summary

State the decision in a few sentences.

Motivation

Describe the problem, affected users or implementers, and why the current protocol or process is insufficient. Include evidence where available.

Goals and non-goals

List what this proposal intends to achieve and what it intentionally leaves out.

Proposal

Describe the behavior or policy precisely enough to evaluate. Identify which material would become normative and which supporting material remains non-normative.

The protocol is language-neutral. Do not define normative behavior only in source code or in terms of one language, runtime, framework, or SDK. All SDKs and implementations, including TypeScript SDKs, are non-normative.

Compatibility and interoperability

Explain effects on existing producers, consumers, tools, schemas, deployments, and protocol versions. Identify breaking changes, migration needs, and mixed-version behavior.

Security, privacy, and operational impact

Describe new trust boundaries, misuse cases, data exposure, resource costs, deployment concerns, and mitigations. Write No known impact only after considering each area.

Do not put undisclosed vulnerability details in a public proposal. Follow the Security policy instead.

Alternatives considered

Describe credible alternatives, including doing nothing, and explain the trade-offs.

Rollout, release, and deprecation

State the expected version impact, implementation sequence, validation, deprecation period, and rollback approach. Acceptance of this proposal does not itself create a release.

Unresolved questions

List questions that must be answered before decision, or state None.

Decision record

Complete this section when the proposal is decided.

  • Decision date: YYYY-MM-DD
  • Outcome: Accepted, Rejected, Withdrawn, or Superseded
  • Deciding maintainers: GitHub handles
  • Recusals: None or GitHub handles with a non-sensitive reason
  • Rationale: Concise explanation
  • Unresolved objections: Summary or None
  • Required follow-up: Links or None