Skip to main content
The idea behind CrazyGoldFish is that grading, planning, and teaching should inform each other instead of sitting in separate tools. This page is about that direction.
Nothing on this page is a shipped feature or a commitment. For what works today, read the product pages and the API overview. Ask CrazyGoldFish before you plan around anything described here.

​
What already joins the products up?

Four things are real today, and they are the parts the products genuinely share.

​
What does not join up yet?

Being plain about this matters more than the vision does, because it decides how much your platform has to build.
  • Results do not travel on their own. Every step is a call your platform makes. Grading an exam does not create an action plan, and an action plan does not create a worksheet.
  • An action plan does not become a worksheet without you. A plan describes what needs work in sentences. Something has to turn those sentences into the topic a builder can use.
  • Nothing is remembered between exams. Each action plan covers one exam or one answer sheet. There is no stored picture of what a student knows that builds up over a term.
  • Assignments and classroom observation stand apart. Action plans read exam results only, and an observation does not change a rubric, a lesson plan, or a worksheet.
  • There is no view across products. No single place shows a class, a teacher, or a school across grading, planning, and observation. If you want that, you build it from the results you collect.
  • There is nothing for parents. No parent product, no parent report, and no messages sent to anyone.

​
Where is this heading?

Two gaps above are the ones worth closing: a result from one product being usable by the next without your platform translating it, and what a learner has shown being remembered from one exam to the next rather than looked at once and forgotten. Neither works today. Until it does, the honest description of CrazyGoldFish is a set of strong single-purpose APIs that share an account, a vocabulary, and a rubric.

​
Frequently asked questions

The four shared things in the first table are. Everything under “where is this heading” is not.
No. Build as though your platform orchestrates every step, because today it does. See one exam, end to end for exactly which calls that means.
The product pages and the API reference. Both are written from the running code, and a feature is only there if the API does it.
Not today. Results are stored against the exam or the answer sheet they came from. Any progress history lives in your own system.

​
Next steps

The five products

What each one takes and gives back today.

One exam, end to end

Every call your platform makes, in order.

Introduction

What CrazyGoldFish is and who it is for.

All APIs

Every endpoint, grouped by product.