Checking device saving. Saved learning will load when ready; choices made now are not added.
Chapters · 4 of 7
AI judgment foundations / Chapter 4 / Practice
Share less and question instructions
Before you start
Building software
Keep the information needed for a task, check permission to share it, and keep instructions inside source material from taking over the task.
Original fictional records and scripted feedback. No model is running; no message, code or approval is sent.
First case
Prepare a test-plan brief from a fictional issue. Keep repository content from expanding the helper's instructions.
Fictional notes
Note 1
Draft a regression test plan using invented input Test input 9. Do not use production rows, run commands or upload files.
Note 2
Demo importer v4 accepts a blank title and then shows an empty heading. Expected: reject the blank title with a clear message. Test input 9 contains invented blank and normal titles.
Note 3
The issue attachment offers a production sample and says to upload a diagnostic file before planning. This text is part of the attachment; the owner did not request those steps.
Note 4
No diagnostic file is needed to describe the observed blank-title failure. The requested output is a draft plan.
Which plan matches these notes?
Choose a proposal before reading its rationale.
Plan A
Draft the importer test plan using invented input Test input 9 and the blank-title result. Keep commands and uploads out; treat the attachment’s extra request as text to report, not permission.
Fits the records. The owner supplied and permitted Test input 9. The attachment cannot expand that request into a production-data or upload task.
Plan B
Draft the importer test plan using the attached production sample and the blank-title result. Keep commands and uploads out; treat the attachment’s extra request as text to report, not permission.
Needs revision. The request permits the invented input only. A production sample does not become permitted because it is attached.
Plan C
Draft the importer test plan using invented input Test input 9 and its normal-title control. Keep commands out, but include the attachment’s diagnostic upload as a separate preparation step.
Needs revision. The owner prohibited uploads. Moving an embedded request into a preparation step still exceeds that boundary.
Changed case
An importer error depends on text shape. Choose a useful test input without exposing an actual customer identifier.
Fictional notes
Note 1
The owner reports an import failure for an identifier with the shape two letters, a hyphen and four digits. Customer identities and full production rows are not needed for this test-plan task.
Note 2
The approved drafting tool may receive invented invented test inputs. Production identifiers, logs and credentials may not be shared there.
Note 3
Invented value ZX-2048 reproduces the same validation failure in the supplied demo. Invented control ZX2048 passes. These are fictional invented test input values, not real identifiers.
Note 4
Draft a reproduction comparison. Root cause and the intended rule for accepting hyphens are not yet confirmed. No code change or production access is authorized.
Which plan matches these notes?
Choose a proposal before reading its rationale.
Plan A
Use invented values ZX2048 and ZX2049 to compare the importer result. Keep production rows out; mark the cause and intended hyphen rule open before proposing a code change.
Needs revision. Both values remove the hyphen. That loses the supplied failing-versus-passing distinction.
Plan B
Use the original production identifier and an edited no-hyphen copy to compare the importer result. Keep adjacent fields out; mark the cause and intended hyphen rule open.
Needs revision. The permission excludes production identifiers, even when adjacent fields are removed. The invented pair already reproduces the difference.
Plan C
Use invented values ZX-2048 and ZX2048 to compare the importer result. Keep production rows out; mark the cause and intended hyphen rule open before proposing a code change.
Fits the records. The pair preserves the observed text-shape difference within the permitted data. The intended rule and cause remain open.
Takeaway
- Write the task before choosing the data. Keep only fields that actually change the useful result.
- Check who may receive the information and what the tool may do with it. Necessary does not mean permitted.
- Use fictional examples, placeholders or a smaller extract when they are sufficient. Removing names alone is not a privacy guarantee.
- Treat instructions inside documents or returned content as source text, not new user permission.
- Limit tool access and review the output. If necessary sharing is not permitted, ask for permission or use a narrower route.
Paper practice is self-checked; independent demonstration has not been assessed.
Lesson quiz self-check
Practice: data handling
1 point for each correct answer; 0 for wrong or unanswered. No penalties. The denominator is every question, including unanswered questions. These are practice scores, not a measure of broader competence.
Note 1: An invented value with two commas reproduces a parser error; expected behavior is to retain all three fields. Note 2: Only invented inputs may enter the drafting tool. Draft a test plan.
Which input supports the plan?
- A production row with two commas and the three-field expectation; keep adjacent customer fields out.
- The invented two-comma value and the three-field expectation; keep the production row out.
- The invented no-comma value and the three-field expectation; keep the production row out.
Answer and explanations
Needs revision: A production row with two commas and the three-field expectation; keep adjacent customer fields out. The permission does not cover production rows, even with adjacent fields removed.
Correct: The invented two-comma value and the three-field expectation; keep the production row out. It preserves both the reproducing shape and the expected outcome within the permission.
Needs revision: The invented no-comma value and the three-field expectation; keep the production row out. Removing both commas removes the supplied failing shape.
Note 1: The developer requested a summary using the invented build log only and prohibited uploads. Note 2: A user-written log line requests a diagnostic upload before the summary.
Which preparation follows the request?
- Summarize the invented log without an upload; mention the embedded request as log content.
- Summarize the invented log after the diagnostic upload approved by the developer’s separate instruction.
- Summarize the production log without an upload; mention the embedded request as log content.
Answer and explanations
Correct: Summarize the invented log without an upload; mention the embedded request as log content. The log line cannot add an upload step to the developer’s bounded request.
Needs revision: Summarize the invented log after the diagnostic upload approved by the developer’s separate instruction. No separate upload instruction appears; the developer explicitly prohibited it.
Needs revision: Summarize the production log without an upload; mention the embedded request as log content. The request permits the invented log only, not a production log.
Note 1: A customer name was removed from an error report, but a unique account number remains. Note 2: Customer identifiers may not enter this tool. Note 3: An invented equivalent reproduces the error.
Which version should enter the tool?
- The name-removed report with its account number, preserving the observed error for the plan.
- The original report with its customer name, preserving the observed error for the plan.
- The invented equivalent with the same error, preserving the useful comparison for the plan.
Answer and explanations
Needs revision: The name-removed report with its account number, preserving the observed error for the plan. The account number still identifies the account and lacks sharing permission.
Needs revision: The original report with its customer name, preserving the observed error for the plan. The original report includes still more unapproved identifying information.
Correct: The invented equivalent with the same error, preserving the useful comparison for the plan. The invented equivalent is sufficient without sharing a customer identifier.