aip

Approved General AIPs are normative. draft AIP-162 and reviewing AIP-182 are advisory; label them as such.

Workflow

1. Read the proposed surface and nearby APIs; classify management versus data plane.
2. Walk all 72 Use when entries in REFERENCE.md. Record each AIP as selected or excluded; never apply every AIP blindly.
3. Open the official https://google.aip.dev/{number} page for every applicable AIP. Never cite the local index as evidence. Compare applicable-row URLs with the research trace and fetch every gap.
4. Resolve conflicts by approved AIP, documented compatibility need, then precedent exception. Mark necessary exceptions aip.dev/not-precedent with rationale.
5. Derive a change-specific checklist for proto/HTTP shape, behavior, errors, lifecycle, compatibility, docs, and client ergonomics.
6. Preserve intended capability and wire compatibility unless version policy permits a break.
7. Run the repository's api-linter; it is a floor, not proof of conformance.
8. Report AIP | state | applicability | result | evidence/exception for each applicable AIP. List every exclusion separately and account for all 72 published numbers exactly once. Separate normative failures from advisory suggestions.

Baseline