Set up the curriculum

Create one named DeepTutor knowledge base for each curriculum or level, upload the approved material and answer conventions, wait for indexing, and verify it with deeptutor kb info <name>. Select that exact curriculum_kb in the dish. A single DeepTutor instance may hold several named KBs; Question Bank categories are not treated as class authority.

Register artifact storage

Before configuring or scheduling a class dish, register one writable file collection under Connections -> Files. For the simplest local setup, first create an existing absolute directory on the Recued server host, make it readable and writable by the Recued server process, and then enroll it with the Filesystem adapter. The root directory must already exist; Recued does not create or choose a host directory. The collection slug is owner-chosen and is not hardcoded; deeptutor-artifacts is only a recommended example. An enrolled writable S3 collection is also valid and does not require a local folder.

Select that collection in Assessment artifact files on every saved class dish. One collection can serve every class, or classes may use different collections. Keep the selected slug and backing storage available while assessments remain active because assessment manifests retain that exact slug. Recued automatically creates its deeptutor-daily-mastery/assessments/... and deeptutor-daily-mastery/submissions/... subdirectories or object keys beneath the selected collection root.

One scheduled dish per class

Save one clone per Seller tier/class. Choose assignment or exam, a stable assessment_key, topic, difficulty, language, question_count, artifact file collection, and sender mail account. question_count defaults to 5 and must be a positive whole number; Recued does not author a maximum. Each question remains bounded to 3,000 characters and its reference answer to 1,500, while the complete portable JSON artifact must fit 5 MiB. The roster remains bounded to 100 validated students. The DeepTutor terminal requested/template/completed/results counts must all equal question_count, every id must be unique, and every observed tool call must be successful RAG against the exact KB.

The compact manifest key is active.assessment.<class_segment>.<assignment|exam>.<assessment_locator>. The email marker carries the same versioned class/kind/locator tuple. Students reply once with all answers labelled by question_id. Use List DeepTutor assignments and exams to open exact details later.

Crash posture

The generated artifact is canonical JSON at a SHA-256-addressed path. Recued writes it, rereads it, verifies its digest and identity, and only then CAS-pins its compact manifest at revision 0 before mail. Same-content concurrent writes are harmless; different generations use different paths, and only one CAS winner can send. A losing race may leave an unreferenced file for later cleanup but cannot replace the winner. Mail uses stable reconciliation ids; revision 1 is written only after all recipients succeed. A prepared run safely resumes from the pinned artifact, and a delivered run is a no-op.

Permissions remain owner-configurable in Pack detail -> Permissions. The KB inspection is a read operation with no default approval; DeepTutor generation, file/shared writes, and mail retain their declared posture.