TOPIC 04 OF 08

Boundaries and constraints

Make the edges visible

PLAIN-LANGUAGE IDEA

State what the system may use, what it must avoid, which rules matter, and where it should stop. Boundaries can cover sources, length, privacy, jurisdiction, dates, prohibited actions, or the need for human approval.

SEE IT IN A SITUATION

Use only the three attached sources. Do not add customer names. If the sources disagree, show the disagreement instead of choosing one. Stop before sending or publishing anything.

DO NOT MISS THIS

Prompt instructions are not security controls. Connected systems still need permissions, allowlists, testing, logging, and approval gates outside the prompt.

TRY THIS NOW

Write one use rule, one refusal rule, and one point where a person must review the result.

CONNECTED LANDMARKS

your-first-boundaryYour first boundary keep-a-human-checkpointKeep a human checkpoint prompt-injectionPrompt injection

← PreviousNext idea →

TAKEAWAY TOOL

The Request Brief

Use this when a task deserves more than a quick question. Leave a field empty when it does not help; never add sensitive information merely to complete the template.

01Goal
What should the work help you create or decide?
02Audience & perspective
Who is it for, and which viewpoint reveals useful criteria?
03Context
What minimum background and sources change the answer?
04Boundaries
What must it use, avoid, protect, or leave to a person?
05Output
Which structure makes the result easy to inspect?
06Example & tone
What does good look and sound like?
07Evidence
How should uncertainty, sources, and missing facts appear?
08Human checkpoint
Who verifies, edits, approves, or acts?

◉

Important topics change.

Environmental impact, copyright, privacy, security, and EU obligations require dated sources and context. The Atlas teaches durable decision habits and clearly separates them from legal or professional advice.