261013_01_ENH: 사업 분류에 4추가

This commit is contained in:
2026-10-13 14:59:46 +09:00
parent 25bacaad45
commit b4f08e9e3a
15 changed files with 420 additions and 67 deletions

View File

@@ -1,21 +1,18 @@
## GWCF Monitoring Backend Repository Rules
# GWCF Monitoring Backend Project Instruction Router
### Deliverable and Domain
## Required Project References
- 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.
Before each related task, read the current contents of every matching reference below, even if it was read earlier in the session.
### Data, File, and Integration Safety
| Task scope | Required reference |
|---|---|
| Any substantive analysis, planning, implementation, debugging, review, or documentation work in this repository | `.agent/references/repository-rules.md` |
- 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.
If a task spans multiple scopes, read every matching reference. Do not assume remembered content is current.
### Shared Library and Verification
## Harness Workflow
- 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.
- `AGENTS.md` and `CLAUDE.md` are generated outputs. Never edit them directly.
- Edit `.agent/project.md` only when routing changes. Store durable project detail in `.agent/references/`.
- A reference-only content change does not require recomposition when its route is unchanged. Run harness verification to validate routing and UTF-8.
- Recompose and verify after changing `.agent/project.md`, `.agent/profile.yml`, or another composed instruction source.

View File

@@ -0,0 +1,21 @@
## 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.