The smallest relevant module doc and narrower playbook from .repo_context/index.md
Workflow
Classify the path: foreground request, metadata coordination, data transfer, background, test-only, or docs-only.
Decide whether the request is one coherent change. Split unrelated behavior, build edits, cleanup, and operator changes
unless they are required for the same deliverable.
Identify high-risk surfaces and owners before coding: shared internal APIs, public APIs, language bindings, RPC,
Bazel/CMake, K8s/Helm, persistence, recovery, concurrency, hot paths, and security boundaries.
Choose risk-based validation evidence before implementation, including whether the change needs targeted tests,
build-system checks, perf evidence, sanitizer/stress coverage, recovery tests, or config/operator validation.
Search for existing helpers before adding logic.
Before editing, run the pre-change checklist in .repo_context/playbooks/features/infra-engineering-workflow.md.
Treat shared internal APIs as semi-public contracts: check naming clarity, one recommended usage style, misuse
prevention, ownership/lifetime semantics, hot-path argument cost, module locatability, and production diagnosability.
For behavior, config, packaging, or operator changes, record default behavior, rollout, rollback, compatibility, and
health-signal expectations.
For production bug fixes, connect symptom, trigger condition, root cause, fix point, regression guard, and prevention
signal before declaring the implementation complete.
