Azure/GPT-RAG

architecture-decision

Conducts and records a verifiable GPT-RAG architectural decision. Use when a choice alters repositories, boundaries, contracts, identity, data, deployment topology, or operation with meaningful reversal cost.

documentation-consistency

Keeps GPT-RAG user and operator documentation aligned with shipped behavior. Use for features, configuration keys, deployment parameters, defaults, component pins, operations, or breaking changes.

engineering-principles

GPT-RAG architecture and implementation principles. Use for design, review, meaningful refactoring, Azure integration, security, testing, or operational changes.

multi-repo-release

Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.