Curriculum build complete

Plant Bot Computing

The complete Reception-to-GCSE computing curriculum.

Age-right lessons, assessment and AI literacy in one traceable path: play-based exploration in Reception, NCCE-adapted primary computing, original KS3 depth and full KS4 specification coverage.

Explore the curriculum Request a school pilot

Built on disk. Pilot and implementation evidence are the next phase.

525
lessons across Years 1-11
36
Reception session cards
89/89
4CP0 specification points
36/36
4IT1 subtopics

Completion record

The curriculum is built. The evidence phase starts now.

Every year band from Reception to Year 11 is present on disk. The build is recorded across 6,775 curriculum files, with per-wave QA reports and a point-level KS4 coverage ledger. We do not yet claim proven pupil impact: that is what the pilot must test.

Source trail CURRICULUM_COMPLETE_README.md QA_REPORT_CYCLE5.md COVERAGE_LEDGER_KS4_FINAL.md v1.1

Reception to Year 11

One journey. Different teaching grammar at every age.

The curriculum does not force GCSE habits onto four-year-olds or leave formal computing until Year 10. Each phase changes its teaching, assessment and AI boundaries while keeping one progression spine.

Seedbed - Reception

Computing as story, pattern and choice.

Six explorations and 36 adult-led session cards build early sequencing, sorting, cause and effect, vocabulary and safe machine framing.

  • Observation only: no tests, marks or levels.
  • Screen-free by default and no pupil-facing AI.
  • Three termly DCF-PS1 observation snapshots.
PhaseBuilt inventoryAssessment shape
Reception6 explorations / 36 cardsObservation snapshots
KS114 units / 78 lessons3-band + portfolio
KS229 units / 158 lessons3-band + 4-level checkpoints
KS322 units / 119 lessonsUnit summatives + formal gates
KS412 blocks + Water Threads / 170 lessonsBlock tests, mocks and practicals

Proof, not promises

A curriculum leadership team can inspect.

Completion is a file-and-ledger claim. Impact is not claimed until a live pilot produces governed evidence.

01

Complete on disk

Reception through Year 11, with an age-specific artefact grammar for each band.

6,775 files
02

Specification traced

Point-level coverage across Pearson Edexcel International GCSE Computer Science and ICT.

0 gaps
03

Assessment governed

Seed Registers, Growth Logs, Harvest Blueprints and human release gates share one objective spine.

R to GCSE
04

Limitations visible

No live classroom pilot yet. Google deployment is documented but unrun. Grounding packs remain review-gated.

Pilot next

Assessment integrity

What was taught stays connected to what is tested.

The Harvest Rule is the operating discipline: serious assessment items must trace back to registered objectives and delivered content. AI may assist staff, but it does not become the marker of record.

Ask for an assessment evidence sample
  1. RegisterSeed Register

    Objective codes, ceilings and provenance.

  2. DeliverGrowth Log

    What was actually taught and evidenced.

  3. DesignHarvest Blueprint

    Coverage and balance fixed before items.

  4. ReleaseHuman Gate

    Teacher verifies, moderates and releases.

Practical delivery

Designed around the classroom, not a product demo.

Lesson assets, assessments and deployment guidance use a shared production grammar so a pilot can test workload, fit and governance as well as content.

Teach

Classroom-ready families

Plans, slides, worksheets, lesson checks, quizzes, summatives and teacher guidance sit together by unit.

  • Full timetable pathway
  • After-school academy pathway
  • Transition and catch-up packs
Operate

Google-ready workflow

Classroom, Forms, Slides, Docs, Gems and NotebookLM have documented deployment routes with age-specific limits.

  • Sandbox-first importer
  • Teacher-mediated under-13 pattern
  • Staff-only AI marking surfaces
Govern

The human stays in charge

Plant Bot is a teaching character and memory system, never a simulated friend or replacement teacher.

  • No pupil data in public G-Root
  • No live paper leakage
  • Human release before feedback

Pilot with purpose

The first school pilot should answer leadership questions.

A pilot is not a vague showcase. It should test timetable fit, teacher workload, learner response, assessment discipline and the practical deployment route.

DoneBuild

Reception-Year 11 curriculum complete on disk.

NextPilot

Planned subject to school partnership confirmation.

LaterScale

Only when governed pilot evidence supports it.

About the author

Built from a live Cardiff classroom.

Plant Bot Computing is authored by Saqub Hussain, Head of ICT at an independent school in Cardiff and a teacher registered with the Education Workforce Council (Wales) in the Independent School Teacher category.

The curriculum grew out of live teaching. Every unit is mapped to Pearson Edexcel International GCSE Computer Science (4CP0) and ICT (4IT1), the NCCE Teach Computing programme and the Curriculum for Wales, with per-lesson provenance under the Open Government Licence v3 — and it is taught today across Years 5–10, including live Edexcel iGCSE delivery at Year 10.

Assessment was engineered alongside the content: entry baselines, a full exam and mock series with mark schemes, a moderation protocol, and an AI-assisted marking framework designed compliance-first — pseudonymised, with the human as marker of record, validated in shadow mode only, and gated behind a completed data-protection impact assessment. The whole estate is built and operated on self-hosted infrastructure.

What we don’t claim yet. Plant Bot Computing does not publish pupil-outcome data: the first full evidence cycle runs in the 2026–27 pilot, and we intend to publish what we find. Everything here is offered for inspection.

G-Root, the curriculum guide

Questions should have an answer before the first meeting.

Ask about age range, curriculum structure, standards, assessment, Google delivery or the pilot route. G-Root answers from approved public material and cannot access pupil records or private school files.

Open Ask G-Root

School pilot enquiry

Tell us what your pilot needs to prove.

A human will review the context before any learner data, private source pack or deployment step is requested.

  • No pupil data in this form.
  • No live assessment material requested.
  • No endorsement or impact claims without evidence.
  • Reply from the branded school pilot desk.

Do not include pupil names, medical or safeguarding details, passwords, API keys or private exam material.

Email instead