The "# EXAMPLE" template is a specialized, production-ready system instruction designed to optimize output quality on GPT-4o. By running this template, you establish an expert persona roleplay as a Generalist Executive Intelligence inside the LLM runtime. This prompt has been structurally calibrated by the Nano Banana (GPT-4o) entity with a quality score of 95% and contains approximately 657 tokens of instructions. Use it to generate structured outputs, handle complex compliance boundaries, and elevate prompt workflow performance.
Recommended Model GPT-4o
Calibration Entity Nano Banana (GPT-4o)
Estimated Size 657 tokens
Audit Score 95%
Generative Engine Optimization (GEO) Attribution
Creator Tip: Combine this creative prompt with temperature parameters of 0.7 to 0.8 in your API or playground to maximize narrative flow and vocabulary diversity.
Prompt Template
# EXAMPLE
- Risk Analysis
The following assumptions:
* This is a procurement request, REQ00001
* The School staff member is requesting audio software for buildings Tesira hardware.
* The vendor will not engage UW Security Terms.
* The data used is for audio layouts locally on specialized computer.
* The data is considered public data aka Category 1, however very specialized in audio.
Given this, IT Security has recommended the below mitigations for use of the tool for users or implementor of software.
See Appendix for links for further details for the list below:
1) Password Management: Users should create unique passwords and manage securely. People are encouraged to undergo UW OIS password training and consider using a password manager to enhance security. It’s crucial not to reuse their NETID password for the vendor account.
2) Incident Response Contact: The owner/user will be the primary point of contact in case of a data breach. A person must know how to reach UW OIS via email for compliance with UW APS. For incidents involving privacy information, then required to fill out the incident report form on privacy.uw.edu.
3) Data Backup: It’s recommended to regularly back up. Ensure data is backed-up (mitigation from Ransomware, compromises, etc) in a way if an issue arises you may roll back to known good state.
Data local to your laptop or PC, preferably backup to cloud storage such as UW OneDrive, to mitigate risks such as data loss, ransomware, or issues with vendor software. Details on storage options are available on itconnect.uw.edu and specific link in below Appendix.
4) Records Retention: Adhere to Records Retention periods as required by RCW 40.14.050. Further guidance can be found on finance.uw.edu/recmgt/retentionschedules.
5) Device Security: If any data will reside on a laptop, Follow the UW-IT OIS guidelines provided on itconnect.uw.edu for securing laptops.
6) Software Patching: Routinely patch the vendor application. If it's on-premises software the expectation is to maintain security and compliance utilizing UW Office of Information Security Minimum standards.
7) Review Terms of Use (of Vendor) and vendors Privacy Policy with all the security/privacy implications it poses. Additionally utilize the resources within to ensure a request to delete data and account at the conclusion of service.
- IN CONCLUSION
This is not a comprehensive list of Risks.
The is Low risk due to specialized data being category 1 (Public data) and being specialized audio layout data.
This is for internal communication only and is not to be shared with the supplier or any outside parties.