Lesson 5 of 12 intermediate

Orchestration and safe parallel work

একসাথে বেশি agent মানেই বেশি লাভ না। আলাদা কাজ, আলাদা file আর integration check দরকার।

Guess first

Pick an answer. You will see if you were right at the end of the lesson.

Who resolves conflicting assumptions before merge?

Open interactive version (quiz + challenge)

Real-world analogy

Several builders can work on different rooms only after agreeing where the walls and pipes go.

What is it?

Orchestration assigns work, sequences dependencies and integrates results. Parallel work helps when tasks have clear boundaries. It can increase cost and conflicts when every worker edits the same files or makes different API assumptions.

Real-world relevance

One shared support-ticket product, three optional entry points. Frontend: Separate component work from browser-test work against one agreed interface. Backend: Separate service and database changes only after agreeing the migration and API contract. Mobile: Separate UI and queue implementation with a shared state contract.

Key points

Draw dependencies — API contract precedes client implementation. Integration follows both.
Assign ownership — One worker owns client files and another owns backend files; shared schema changes have one owner.
Use isolated work — Branches or worktrees prevent concurrent edits from silently overwriting each other.
Return evidence — Each handoff names changed files, tests, limitations and unresolved questions.
Integrate sequentially — Review one candidate, run contract checks and then integrate the next.
Budget total work — Count all workers and retries, not only the coordinator request.
Prefer one worker when enough — A small bug does not need a planning committee of agents.
Frontend practice — Separate component work from browser-test work against one agreed interface.
Backend practice — Separate service and database changes only after agreeing the migration and API contract.
Mobile practice — Separate UI and queue implementation with a shared state contract.

Quick check

Answer from memory — scrolling up first makes it stick less.

What artifact demonstrates this lesson?

Which statement is defensible?

Code example

Contract -> Backend fixture -> Integration test
        -> Flutter queue ----^
        -> Review UI --------^

Handoff:
- Changed files
- Test command and result
- Contract version
- Known failures
- No deployment performed

Line-by-line walkthrough

1. The graph permits independent implementations only after the contract. Arrows end at a shared integration check, not at automatic release.

Spot the bug

Two agents both edit the database schema independently

Need a hint?

Who resolves conflicting assumptions before merge?

Show answer

Assign schema ownership and require an approved contract before parallel implementation.

Explain like I'm 5

একসাথে বেশি agent মানেই বেশি লাভ না। আলাদা কাজ, আলাদা file আর integration check দরকার।

Fun fact

A useful artifact for this lesson: API contract precedes client implementation. Integration follows both.

Hands-on challenge

Choose ONE stack; you do not need to build all three. Junior foundation: Complete one task sequentially and write a clear handoff. Senior extension: Partition two independent tasks, inject a contract mismatch and catch it at integration. Evidence: save the input, expected behaviour, actual result and one failure or limitation. Junior means basic coding and Git, not zero programming experience.

More resources

Free Context Course (Hugging Face)
Download the free offline lab (Python, tests and instructions) (Teamz Lab)

Open interactive version (quiz + challenge) Download the whole course as PDF / Word

Lock it in

← Back to course: AI-Assisted Software Engineering