docs: adopt AI agent harness
This commit is contained in:
26
.agent/profile.yml
Normal file
26
.agent/profile.yml
Normal file
@@ -0,0 +1,26 @@
|
||||
schema_version: 1
|
||||
|
||||
project:
|
||||
id: asp-intranet
|
||||
name: ASP Intranet
|
||||
type: internal-service
|
||||
layer: fullstack
|
||||
legacy: true
|
||||
|
||||
stack:
|
||||
- classic-asp
|
||||
|
||||
databases:
|
||||
- id: intranet
|
||||
engine: mssql
|
||||
role: primary-intranet-data
|
||||
access: read-write
|
||||
|
||||
migration:
|
||||
status: planned
|
||||
target_stack:
|
||||
- typescript
|
||||
- react
|
||||
- nextjs
|
||||
- java-springboot
|
||||
strategy: staged
|
||||
27
.agent/project.md
Normal file
27
.agent/project.md
Normal file
@@ -0,0 +1,27 @@
|
||||
## ASP Intranet Repository Rules
|
||||
|
||||
### Repository Role and Current Authority
|
||||
|
||||
- This is the legacy Classic ASP intranet application covering approval, business, contact, cost, knowledge, management, project, statistics, and related employee workflows.
|
||||
- Preserve current routes, includes, sessions, authentication, authorization, form fields, redirects, document links, uploads, and MSSQL behavior while the application remains in service.
|
||||
- Treat employee, organization, contact, approval, cost, and uploaded-document data as sensitive internal information. Minimize exposure in logs, errors, fixtures, and completion reports.
|
||||
- Do not modernize multiple business areas or shared libraries as a side effect of a narrow maintenance task.
|
||||
|
||||
### Encoding and File Safety
|
||||
|
||||
- Most ASP files in this repository are not UTF-8. Treat CP949/EUC-KR-family encoding and CRLF as the likely legacy contract, but verify each touched file rather than applying a repository-wide assumption.
|
||||
- Never normalize the repository to UTF-8 or rewrite a broad include tree. Preserve each file's bytes, BOM state, line endings, response code page, and charset behavior.
|
||||
- Do not use a UTF-8-only formatter or patching workflow on a legacy file. Inspect the byte-level diff and Korean text after every approved ASP change.
|
||||
- Large document and image collections are business artifacts, not automatic refactoring or formatting targets.
|
||||
|
||||
### Data and Migration Direction
|
||||
|
||||
- Trace include chains and shared DB helpers before changing SQL, authentication, authorization, or session behavior.
|
||||
- Parameterize new or changed values while preserving ADO parameter order, types, result shapes, transactions, null behavior, and ordering.
|
||||
- The approved long-term destination is a Spring Boot backend and Next.js/TypeScript frontend migrated by bounded business workflow.
|
||||
- Establish behavior, data, document, permission, rollout, and rollback baselines before replacing a legacy workflow.
|
||||
|
||||
### Harness and Verification
|
||||
|
||||
- `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files.
|
||||
- Do not start IIS, connect to a real database, submit approval or business data, or modify uploaded documents during validation without separate approval.
|
||||
Reference in New Issue
Block a user