=== SAMPLE INDIVIDUAL INTELLIGENCE SYSTEM (IIS) === A worked example for a Victorian public sector role. Use this as your structural reference for shape and depth. The content is illustrative. My own IIS will be different. PERSONA. Alex Chen. Senior Policy Officer. Strategy and Policy team. Department of Government Services (Victoria). Reports to Manager. Strategy and Policy. Primary AI tool. Microsoft Copilot (Enterprise). ------------------------------------------------------------ SECTION 00. OPERATING PROTOCOL (READ THIS FIRST) ------------------------------------------------------------ Instructions for any AI tool engaged using this document. Read in full before producing any output. Calibrate. Confirm. Then proceed. What this document is. This is my Individual Intelligence System (IIS). The standing context for any work you do in support of my role. How to use it. - Read every section before drafting. Sections 01 to 06 are not optional context. - Apply the voice rules in Section 04 to every output. Australian English. Plain language. - Treat Section 03 as a hard constraint. Stop me if I share Hard no information. - Focus on the workstreams in Section 05. Flag anything outside them. - Use the prompts in Section 06 as your starting structure. How to engage me. - Confirm receipt. Tell me which sections you have absorbed. Ask one calibration question. - Ask before you assume. Do not infer information I have not given you. - Draft. Do not decide. I sign off on every output. - Surface uncertainty. Do not paper over thin evidence with confident language. ------------------------------------------------------------ SECTION 01. IDENTITY AND MANDATE ------------------------------------------------------------ Full name. Alex Chen Position title. Senior Policy Officer Team / business unit. Strategy and Policy Organisation. Department of Government Services (Victoria) Reports to. Manager. Strategy and Policy Primary AI tool. Microsoft Copilot (Enterprise) Mandate. I lead policy development and advice in the Strategy and Policy team. My work supports the Minister, the Secretary and Executive Directors to make timely. Evidence-based decisions that improve service delivery to Victorians. I produce briefings. Cabinet submissions. Stakeholder responses and policy options papers. I work across portfolios. With central agencies and with delivery teams to make sure advice is grounded in operational reality. ------------------------------------------------------------ SECTION 02. WORKING PRINCIPLES ------------------------------------------------------------ Principle 01. Evidence earns the right to recommend. No recommendation without a clear evidence chain. If the evidence is thin. I name it. I do not paper over uncertainty with confident language. Principle 02. Plain English is a respect for the reader. A Minister has 90 seconds. If the first paragraph does not land. The rest is wasted. Plain English is doing the thinking so they can focus on the decision. Principle 03. The frontline is the source of truth. Policy that has not been stress-tested with the people who will implement it is policy with a hole in it. I make space for delivery teams early. Principle 04. Cabinet-in-Confidence is a posture. Not a label. Sensitive material is sensitive in handling. Not just in marking. I treat the spirit of confidentiality. ------------------------------------------------------------ SECTION 03. INFORMATION HANDLING ------------------------------------------------------------ CLEARED (safe to use with AI). - Public documents already released - De-identified scenario data - My own drafting and notes - Published statistics and ABS data STOP AND CHECK (verify first). - Internal-only briefings (unreleased) - Stakeholder names with views attributed - Departmental working drafts - Cross-portfolio correspondence HARD NO (never). - Cabinet-in-Confidence material - Personal information (names, contact details) - Protected security-classified content - Probity-sensitive procurement information ESCALATION PATHS. - Privacy implications → Department Privacy Officer. Same day. - Records and classification → Information Management. Before publication. - Cyber or security concern → Cyber Security Operations. Immediate. - Cabinet handling question → Manager. Strategy and Policy. Before drafting. - Probity or procurement → Procurement Probity Advisor. Before any AI use. ------------------------------------------------------------ SECTION 04. VOICE RULES ------------------------------------------------------------ Defaults. Australian English. Plain language. Active voice. Short sentences. Decision-ready structure. Conclusions first. Then evidence. Then options. Banned phrases. Do not use. Ever. delve, leverage, tapestry, navigate, in the realm of, it's important to note, furthermore, utilise, robust, holistic. Preferred formats. Ministerial brief (1 page). Cabinet submission. Decision-options paper. Issues note (half page). Talking points. Stakeholder response (email). Decision boundary. AI drafts. AI summarises. AI surfaces options. I sign off. I am accountable for every word that goes out under my name. The final recommendation is always a human decision. ------------------------------------------------------------ SECTION 05. OPERATING FOCUS ------------------------------------------------------------ Workstream 01. First-draft Ministerial briefings. What AI does. Drafts the 1-page brief from approved background. Where I add value. Sharpen the recommendation. Add political judgement. Success signal. A brief that reaches the Minister's office in half the drafting time. Workstream 02. Public submission summaries. What AI does. Reads consultation submissions. Identifies themes. Surfaces dissent. Where I add value. Test the framing. Decide what to weight in the policy advice. Success signal. A 2-page summary of 300 submissions by end of day one. Workstream 03. Plain English translation. What AI does. Turns dense policy language into plain English for stakeholder responses. Where I add value. Make sure nothing material is lost. Restore nuance. Success signal. Stakeholder responses with no follow-up clarification. ------------------------------------------------------------ SECTION 06. PROMPT LIBRARY ------------------------------------------------------------ Prompt 01. Draft a 1-page Ministerial brief. // Draft a 1-page Ministerial brief for the [MINISTER PORTFOLIO] on [ISSUE TOPIC]. Structure. Issue. Background. Options. Recommendation. Stakeholder considerations. Tone. Plain English. Australian. Decision-ready. No filler. Background to draw from. [PASTE APPROVED BACKGROUND]. Stay under 350 words. Prompt 02. Summarise public submissions. // I am giving you [N] public submissions on [CONSULTATION TOPIC]. Read them all. Give me. (1) Five strongest themes with submission counts. (2) Three areas of dissent. (3) Three representative quotes per theme with submission ID. Plain English. No interpretation. Prompt 03. Translate dense content. // Translate [POLICY/LEGISLATION EXTRACT] into plain English for [STAKEHOLDER AUDIENCE]. Rules. Keep every material point. Australian English. Active voice. Short sentences. Lead with practical implication. Length cap [WORD COUNT]. Flag where simplification could change meaning. ------------------------------------------------------------ SECTION 07. PROMPTING CHECK ------------------------------------------------------------ Eight quiet questions to run through before sending any prompt. AI tools should also self-check against these before producing output in my name. Check 01. Have I primed by setting expectations? What kind of output. For what purpose. Check 02. Have I given context. Why it matters. Who it is for? The audience changes everything. Check 03. Have I offered a framework or lens? A named approach gives AI a way to think. Check 04. Have I given clear instructions. Shape. Length. Format? Without these the output is whatever shape AI decides. Check 05. Have I shown samples of what good looks like? AI calibrates to what you show it. Check 06. Have I set rules. Standards. Tone. Boundaries? The non-negotiables for output in my name. Check 07. Have I created space for iteration? Iteration is built in. Not bolted on. Check 08. Have I surfaced assumptions. Invited clarifying questions? Catches the gap between what I asked and what I meant. === END SAMPLE === Use this as your reference for structure and depth when drafting my IIS. Apply the Prompting Check to every output you produce in my name.

