Use this checklist before the FLOCO pilot starts. It separates what TutorFlow can support now from the information the customer should confirm before production integration.
Confirmed integration scope
| Item | Current support | Customer input needed |
|---|---|---|
| Input method | POST /v1/content/integrations/expansions accepts customer-owned JSON. | Provide the latest FLOCO production JSON for one glossary level. |
| Source structure | Category, level, and ordered lessons are supported. Unknown fields are preserved in prompt context. | Confirm the final names and required fields for the five lesson types. |
| Output priority | TutorFlow creates outputs in this order: interactive_module, summary_video, expanded_quiz. | Confirm whether all three outputs are needed for pilot review or only the first priority. |
| Result retrieval | Poll status and result endpoints with the returned job id. | Store the TutorFlow job id in the external system. |
| UI-authored content export | POST /v1/content/classrooms/{classroomId}/integrations/exports returns a completed manifest for TutorFlow UI content. | Confirm which UI-authored content should be synced first. |
| Authentication | Expansion endpoints use a TutorFlow workspace API key. UI export uses the signed-in TutorFlow admin session. | Confirm key owner, rotation policy, and environment separation. |
| Rate limits | Rate limits follow workspace API key settings. | Provide expected pilot and production request volume. |
| Webhooks | content.completed and content.failed events are available after polling is verified. | Provide callback URL and retry expectations for production use. |
| Copyright | TutorFlow stores the submitted source payload and generated output metadata. | Confirm FLOCO owns or can process the submitted content. |
| Billing | Generated modules, videos, and quizzes use existing TutorFlow billing meters for those content types. MP4 rendering is separate. | Confirm who owns pilot cost approval and whether video rendering should be enabled after review. |
| Pilot scope | One glossary level can be validated first. | Provide the glossary level JSON and expected review criteria. |
Pilot acceptance checks
- The source JSON is accepted without pre-conversion.
- The job status endpoint moves through
queued,processing, and a terminal status. - The result manifest includes one entry per requested output.
- The interactive module is usable inside TutorFlow.
- Summary video output creates editable video structure before MP4 rendering.
- Expanded quiz output preserves answer intent from source quiz content.
- Authentication, rate limit behavior, and billing expectations are understood before production rollout.