Spaces:
Sleeping
Sleeping
| """ | |
| Knowledge checks, one list per module, matched by position to MODULES in modules.py. | |
| Each question: prompt, options, answer (index into options), and why (shown when wrong). | |
| """ | |
| QUIZZES = [ | |
| # Module 1: AI at BOS | |
| [ | |
| { | |
| "q": "Which AI tool is approved for BOS and client information?", | |
| "options": [ | |
| "Any tool, as long as you delete the chat afterward", | |
| "The BOS Claude Enterprise account only", | |
| "Claude Enterprise or a personal ChatGPT account", | |
| "Whatever tool your manager prefers", | |
| ], | |
| "answer": 1, | |
| "why": "Company and client information goes into the BOS Claude Enterprise account and nowhere else. Personal accounts, free tools, and AI features in other apps have not been reviewed and cannot be defended in an audit.", | |
| }, | |
| { | |
| "q": "What does a large language model actually do?", | |
| "options": [ | |
| "Looks up verified facts in a database", | |
| "Produces the most plausible next text based on the conversation so far", | |
| "Connects to BOS systems automatically to find answers", | |
| "Records everything you type for the company", | |
| ], | |
| "answer": 1, | |
| "why": "A language model predicts plausible text from patterns it learned. It does not look up facts unless given a tool for that, and plausible is not the same as true.", | |
| }, | |
| { | |
| "q": "Which of these is the AI tool NOT good at without help?", | |
| "options": [ | |
| "Tightening the wording of a paragraph you wrote", | |
| "Summarizing a long document you attach", | |
| "Knowing BOS procedures, clients, and pricing on its own", | |
| "Laying out pros and cons of two approaches", | |
| ], | |
| "answer": 2, | |
| "why": "The model does not know anything about BOS, our clients, or our procedures unless you put that context into the conversation.", | |
| }, | |
| { | |
| "q": "Why did BOS standardize on one AI tool?", | |
| "options": [ | |
| "It was the cheapest option", | |
| "Data control, consistency, and compliance", | |
| "So IT could monitor every employee", | |
| "Because other tools do not work", | |
| ], | |
| "answer": 1, | |
| "why": "One approved tool puts our data under negotiated terms, lets IT support and configure it consistently, and gives us something we can defend in an audit.", | |
| }, | |
| ], | |
| # Module 2: How AI Works | |
| [ | |
| { | |
| "q": "The AI confidently gives you a statistic you did not provide. What should you do?", | |
| "options": [ | |
| "Use it, because the tool sounded confident", | |
| "Verify it against a real source before using it anywhere", | |
| "Ask the AI to confirm and then use it", | |
| "Round it to be safe", | |
| ], | |
| "answer": 1, | |
| "why": "Numbers the model produces on its own are the highest hallucination risk. Every figure needs a source you can point to. Asking the AI to confirm its own guess is not verification.", | |
| }, | |
| { | |
| "q": "What is the model's context?", | |
| "options": [ | |
| "Its knowledge of the whole internet", | |
| "Everything in the current conversation, including attachments", | |
| "The BOS company handbook", | |
| "Its memory of your past chats", | |
| ], | |
| "answer": 1, | |
| "why": "Context is everything the model can see in this conversation: your messages, its replies, and any files. That is its entire working knowledge for the chat.", | |
| }, | |
| { | |
| "q": "A long chat starts forgetting instructions you gave earlier. The most likely cause is:", | |
| "options": [ | |
| "The AI is broken and IT needs to restart it", | |
| "The context limit has pushed earlier material out of view", | |
| "Someone else is using your account", | |
| "The model updated overnight", | |
| ], | |
| "answer": 1, | |
| "why": "Context has a size limit. Long sessions and many attachments can push earlier material out. Start a fresh chat with a clean summary of where you are.", | |
| }, | |
| { | |
| "q": "Who is the authority on whether a camera works with the VirtuGuard platform?", | |
| "options": [ | |
| "The AI, if you describe the camera well", | |
| "The camera manufacturer's website", | |
| "The Immix integration matrix", | |
| "Whoever sold the camera", | |
| ], | |
| "answer": 2, | |
| "why": "Compatibility claims come from the Immix integration matrix, not from the AI's opinion or a vendor's marketing page.", | |
| }, | |
| ], | |
| # Module 3: First Conversations | |
| [ | |
| { | |
| "q": "Which request is most likely to produce something you can actually send?", | |
| "options": [ | |
| "Write an email", | |
| "Write a short email to a non technical property manager explaining that a scheduled camera check moved from Tuesday to Thursday", | |
| "Email about the camera thing", | |
| "Write something professional", | |
| ], | |
| "answer": 1, | |
| "why": "Good requests carry context, specifics, and material. Who it is for, what it is about, and how long it should be all change the result.", | |
| }, | |
| { | |
| "q": "The first answer is not quite right. What do experienced users do?", | |
| "options": [ | |
| "Start over in a new chat with the same request", | |
| "Accept it and fix it by hand", | |
| "Tell the tool what to change and iterate two or three times", | |
| "Try a different AI tool", | |
| ], | |
| "answer": 2, | |
| "why": "Treat the first answer as a first draft. Shorter, less formal, you dropped the part about the invoice. Two or three rounds is normal.", | |
| }, | |
| { | |
| "q": "Before using the tool for work, you should confirm that:", | |
| "options": [ | |
| "You are signed into the BOS organization workspace, not a personal account", | |
| "Your manager has approved each request", | |
| "You have read the full user manual", | |
| "The chat is set to private mode", | |
| ], | |
| "answer": 0, | |
| "why": "Check the workspace shown is the BOS organization. If you are unsure which account you are in, ask BOS IT before you use it for work.", | |
| }, | |
| { | |
| "q": "Why start a new chat for each new task?", | |
| "options": [ | |
| "The company is billed per chat", | |
| "Mixing unrelated work degrades results and makes things harder to find", | |
| "Old chats are deleted after an hour", | |
| "It is required by the security policy", | |
| ], | |
| "answer": 1, | |
| "why": "Unrelated work in one long conversation clutters the context and lowers quality. One task per chat keeps results sharp and searchable.", | |
| }, | |
| ], | |
| # Module 4: Better Results | |
| [ | |
| { | |
| "q": "You want consistent output in your own format and tone. The most reliable technique is:", | |
| "options": [ | |
| "Describe your style in detail", | |
| "Paste an example of past work you were happy with and ask for the same style", | |
| "Ask the tool to guess your style", | |
| "Use very short prompts", | |
| ], | |
| "answer": 1, | |
| "why": "One good example teaches format and tone faster than any description. Here is how I wrote the last three, write the next one the same way.", | |
| }, | |
| { | |
| "q": "You need a long document. The better approach is:", | |
| "options": [ | |
| "Ask for the whole thing in one request", | |
| "Ask for an outline, review it, then write one section at a time", | |
| "Ask three times and pick the best one", | |
| "Ask for it twice as long, then cut", | |
| ], | |
| "answer": 1, | |
| "why": "Breaking big tasks into steps catches problems early and gives each piece full attention. One shot requests for long documents invite mediocre results.", | |
| }, | |
| { | |
| "q": "Which instruction cuts hallucination sharply when working from an attached file?", | |
| "options": [ | |
| "Be accurate", | |
| "Answer only from the document and tell me when it does not cover something", | |
| "Use your best judgment", | |
| "Do not make mistakes", | |
| ], | |
| "answer": 1, | |
| "why": "Telling the model to answer only from the document, and to say when the document is silent, keeps it from filling gaps with plausible guesses.", | |
| }, | |
| { | |
| "q": "Before creating a shared project for your team, you should:", | |
| "options": [ | |
| "Just build it, then tell people", | |
| "Ask BOS IT which projects already exist", | |
| "Get sign off from the CEO", | |
| "Copy one from a personal account", | |
| ], | |
| "answer": 1, | |
| "why": "IT can tell you what already exists and help set one up, so we avoid a dozen slightly different versions of the same thing.", | |
| }, | |
| ], | |
| # Module 5: Security and Data | |
| [ | |
| { | |
| "q": "A document may contain Controlled Unclassified Information. You need a summary. What do you do?", | |
| "options": [ | |
| "Summarize it with the company Claude account since it is approved", | |
| "Remove the header and then summarize it", | |
| "Stop and route it through the approved handling process", | |
| "Summarize only the first half", | |
| ], | |
| "answer": 2, | |
| "why": "CUI, Federal Contract Information, and export controlled material never go into any AI tool, including the company one. Treat it as controlled until IT or leadership says otherwise.", | |
| }, | |
| { | |
| "q": "You are drafting a case study that will go to a prospect. How do you refer to the client?", | |
| "options": [ | |
| "By name, since it is good marketing", | |
| "Generically by vertical and size, unless the client approved attribution in writing", | |
| "By first name only", | |
| "By site address so it is credible", | |
| ], | |
| "answer": 1, | |
| "why": "External material never carries client names, site addresses, camera locations, account numbers, or contract values without written approval. Use the vertical and size instead.", | |
| }, | |
| { | |
| "q": "Which of these can go into the company Claude account?", | |
| "options": [ | |
| "A VMS login so the tool can write setup instructions", | |
| "An incident narrative tied to a specific site for a client report", | |
| "A compensation spreadsheet to reformat", | |
| "Your own rough meeting notes with the client referred to as Site A", | |
| ], | |
| "answer": 3, | |
| "why": "Credentials, raw incident narratives, and personnel or payroll data never go in. Your own notes with placeholders for client specifics are exactly the right habit.", | |
| }, | |
| { | |
| "q": "A subpoena arrives and you want help drafting a response. You should:", | |
| "options": [ | |
| "Draft it with Claude and send it to legal for review", | |
| "Route it to leadership without drafting anything", | |
| "Draft it yourself without AI", | |
| "Ask the AI what the law requires first", | |
| ], | |
| "answer": 1, | |
| "why": "Responses to legal notices, subpoenas, insurance claims, regulatory inquiries, and client incident disputes go to leadership. They are not drafted by staff, with or without the tool.", | |
| }, | |
| { | |
| "q": "The tool does something strange after you paste an email from an unknown sender. What should you do?", | |
| "options": [ | |
| "Ignore it and keep working", | |
| "Paste the email again to see if it repeats", | |
| "Stop and report it to BOS IT", | |
| "Delete the chat and start over", | |
| ], | |
| "answer": 2, | |
| "why": "Material you give the model can contain hidden instructions that redirect it. Unexpected behavior after pasting outside content is a report, not a retry.", | |
| }, | |
| ], | |
| # Module 6: Everyday Workflows | |
| [ | |
| { | |
| "q": "Which is an appropriate Command Center use of the tool?", | |
| "options": [ | |
| "Describing the video from last night's incident to draft the client report", | |
| "Turning rough shift notes into a consistent report format with no incident specifics tied to sites", | |
| "Pasting dispatch records to find patterns", | |
| "Uploading the law enforcement interaction log", | |
| ], | |
| "answer": 1, | |
| "why": "Cleaning up shift notes and rewriting procedures are good uses. Video descriptions, dispatch records, and law enforcement details stay inside operations systems.", | |
| }, | |
| { | |
| "q": "Which is written correctly per the BOS standard?", | |
| "options": [ | |
| "Virtu Guard, a division of BOS", | |
| "VirtuGuard, a division of BOS Security", | |
| "VG (VirtuGuard) by B.O.S.", | |
| "Virtuguard from Bos Security", | |
| ], | |
| "answer": 1, | |
| "why": "VirtuGuard is one word with a capital V and capital G. Spell out BOS Security on first reference.", | |
| }, | |
| { | |
| "q": "Which formatting rule applies to client communications at BOS?", | |
| "options": [ | |
| "Bullet lists for everything", | |
| "Emojis to keep it friendly", | |
| "Prose with bold inline labels, no em dashes, no emojis", | |
| "All caps headings", | |
| ], | |
| "answer": 2, | |
| "why": "Client communications use prose with bold inline section labels where structure is needed. No em dashes and no emojis, and plain language for non technical readers.", | |
| }, | |
| { | |
| "q": "When should you contact BOS IT?", | |
| "options": [ | |
| "Only when the tool is completely down", | |
| "Before pasting something you are unsure about, and any time the tool behaves unexpectedly", | |
| "After you have already tried a few other tools", | |
| "Only through your manager", | |
| ], | |
| "answer": 1, | |
| "why": "IT would much rather hear from you before you paste something than after. A two minute question on Teams is the cheapest step in the process.", | |
| }, | |
| ], | |
| ] | |