---
# ─────────────────────────────────────────────────────────────────────────────
#  .github/instructions/payments.instructions.md  ·  PATH-SCOPED instructions
#  QRefAI AI Coding Field Guide, Part 3 (Q3.1)
#
#  Path-scoped instruction files apply ONLY to files matching the `applyTo` glob
#  in this frontmatter. This works for the Copilot cloud agent, code review, and
#  IDE chat (VS Code / Visual Studio). Use these for rules that are true for a
#  SUBTREE but not the whole repo — keeping copilot-instructions.md lean.
#
#  Ship one of these per domain/area. The glob is the whole point: scope tightly.
# ─────────────────────────────────────────────────────────────────────────────
applyTo: "internal/payments/**/*.go"
---

- All monetary values are int64 minor units; never floats.
- Every transaction mutation must call `audit.Emit()`.
- New payment endpoints require sign-off from the payments team.

<!--
  AUTHORING NOTES (delete before shipping):

  • applyTo takes a glob. Examples:
      "internal/payments/**/*.go"     a single subtree, one language
      "**/*.tsx"                       all React components, repo-wide
      "{api,services}/**"              multiple roots via brace expansion

  • Keep the body to rules that ONLY make sense for this scope. Anything true
    repo-wide belongs in copilot-instructions.md, not here.

  • These compose with copilot-instructions.md — they don't replace it. A file
    under internal/payments/ gets BOTH the repo-wide rules and these.

  • Make as many of these as you have distinct areas (payments, auth, infra,
    frontend…). One file per area keeps ownership clear.
-->