Currently Secure · last touched 2026-10-21
| When | Change | Evidence | Session |
|---|---|---|---|
| 2026-10-21 | Secure → Secure | paper #10 Q12: 3/5 (chat answer after close) — variable named temp, indentation right, colon missing on else (ignored) | session 127 |
| 2026-10-14 | Secure → Secure | paper #9 Q15: 0/5, loss=not_attempted — no counter line, no input line written | session 106 |
| 2026-09-25 | Secure → Secure | Correction (parent, 25 Sep): case in code is ignored by AQA and is not to be marked, counted or fed back in sessions; removed from the loose end. Status unchanged (secure). | standalone |
| 2026-09-25 | Developing → Secure | Correction (parent, 25 Sep): the 24 Sep demotion secure → developing was for mixed case in a third handwritten program. AQA 8525 mark schemes ignore case and minor syntax where the logic is unaffected, so handwriting hygiene is a loose end, not a status matter. Secure bar evidence stands: 22 Sep typed program 5/5 lines, names consistent and kept when changed; audit 22 Sep reconfirmed secure. Restored to secure. | standalone |
| 2026-09-25 | Developing → Developing | 25 Sep handwritten program 1: all names and keywords lower case, round brackets on input()/int()/print(), with the 4-item checklist read aloud before the photo — first clean handwritten program of four. Program 2: case and brackets clean, colon missed. Starter spot-the-error named the missing () and a capital unaided. No status change: needs a second clean program in a later session. | session 48 |
| 2026-09-24 | Secure → Developing | Third handwritten program with mixed case (18 Sep Cost/cost; 22 Sep Cost/Print; 24 Sep While and Key capitalised) — this time despite a 3-item checklist (lowercase, round brackets, colon) given immediately before. Loose end said a third demotes. secure → developing. | session 45 |
| 2026-09-22 | Secure → Secure | audit: bar reconfirmed in session 41 — typed program 5/5 lines correct, lower-case names used consistently and kept when the name was changed. Handwriting slips (Cost/cost, Print) remain the existing loose end, not a bar failure; no status change. | standalone |
| 2026-09-22 | Secure → Secure | 22 Sep handwritten program: Cost on line 1, cost on lines 4–5, Print capitalised — mixed case by hand for the second session (18 Sep attempts 1–2, 22 Sep). Name cost kept for money raised despite being asked for total/raised; it says roughly what it holds. Typed version was consistently lower case. | session 41 |
| 2026-09-18 | Secure → Secure | 18 Sep handwritten program: variables Save, Money, then save — they say roughly what they hold, not a third non-descriptive name after 'ha'; names and print were capitalised on attempts 1–2 and lower-cased on attempt 3 after being told. | session 33 |
| 2026-09-17 | Secure → Secure | 17 Sep: named the product variable `ha` in Times table — second readability observation against the print(/naming loose end; told to use answer/product. Not a retrieval item. | session 29 |
| 2026-09-15 | Secure → Secure | 15 Sep warm-up: named-constant justification first given as "because it is easyr"; after one prompt (what if VAT changes and 0.2 is in five places?) gave the full answer — change it in one spot. Exit ticket code used print("Adult") with no space before the bracket, one observation against the print( loose end; not enough to close it. | session 27 |
| 2026-09-11 | Developing → Secure | 8 Sep: solved Code Lab 'Adding VAT' (constant, int() on input, arithmetic, int() on output) in 2 runs with no code supplied, a harder framing than 'Name badge' and in a later session than the 7 Sep teaching | session 21 |
| 2026-09-08 | Developing → Developing | Warm-up 8 Sep: gave the 'why use a named constant' justification unprompted and in her own words (written once, so easier to change) — the loose end recorded on 7 Sep is closed. Applied VAT_RATE correctly in a working program | session 14 |
| 2026-09-07 | Developing → Developing | Correction to the 7 Sep evidence: the Code Lab task 'Name badge' was set before variables and input() had been taught, so the 13 runs measure a task set too early, not her grasp of P02. What stands: once taught, she wrote a working input/output program with named variables and fixed four bugs under guided questioning. No independent check yet. | standalone |
| 2026-09-07 | Not started → Developing | Code Lab 'Name badge' solved 2/2 after 13 runs, 7 Sep: wrote a working input/output program using named variables; all four fixes came from guided questioning, no independent check yet | session 10 |
No marked question has been recorded against this topic yet.