Training

The reference docs answer "how does X work?" The tutorials answer "how do I build my first X?" This section answers a different question: "How do I learn the whole platform end to end?"

The training section is a self-paced 8-week intensive curriculum — 16 modules, one capstone, every platform pillar — that condenses a full college-semester sweep of FastYoke into roughly 160 hours of work.

Jump to

Who this is for

• An industry developer ramping on FastYoke in 4–8 weeks rather than learning piecemeal as tickets come in.
• A Strategic Partner engineer (see iNetko) onboarding to support or implement on FastYoke for customer engagements.
• An evaluator who wants to gauge how much surface there actually is to learn before committing.

Delivery mode

Self-paced. There is no cohort schedule, no enrollment, no proctored exam. A learner who can follow the syllabus end-to-end has effectively completed the program. Run it as fast or as slow as your workload allows; pause and resume at module boundaries.

If you want to use this material to run a cohort or in-house training engagement, the same content works as the source-of-truth syllabus.

Prerequisites

• JavaScript or TypeScript fluency.
• Comfort with REST + HTTP basics.
• A working curl + Unix shell.
• Familiarity with a relational-database concept (rows, foreign keys) and JSON.

No prior FastYoke knowledge is required.

Cadence

• 8 weeks, 16 modules (two per week), ~20 hr/wk workload — ~160 hours total.
• Each module follows a uniform five-section shape — learning objectives, assigned reading, lab title, project deliverable title, quiz topics — documented in the Syllabus.
• The capstone is a single multi-week project, default shape: ship a Tenant Yoke end-to-end. See Capstone.

What's in this section today

• This index — the framing you're reading.
• Syllabus — 16 modules with learning objectives, reading lists, and lab/project titles per module.
• Lectures — short narrative explainers per module: the why behind each primitive, mental model, key concepts, common pitfalls.
• Labs — hands-on exercises per module with verifiable checkpoints + answer-key solutions. Most carry Postman + curl paths side by side.
• Quizzes — 10-question self-check banks per module (160 questions total) with reveal-style answers and brief explanations.
• Capstone — final integration project with a five-category self-grading rubric.
• Starter code — skeleton scripts and JSON templates the labs reference. Parachute, not template.
• Certification — sealed-PDF completion certificate issued via the M14 e-sign trust model on capstone acceptance.

How to use the syllabus self-paced

1. Read the syllabus end-to-end first to know where every module sits.
2. Pick a starting module — the syllabus order is the recommended order, but every module's reading list cross-links into reference docs you can also consume out of order.
3. For each module, work the lab (once labs ship) and submit the project deliverable to your own sandbox tenant.
4. The capstone is the final integration — see Capstone.

What's not in training today

Each item below is a deliberate follow-on:

• Capstone walkthrough — a worked reference Tenant Yoke that hits every rubric category. Deferred until real submissions land so it doesn't anchor early learners.
• Centrally-graded submissions / auto-grader — the rubric is self-graded; there is no platform-side grader and no LLM-graded path. Reviewers are humans.
• Cohort delivery materials — instructor guides, slide decks, recorded lectures. Only relevant if you run a live cohort. The existing content is the source-of-truth syllabus either way.

See also

• Tutorials — the 101/201/301 on-ramp for developers who want a guided build rather than a structured curriculum.
• Recipes — single-task snippets you can copy-paste during a module.
• Developers — the day-1 API invariants every module assumes.