Examples and packages

An example is a whole course to start from: its activities, the AI beside the work and how far it may go, the questions and rubrics it uses, and the files it reads. A package is the file any course travels as, and each example is one.

Start from an example

Docs → Examples has six, each arranged differently: fractions practice with a checked tutor, a PDF reading with a Socratic tutor, an argument essay, English speaking practice by voice, a density lab on an embedded page, and a library research desk that answers from its guides.

Only a project's owners and editors add courses this way. An activity that is hidden in the example stays hidden until you open it.

Download a course as a package

On a course, press Download as package, then choose:

• The course (.json): one file with the course's settings, units and activities, the agents they use (each one's published version) and the question sets their Questions panels ask. Reading panels and knowledge bases stay behind.
• With its files (.zip): the same, plus each Reading panel's PDF and the knowledge bases its agents search: their uploaded files, and the addresses of their websites, which are read again where it's imported. Up to 25 MB.

The project's owners and editors can download it, since it carries the agents' workflows.

Duplicate a course

On a course, press Duplicate and choose Into the project: this one, or another where you're an owner or editor. You get a new draft with the course's settings, look, units and activities, and none of its learners: no class list, sections or anyone's work, and activities with dates start hidden.

• In the same project, the copy is called "… (copy)" and uses the same agents, question sets and readings, with the course's AI key.
• In another project, that project gets its own copies of the agents, question sets and knowledge bases, and you choose one of its keys. An agent whose name it already uses gets "(imported)" after it.

Learners never move with a course. Their work stays with the course they did it in. An agent that a course, study or chat page still uses can't be moved to another project, since they use only their own project's agents: duplicate the course there instead.

Bring a file into a project

In the project, open Teach → Courses, press From an example or a file, then Choose file under Upload a package and pick the .viable.json or .viable.zip. If you own or edit more than one project, choose Into the project. The course arrives as a new draft, with new knowledge bases for its files. An agent whose name the project already uses gets "(imported)" after it. If something can't be made, nothing half-made is left open.

What a package never carries

• Learners, the class list, sections, or anyone's work.
• The course's key, or the first project's IDs.
• In a .json without files: knowledge bases. A Reading panel comes without its PDF and is left out, so add it again, and an agent comes without the knowledge bases it searches. Download it with its files to keep them.
• The headers of an agent's Fetch URL steps, and email addresses in the course information.
• Opening dates. Each activity is open, or hidden until you open it.

A .viable.json can be up to 2 MB and a .viable.zip up to 25 MB, with up to 20 agents, 50 question sets and 100 activities. A package can also name its files by address instead, as the examples do: they are fetched when it is used.