Files
gwcf-review-back/.agent/references/repository-rules.md

1.8 KiB

GWCF Monitoring Backend Repository Rules

Deliverable and Domain

  • This Spring Boot backend manages GWCF performance records, monitoring assignments, schedules, visits, reviews, users, codes, files, templates, and event history.
  • Its operational character is similar to KriContact, but its API, data, permissions, and deliverables remain project-specific contracts.
  • Treat approved planning material and acceptance criteria as the scope boundary. Preserve assignment, confirmation, monitoring, visit, review, and user workflow state transitions.

Data, File, and Integration Safety

  • Preserve organization, performance, user, assignment, and role authorization boundaries for every query and mutation.
  • Treat Excel uploads/downloads, review templates, PDF conversion, visit files, and stored paths as sensitive file-lifecycle operations. Validate names, paths, sizes, types, cleanup, and partial failures.
  • Keep MySQL JPA/QueryDSL persistence separate from the read-only KON MSSQL/MyBatis integration. Do not mix dialects, transactions, entities, or mapper assumptions.
  • Make retries and duplicate submissions safe for assignment, confirmation, visit, upload, and review operations.
  • Do not expose personal information, monitoring details, customer documents, raw file paths, or unrestricted event logs.

Shared Library and Verification

  • Consume com.kri.common:starter:beta.1.6.3 and use public com.kri.common.feature.* APIs. Do not duplicate a KriCommon feature locally.
  • AGENTS.md and CLAUDE.md are generated. Edit .agent/profile.yml or .agent/project.md, then recompose instead of editing generated files.
  • Use the Gradle Wrapper and narrow safe checks. Do not connect to real databases, run the PDF converter, or process customer files during validation without separate approval.