Offer exact source/linear aid, usual communication/access support and another sitting. Capture one meaningful first component before help/key; later response separate. Different valid algorithms/reasons are welcome. No speed/amount-of-writing/programme-completion score. Adult entry/paper planning does not earn independent child implementation. Keep separate teacher key away until first capture; the app never loads these sources.
Held E · Pretend stage energy · Day25
Entirely fictional counter; not a real energy/safety task. Start total3; ordered input records[2,4,1]. The user wants the start included once and every record added to it. Candidate design: FOR EACH [SET total3; ADD current input]; SHOW total. Predict/trace what it does; choose a useful correction or another own algorithm and explain. With approved access, enter/create/change your own blocks, Run and inspect; record operator/help. One meaningful first prediction or design can be captured before continued making.
Optional fresh E aid · Font copyright and permissions and exact alternative; no result/answer drawn. Do not explain the repair during first capture.
Held F · Pretend packet score · Day30
Entirely fictional token rule; no real ranking/allocation. Start total2. For each input: if input<3 add1; otherwise if input<6 add2; otherwise add4. User criteria: start counted once, every record processed, exactly one outcome per record, final total visible. New ordered batch[1,4,7]. Generate/compare an own design, then with approved access create/run it and inspect input/branch/total. Predict/test changed boundary batch[3,6] and empty batch[] when ready; record first versus later work. Different structures that honour the rule are valid. A matching final numeral alone is not the whole evidence.
Optional fresh F aid · Font copyright and permissions and exact alternative; no answered programme/total. Capture a meaningful first component before continuation/help. If no digital access, retain the complete own algorithm/trace and leave implementation open.