# Four-role desk critique · original unpiloted draft

**Teacher:** One model/route starts immediately; optional print/no-device equivalence useful. SET/source/body/IF decisions need scaffolding appropriate to actual prior experience; do not assume the short prior menu established coding. A shared device can constrain actual child entry; attribute support. One useful observation rather than30route logs. Future systems/network/common-tool and current SE review remain gaps.

**Learner:** Own purpose, values, operations and tests change an actual result. Blank editor avoids a solved activity; adding nested bodies may still demand assistance. Choose one meaningful first component/split sitting; no completion quota. Real access/child pilot and screen-reader/switch testing not supplied; labelled controls do not prove all access.

**Family:** Every home offer free/standalone/conversational; no purchase/device/account/identifying data. Extras optional, not catch-up homework. Browser closing loses work by design; this limitation is visible. No fabricated family feedback/trial.

**Funder/reviewer:** Ten substantial starts/30filled routes/20varied contexts/10home10extras/8aid pairs/2fresh cases are authored components, not attained descriptors/hours/full-year curriculum or served publications. Computer source/engine/browser/rebuild/render/fault gates must be read with exact freeze and human/local holds. New visual programming depth leaves broad14-description band/system/data/privacy/common-tool gaps. No automatic common-tool, broader community impact or learner-benefit claim.