Context Management 103: เตรียม source bundleContext Management 103: prepare a source bundle

A source bundle is the material AI should use as evidence.

It can be pasted text, file excerpts, links, meeting notes, screenshots, tables, or code snippets. The important part is not the format. The important part is that the model knows what each source is and how to use it.

Why source bundles matter

If you paste ten paragraphs without labels, the AI has to guess:

• where the text came from
• which parts are current
• which parts are authoritative
• which parts are draft notes
• whether outside knowledge is allowed

A good source bundle makes those decisions explicit.

The source bundle format

Use this simple structure:

Sources:

[Source 1]
Type:
Date:
Owner:
Use for:
Do not use for:
Content:

[Source 2]
Type:
Date:
Owner:
Use for:
Do not use for:
Content:

You can shorten it for small tasks, but keep labels when accuracy matters.

Include boundaries

Boundaries tell the AI what a source can and cannot prove.

Use for: current workshop lesson titles and order.
Do not use for: pricing, launch date, or certificate policy.

This is useful because real documents often mix confirmed facts, old ideas, and unfinished drafts.

Prefer excerpts over dumps

Do not paste a whole document if only one section matters.

Better:

Source: product guideline excerpt
Use for: brand boundary between learn app and marketing site
Excerpt:
- learn app owns lesson, practice, workshop, guide, course, progress UI
- www site owns marketing and catalog pages

This gives the model high-signal context without burying the task.

If the full document is needed, say why:

The full policy is included because the answer must check for contradictions across sections.

Preserve source identity

When working with files, include file paths.

File: src/lib/catalog.ts
Use for: current workshop metadata shape
Relevant fields: id, titleTh, titleEn, descTh, descEn, badge, lessons, duration, thumbnail

When working with research, include links and dates.

Source: official docs page
Access date: 2026-05-08
Use for: current terminology only

This helps later verification.

Separate facts from notes

Do not mix confirmed facts with ideas in one unlabeled block.

Instead:

Confirmed facts:
- Thai is default language.
- Free workshops use /workshops/{slug}/ route shape.

Draft ideas:
- Could include screenshots exercise.
- Might add a final context-pack template.

The model should not treat every note as a decision.

Tell AI what to do when source is missing

Add a rule:

If the source does not support a claim, say "not stated in the source" instead of guessing.

This is one of the highest-value context rules for reliable work.

Practice: build a source bundle

Choose a task:

Write a lesson summary for beginners.

Now create a source bundle with three sources:

[Source 1]
Type:
Date:
Use for:
Do not use for:
Content:

[Source 2]
Type:
Date:
Use for:
Do not use for:
Content:

[Source 3]
Type:
Date:
Use for:
Do not use for:
Content:

Then add this instruction:

Use only the sources above for facts. If a detail is missing, list it under "Needs human confirmation".

Next: Context Management 104 - use examples and constraints.