Module 01 Activity

Scenario

You are deciding whether a new service should use LangChain or the provider SDK directly, and which parts should not touch the framework at all.

What you build

A written architecture decision, with the framework/SDK boundary drawn and the concerns that stay in your own code listed.

Steps

1. Describe what the service does in five sentences. Note whether it composes several pieces or makes one call.
2. Sort it against the five situations from Unit 01 and pick SDK or framework, with the reason.
3. List the abstraction costs you are accepting, and say which one you will actively mitigate.
4. Build the smallest chain that does the job and print the type at each boundary.
5. Sort six concerns into inside/outside the framework, and justify anything you put inside.
6. Print the resolved prompt once, and keep that line in the codebase.

Evidence to hand in

• The five-sentence description with the composition note.
• The SDK-versus-framework decision and its reason.
• The type at each chain boundary.
• The inside/outside table.
• The resolved prompt as it goes over the wire.

Review checklist

• The decision cites composition or provider-swapping, not preference.
• Business rules, retries, validation and logging are outside the framework.
• The types at each boundary are named.
• The resolved prompt has actually been printed and looked at.
• If the answer was 'SDK', that is written down plainly.

Mark complete