## Internal Service Project Rules - Internal-only usage does not reduce security, privacy, compatibility, or validation requirements. - Preserve authentication, authorization, role boundaries, auditability, and personal-data protections. - Identify affected user workflows before changing visible behavior. - Treat Frontend and Backend repositories as separate deployable systems with an explicit API contract between them. - Coordinate request, response, authentication, error, and versioning changes across both sides when the approved scope includes both repositories. - Do not silently require a simultaneous Frontend and Backend deployment. - Prefer backward-compatible transitions when deployments may occur independently. - Include migration and rollback considerations for database, API, and configuration changes. - Do not modernize legacy code as an unrelated side effect. - Apply Classic ASP text-safety rules only when the project profile declares the `classic-asp` stack. - Do not access or modify production data merely because the service is internal.