CS-215 AI Literacy
Topic 12 · Prompt strategy + source safety

Prompt Strategy and Source BoundariesChoose a prompting strategy, test it on fixed cases, and keep untrusted context inside its evidence boundary.

A longer prompt is not automatically a better prompt. Students select a strategy for a bounded task, compare behavior on fixed synthetic cases, revise from evidence, and constrain source use so retrieved text cannot silently change the task.

Before class

Bring or recreate one bounded project task, one weak prompt, and one human-check rule from Topic 11, or use the supplied Study Sprint task. No prior packet, live model, AI account, paid tool, public URL, private upload, live web, or prompt history is required.

Four outcomes you can demonstrate.

The focus is judgment students can show, not vocabulary they can merely repeat.

01 · ROUTE

Choose direct instruction, examples, rubric critique, or source-bound prompting for a task.

02 · TEST

Compare weak and improved prompts using observable criteria and fixed synthetic cases.

03 · BOUND

Treat supplied or retrieved text as inspectable evidence rather than hidden authority or instructions.

04 · HANDOFF

Record prompt, evidence, failure, revision, human checkpoint, and one Topic 13 security risk.

Two meetings with separate learning arcs.

Meeting 1 plans 68 taught minutes plus a 12-minute flex and access buffer; Meeting 2 plans 80 with no separate buffer.

MEETING 1

Choose and Test a Prompt Strategy

Recover a bounded task, route it to a strategy, work through three strategy rounds, build a selective prompt contract, and run a three-case mini-evaluation before revising.

80 MIN
  1. Task before wordingRecover or select a bounded task; identify the job and the behavior that would count as success.
  2. Three strategy roundsCompare direct instruction, examples, and neutral rubric critique through commit-before-reveal cases.
  3. Contract + fixed-case mini-evalChoose only load-bearing prompt fields, test three fixed cases, and revise one component.
  4. Preserve the experimentRecord prompt, test evidence, failure, revision, and human-check rule.
  5. Flex/access bufferUse projected outputs, the account-free lab, paper, private writing, speech-to-text, or LMS text.
Start Meeting 1
MEETING 2

Build a Source Boundary and Security Handoff

Inspect a synthetic source pack, separate evidence from instructions, complete three source-bound rounds, audit an answer claim-by-claim, add permissions and stop rules, and package the Topic 13 handoff.

80 MIN
  1. LaunchOne vague rule, six cases, four roles, one laptop per table.
  2. Cases 1–2 · source role, embedded instructionWhat may enter the prompt; what a line inside a source may not make it do.
  3. Cases 3–4 · not stated, empty ruleWhen the pack cannot answer; when an instruction decides nothing.
  4. Cases 5–6 · permission, the handoff claimWhat a workflow may do unasked; what you may honestly say you found.
  5. Audit + Experiment CardMap claims to sources against the rules the table wrote, then assemble three pages of evidence.
  6. Security handoffName the untrusted-context risk Topic 13 should test; this screen also holds the access and transfer time.
In-class exerciseSource Boundary Simulation

Six cases, four roles, one laptop per table. Your table relays through prompter, reviewer, source owner and security, then writes the rule the case needed. Open it when your instructor names the case; it also works alone.

Open the simulation
Start Meeting 2

Prompt Experiment Card

Define one bounded task; compare a weak and improved prompt; justify the selected strategy; run three fixed synthetic cases; revise from evidence; add a source rule, assistance disclosure, limitation, human-review checkpoint, and Topic 13 untrusted-context handoff.

What to submit

  • Submit the three-page card through the course LMS only if the instructor assigns it. Preferred filename: Lastname-Topic12-PromptExperiment.pdf. LMS text, DOCX/export, scanned paper, speech-to-text, projected/transcript evidence, or an instructor-approved accessible alternative is accepted. The LMS supplies the exact deadline, points, late rule, and resubmission rule.
  • Include one bounded task, observable success criterion, weak prompt, selected strategy and reason, improved prompt contract, and one prompt element intentionally omitted with a reason.
  • Compare the same three synthetic or approved class-safe cases before and after the repair. Record expected behavior, observed behavior, pass/revise/not tested status, one failure, one targeted revision, and one tradeoff or remaining limit.
  • Include a source-bound rule that treats supplied text as evidence rather than authority, rejects embedded instructions, uses not-stated behavior for missing evidence, and names a human-review checkpoint before any consequential external action.
  • No live model, AI account, paid tool, public URL, prior packet, private prompt, private upload, prompt length, generated volume, or polished output determines core credit.
Open assignment