Good program design is expensive. An Instructor can spend hours sequencing prerequisites, checking distractors and deciding when support should fade. When that work remains inside one account, the next Instructor starts again.
The Community Store lets Professional, Researcher and Institution accounts browse shared pathways and clone a promising one into their own workspace. The copy can then be inspected and adapted before it reaches a learner.
In practice that is four steps: open Browse Modules, open a card to read its detail view, press Clone to My Modules, then open the new copy in your own pathway editor to review every stage before you assign it to a student.
What a clone gives you
A shared pathway carries its stage sequence, activity configuration, selected concepts and criteria — that is more useful than a PDF description because the structure is ready to examine and edit inside the same environment where it may later run. What travels automatically depends on where the material comes from: concepts drawn from Interlaza’s built-in library bring their images and sounds with them, but a concept the author added themselves, or the physical objects an off-tablet stage calls for, are not shipped by the clone — the recipient may need to recreate the concept or gather the same materials before the stage runs as intended.
It is not a clinical recommendation. The author designed it for a particular purpose and context. The recipient remains responsible for deciding whether those assumptions fit.
Five checks before assigning community material
- Goal: does the pathway teach or measure the relation you actually care about?
- Prerequisites: can the learner use the response format and perform the simpler relations the sequence assumes?
- Stimuli: are examples recognizable, licensed and appropriate for the learner’s language and context?
- Procedure: do prompt, feedback, correction and probe settings — trials run with no help and no feedback, most often on material the child has not practised, though some hold the material constant and vary the criterion instead — match the claim the pathway makes?
- Criterion: does reaching it justify the label shown, or is a generalization or maintenance check still needed?
A visible clone count can tell you that other people found a module interesting. It cannot answer any of those five questions.
Authorship is a starting point for trust
Shared work should not become anonymous content detached from responsibility. The Store shows an author’s display name and clone count on every card and in the detail view, so a user can judge provenance before importing something. It does not display a license field — a shared pathway is assumed shareable inside the Store by the act of publishing it there, and a recipient distributing it further should confirm the terms with the author rather than assume any particular license.
That signal has limits too. A real name does not prove quality, and a flagging system does not amount to pre-publication peer review. Treat unfamiliar pathways as peer resources: useful enough to inspect, never safe merely because they are available.
- Read the proposal
- Review stages and criteria
- Copy and adapt before assigning
Who the Store is for
Browsing, cloning and publishing belong to the Professional tier and above. The Family experience is intentionally guided and does not expose the pathway authoring workspace.
This boundary keeps the home interface clear and puts editing controls where the person using them is expected to review program structure.
Why this is worth building
The Community Store is not a race to the largest catalog. Its value is the shorter path from “someone has solved a similar design problem” to “I have reviewed and adapted a defensible starting point.”
Interlaza provides the structure, provenance and editable copy. The Instructor provides the judgment.