Retrieval and embeddings · Lesson 3 of 16 · 8 min

Review chunk boundaries

Chunk boundaries should preserve enough local context to interpret a passage. Separating a condition from its exception can change the meaning of the retrieved evidence.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read the case evidence
Read /opt/ai-lab/cases/aiops-retrieval-embeddings-003.json. Separate the recorded facts from your assumptions.
Hint & worked example
Chunk boundaries should preserve enough local context to interpret a passage. Separating a condition from its exception can change the meaning of the retrieved evidence.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-retrieval-embeddings-003.json
```
Common mistake to avoid: Treat chunks as unrelated sentences even when an exception changes the rule.
2
Isolate the deciding signal
Select the exception_separated field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Preserve the exception with the eligibility context when reviewing chunking.
A successful JSON query isolates exception_separated.
```
jq .exception_separated /opt/ai-lab/cases/aiops-retrieval-embeddings-003.json
```
Common mistake to avoid: Using a different case or an unrelated signal as the justification.
3
Record your operational decision
Choose the justified code: preserve-exception-context, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-retrieval-embeddings-003-decision.txt.
Hint & worked example
Preserve the exception with the eligibility context when reviewing chunking.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'preserve-exception-context' > /home/learner/lab/aiops-retrieval-embeddings-003-decision.txt
```
Common mistake to avoid: Treat chunks as unrelated sentences even when an exception changes the rule.

Understand the pattern

Chunk boundaries should preserve enough local context to interpret a passage. Separating a condition from its exception can change the meaning of the retrieved evidence.

Interpret the evidence

Preserve the exception with the eligibility context when reviewing chunking.

A tempting mistake

Treat chunks as unrelated sentences even when an exception changes the rule.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result

$ cat /opt/ai-lab/cases/aiops-retrieval-embeddings-003.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "chunk_1": "Eligible after 30 days",
  "chunk_2": "except temporary accounts",
  "exception_separated": true
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .exception_separated /opt/ai-lab/cases/aiops-retrieval-embeddings-003.json

true

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'preserve-exception-context' > /home/learner/lab/aiops-retrieval-embeddings-003-decision.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “preserve-exception-context” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Review chunk boundaries” justify?Preserve the exception with the eligibility context when reviewing chunking.Treat chunks as unrelated sentences even when an exception changes the rule.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Treat chunks as unrelated sentences even when an exception changes the rule.” What should you do?Accept it because the training command completed.Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Read embedding metadata Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

Case methodology: evidence, limits, decision