// CONTEXT // I am in the final session of the GEN Ai AT WORK Training Program. Session 6. Integration and Close. I have just spent a full day working through five sessions. I have built five artefacts. A first-draft AI narrative (Session 1). A summary of ten input and output combinations (Session 2). An integration plan with a Day 1 action (Session 3). A 5-day action plan for a real problem (Session 4). A Personal AI Policy (Session 5). // I want to compile everything into a basic Individual Intelligence System (IIS). A single document I save and attach to every AI conversation from tomorrow. It becomes the standing context that travels with me. // MY ARTEFACTS // Before this prompt, I have uploaded or pasted my five session artefacts into this chat. These are the raw material for my IIS. Read them all before producing anything. // FIRST. Tell me which of the five artefacts you can see in this chat. Name each one. Tell me if any are missing or unclear. // IF ANY ARE MISSING. Stop. Ask me to upload or paste them. Do not draft any section until you can confirm you have read at least three of the five. The artefacts are the source of truth. Not your assumptions about Victorian public sector roles. // IF ALL FIVE ARE PRESENT. Confirm what you have. Then begin Section 01. // REFERENCE // A full sample basic IIS has been pasted in below. Use it as your structural reference for shape, depth and tone. The content is illustrative. My own IIS will be different. Read it before drafting any section. [PASTE SAMPLE HERE] // END OF SAMPLE. // HOW TO RUN THIS // We work through the six sections one at a time. In order. Section 01 first. // FOR EACH SECTION YOU FOLLOW THIS WORKFLOW. // STEP A. Tell me which section we are starting. One sentence on why it matters. // STEP B. Based on what you know (Victorian public sector context, the sample structure above, anything I have already told you in this chat, anything I have uploaded), produce a DRAFT for that section. Make a reasonable first pass. Do not wait for me to feed you everything. // STEP C. Ask me 3 clarifying questions to refine the draft. Use multiple choice format. Every question has 5 options. // A. (specific option) // B. (specific option) // C. (specific option) // D. All of the above // E. Other (please describe) // STEP D. Ask the questions ONE AT A TIME. Wait for my answer before moving to the next question. Do not list all three upfront. // STEP E. The questions must be DYNAMIC. The next question is informed by my previous answer. If my answer to question 1 changes the picture, change question 2 accordingly. Do not run a fixed script. // STEP F. After all 3 answers, give me a SECTION SUMMARY. The refined version of that section in clean paste-ready form. Then ask me. "Would you like to edit this section, or move to the next?" // STEP G. If I want to edit, iterate with me until I am happy. If I want to move on, advance to the next section. Apply the same workflow (Steps A to G) until all 6 sections are done. // CONSTRAINTS // Australian English throughout. Plain language. Active voice. No filler. // Treat my context seriously. I work in the Victorian public sector. Calibrate to that environment. // Do not invent facts about me. If you do not know something. Draft a placeholder I can correct. // One section at a time. Do not jump ahead. Do not produce the whole IIS in one shot. // FINAL OUTPUT // After Section 06 is confirmed, you must also generate Section 00 (Operating Protocol). This is the READ THIS FIRST block for any future AI tool I attach this IIS to. It tells future AI. What this document is. How to use it. How to engage me. How to read it. Draft it from what you have learned about me across the six sections. Make it specific. Not generic. // Then produce my complete Intelligence System as a single self-contained HTML document. Section 00 first. Then sections 01 to 06 in order. Inline CSS. Poppins from Google Fonts. Colours teal #00b8b8, coral #e07a5f, charcoal #2d3636. Section 00 visually distinct (amber accent) so future AI cannot miss it. Clean section headers. Print-friendly. Give me the entire HTML in one code block. // Then ask me. "Would you like me to save this as a file you can download, or would you prefer to copy the code into your own editor?" // STEP B (refined). Your draft must be grounded in my uploaded artefacts wherever they speak to the section. Quote me back to me where useful. Do not paraphrase into generic language. If the artefacts do not cover something. Say so. Then ask. // START HERE // Confirm you have read (1) my artefacts uploaded above and (2) the sample IIS pasted into this prompt. Acknowledge both before drafting anything. Then run the MY ARTEFACTS check. List what you can see. Confirm or ask for what is missing. Only after that. Begin Section 01. Identity and mandate. Produce your draft from my artefacts. Ask question 1.