By Class 7, text programming is a primary medium rather than a special event. Students design algorithms, use functions with parameters and returns, work with structured data, build simulations, test deliberately and inspect code they did not write.
“I can solve and explain more complex systems.”
Who owns whatThe problem and component structure are supplied; the learner increasingly owns algorithms, text implementation, data handling, testing and explanation.
“I can read and modify structured text with support.”
“I can design algorithms and implement most core logic in text, then test, debug and explain the system.”
Text is normal. Syntax is still not the curriculum.
An illustrative interaction, not a lesson from the curriculum — but the reasoning is the reasoning.
A working program is not the same as a correct program. Find the case that exposes the bug.
Orders of Rs 1,000 or more receive free delivery.
def free_delivery(total):
if total > 1000:
return True
return FalseWhich test case exposes the bug?
Each case passes or fails silently. Pick the one whose expected result the code cannot produce.
| Order total | Expected | Choose |
|---|---|---|
| Rs 850 | false | |
| Rs 1,000 | true | |
| Rs 1,250 | true |
Support matters. A heavily guided success is not reported as independent mastery.
A Band is not a pile of unrelated activities. Each standard Band contains 12 Projects arranged so that capability is established, combined, transferred and increasingly owned.
Design archetype: Simulation / data / model synthesis
Current Band design establishes the synthesis pattern; public Project naming should come from approved curriculum data.
These are Band end-states, not lesson titles. Follow any of them across all eight years in the Capability Telescope.
Class 8 turns fluency into applied building. The architecture is still supplied, but the learner owns serious implementation across algorithms, real data, APIs and simple machine learning.
Enter Ama Dablam Basecamp