Contributors Who Do Not Program

Contributors Who Do Not Program

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

The agent's side of the contributor studio: an agent fenced into the one course it was asked about, files read as material and never as instructions, a person who switches a new version on for testers, a group or a school, and a person who merges it. What the studio covers today, and how requests in other subjects become proposed changes.

Teachers and authors help write the curriculum, and most of them do not program. For them, the app has a studio. Curriculum as Data, Rendered Anywhere tells the contributor's side: ask for a change in plain words, compare the new version with the old one, try it with a group, hand it in. Here is the agent's side.

The studio's agent is fenced in. It may change only the course the request is about. It is given no access to the wider computer, to the web, or to other agents. Files the contributor attaches, such as a photo or a Word document, are material to read, never instructions. A photo loses its location data before the agent sees it.

The agent never decides who sees its work. A new version reaches children only when a person switches it on. For a school's testers or for one group, that is a contributor who also guides at that school. For a whole school, it is only someone who has been given that right.

A person takes it in. Handing a version in opens a proposed change that names the contributor first. A person merges it: the maintainer who reviews the code, or a contributor who has been given the right to merge.

Today the studio covers the reading courses and Fido's own concept texts. Elsewhere, contributors send requests from the app. The contributors' routine turns a request of a known kind, such as a check of a mathematics lesson, into a proposed change for review; a person sorts the rest.

Keine Aufgaben fĂĽr dieses Thema.